A postgres-mcp service on its own internal control network and an egress one, a /postgres/* route in both Caddyfiles (and :3105 in the loopback one), and the variables, documented in ENVIRONMENT.md and the example environment. Its external mode is off until POSTGRES_MCP_ALLOWED_HOSTS lists the hosts it may use. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| browser-mcp | ||
| dev-server-mcp | ||
| .gitignore | ||
| ENVIRONMENT.md | ||
| MCP-STACK.md | ||
| README.md | ||
| egress-proxy.squid.conf | ||
| mcp-stack.Caddyfile | ||
| mcp-stack.compose.yml | ||
| mcp-stack.env.example | ||
| mcp-stack.vm.Caddyfile | ||
| mcp-stack.vm.compose.yml | ||
README.md
MCP stack - Docker Compose deployment
Runs the MCP servers (coding agent, development server, browser,
MinIO) behind one Caddy gateway. The servers’ code and their images live
in the mcps repository; this repository only deploys them
from Docker Hub (luciolelii/*), so the host needs no
sources and no build toolchain.
cp mcp-stack.env.example .env # then fill it in: see ENVIRONMENT.md
docker compose --env-file .env -f mcp-stack.compose.yml pull
docker compose --env-file .env -f mcp-stack.compose.yml up -dOn a dedicated VM add -f mcp-stack.vm.compose.yml to
both commands.
- MCP-STACK.md - what runs, how to start and update it, security notes.
- ENVIRONMENT.md - every environment variable, required and optional.