lelii
/
mcps-docker-compose
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
1 Commit 1 Branch 0 Tags 92 KiB
Markdown 100%
Go to file
Lucio Lelii 2e89c7e0b7 Deploy the MCP servers from published images 
The compose files, the gateway's Caddyfiles, the egress proxy's configuration and
the example .env, moved out of the mcps repository. That repository builds the four
servers and publishes their images to Docker Hub (luciolelii/*); this one only pulls
them, so a server needs neither the sources nor a build toolchain, and a deploy is a
new image tag.

The compose file names its images by one tag, MCP_IMAGE_TAG, defaulting to the build
it was last checked against. File names are unchanged, so existing commands and the
project name - and with it the volumes - stay as they were.

The dev-server image is built with a fixed user, 10001:10001, and the two volumes the
worker mounts take their owner from it; MCP_UID and MCP_GID therefore stay at 10001
and the workspace directory is given to that user, which the docs now say.

The VM settings in .env.example are commented out. They were live, so copying the file
to a laptop started Caddy in HTTPS mode and had it ask a certificate authority for the
production host name from a machine that is not that host.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
 		2026-10-02 11:48:15 +02:00
browser-mcp Deploy the MCP servers from published images 2026-10-02 11:48:15 +02:00
dev-server-mcp Deploy the MCP servers from published images 2026-10-02 11:48:15 +02:00
.gitignore Deploy the MCP servers from published images 2026-10-02 11:48:15 +02:00
ENVIRONMENT.md Deploy the MCP servers from published images 2026-10-02 11:48:15 +02:00
MCP-STACK.md Deploy the MCP servers from published images 2026-10-02 11:48:15 +02:00
README.md Deploy the MCP servers from published images 2026-10-02 11:48:15 +02:00
egress-proxy.squid.conf Deploy the MCP servers from published images 2026-10-02 11:48:15 +02:00
mcp-stack.Caddyfile Deploy the MCP servers from published images 2026-10-02 11:48:15 +02:00
mcp-stack.compose.yml Deploy the MCP servers from published images 2026-10-02 11:48:15 +02:00
mcp-stack.env.example Deploy the MCP servers from published images 2026-10-02 11:48:15 +02:00
mcp-stack.vm.Caddyfile Deploy the MCP servers from published images 2026-10-02 11:48:15 +02:00
mcp-stack.vm.compose.yml Deploy the MCP servers from published images 2026-10-02 11:48:15 +02:00

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 -d

On 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.