π¦ Container Deployment¶
You can run MCP Gateway as a fully self-contained container. This is the recommended method for production or platform-agnostic deployments. You can use any container engine (ex: Docker or Podman).
Quick Start (Pre-built Container Image)¶
If you just want to run the gateway using the official OCI container image from GitHub Container Registry:
docker run -d --name mcpgateway \
-p 4444:4444 \
-e HOST=0.0.0.0 \
-e JWT_SECRET_KEY=my-test-key \
-e BASIC_AUTH_USER=admin \
-e BASIC_AUTH_PASSWORD=changeme \
-e AUTH_REQUIRED=true \
-e DATABASE_URL=sqlite:///./mcp.db \
--network=host \
ghcr.io/ibm/mcp-context-forge:0.6.0
docker logs mcpgateway
You can now access the UI at http://localhost:4444/admin
π³ Build the Container¶
Using Podman (recommended)¶
Using Docker (manual alternative)¶
The base image uses
python:3.11-slim
with Gunicorn and Uvicorn workers.
π Run the Container¶
With HTTP (no TLS)¶
This starts the app at http://localhost:4444
.
With Self-Signed TLS (HTTPS)¶
Runs the gateway using certs from ./certs/
, available at:
β Runtime Configuration¶
All environment variables can be passed via:
docker run -e KEY=value
- A mounted
.env
file (--env-file .env
)
π§ͺ Test the Running Container¶
Use
curl -k
if running with self-signed TLS
π§Ό Stop & Clean Up¶
Or with Docker: