dev-mcps/coding-agent-mcp/test
Lucio Lelii 0e6b400441 Bring the three MCP servers together as one deployable stack
They were three folders on one laptop: a coding agent with a git history of its
own, and two servers - a development server and a browser - with none at all.
What makes them a stack is what sits between them, and that lived nowhere: the
compose file, the gateway, the egress proxy and the networks that keep the worker
off the internet. So the whole thing is one repository, and the coding agent's
separate history is folded into it rather than kept alongside.

What is deliberately absent: .env, node_modules, and the live service
definitions. The .example files next to them say what belongs there.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-22 11:45:55 +02:00
..
command-service.test.js Bring the three MCP servers together as one deployable stack 2026-09-22 11:45:55 +02:00
http-transport.test.js Bring the three MCP servers together as one deployable stack 2026-09-22 11:45:55 +02:00
workspace-service.test.js Bring the three MCP servers together as one deployable stack 2026-09-22 11:45:55 +02:00