It runs as a fully compliant MCP server, deployable via PyPI or Docker, and scales to multi-cluster environments on Kubernetes with Redis-backed
It runs as a fully compliant MCP server, deployable via PyPI or Docker, and scales to multi-cluster environments on Kubernetes with Redis-backed federation and caching. The mcp context forge mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.
For a list of upcoming features, check out the ContextForge Roadmap
@modelcontextprotocol/inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 7 environment variables: MCP_AUTH, MCP_SERVER_URL, MCP_TOOL_CALL_TIMEOUT, JWT_SECRET_KEY, AUTH_ENCRYPTION_SECRET, MCPGATEWAY_BEARER_TOKEN, DATABASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by IBM; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
{
"mcpServers": {
"context-forge": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"MCP_AUTH": "your-value",
"MCP_SERVER_URL": "your-value",
"MCP_TOOL_CALL_TIMEOUT": "your-value",
"JWT_SECRET_KEY": "your-value",
"AUTH_ENCRYPTION_SECRET": "your-value",
"MCPGATEWAY_BEARER_TOKEN": "your-value",
"DATABASE_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| MCP_AUTH | Configuration value read at startup. | Optional |
| MCP_SERVER_URL | Endpoint or connection string the server talks to. | Yes |
| MCP_TOOL_CALL_TIMEOUT | Configuration value read at startup. | Optional |
| JWT_SECRET_KEY | Credential the server authenticates with. | Yes |
| AUTH_ENCRYPTION_SECRET | Credential the server authenticates with. | Yes |
| MCPGATEWAY_BEARER_TOKEN | Credential the server authenticates with. | Yes |
| DATABASE_URL | Endpoint or connection string the server talks to. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.