coreforged-mcp

# CoreforgedMCP **One MCP server to dock them all.** CoreforgedMCP is a gateway that consolidates multiple MCP servers behind a single endpoint. Instead of configuring 5 separate servers in your `.mcp.json`, you configure one — and control which plugins load with a single environment variable. ``` Before: 5 servers × 5 processes × 5 config blocks After: 1 server × 1 process × 1 config block ``` ## Quick Start ```bash pip install coreforged-mcp coreforged-mcp init ``` This adds CoreforgedMCP to your `.mcp.json`. Restart Claude Code — you're running. ## What You Get ### The Gateway (free, open source) - **Plugin docking** — native Python plugins load in-process; proxy plugins spawn as subprocesses - **Products on demand** — products come from your CoreForged menu and dock when a task needs them; a named loadout such as `COREFORGED_LOADOUT=analytics` docks, when the gateway starts, the products it names that you have installed - **Plugin discovery** — drop a plugin into `~/.coreforged/plugins/` and the gateway finds it; a product you own docks when a task needs it, from your CoreForged menu or when your agent asks, and any other plugin docks when `COREFORGED_PLUGINS` or a loadout names it - **Cross-platform** — Windows, Mac, Linux ### KeyRing — Free Secret Management KeyRing's tools never put your API keys in the conversation. The encrypted store and its master key sit in `~/.coreforged/keyring/`, and an agent that can read files there can decrypt the store without any KeyRing tool. Keep your agent and its file tools out of `~/.coreforged/`. KeyRing is bundled with the gateway: ```bash pip install coreforged-mcp coreforged-mcp setup # creates keyring, wires MCP config ``` Secrets are encrypted at rest (Fernet/AES-128-CBC + HMAC-SHA256) with a machine-local master key. The keyring retrieves and decrypts the secret, makes the authenticated API call, and returns only the response data. Every checkout is logged. A …