Mcp All
Run and compose multiple MCP servers from one stdio or HTTP endpoint so Claude Code or Cursor can manage a whole tool stack without hand-editing every server config.
Overview
io.github.Antonytm/mcp-all is an MCP server for the Build phase that runs and routes other MCP servers over stdio or streamable-http from one npm package.
What is this MCP server?
- Acts as an MCP hub that runs other MCP servers from a single connection
- Ships via npm as @antonytm/mcp-all (v0.1.20) with stdio and streamable-http transports
- TRANSPORT env var configures how child servers are reached
- Useful when you outgrow a flat mcp.json and need nested or dynamic server startup
- GitHub source at Antonytm/mcp-all for self-hosting and forks
- Package version 0.1.20 on npm as @antonytm/mcp-all
- Two documented transports: stdio and streamable-http (e.g. http://localhost:3001/mcp)
- TRANSPORT environment variable is the primary runtime switch
Community signal: 1 GitHub stars.
What problem does it solve?
Juggling many MCP server entries and transports in each agent client becomes brittle as soon as you add a second or third integration.
Who is it for?
Indie developers standardizing a local or small-team MCP stack in Claude Code or Cursor before shipping product features.
Skip if: Builders who only need one fixed MCP server with no nesting, or teams that want a hosted SaaS catalog instead of self-run orchestration.
What do I get? / Deliverables
After install, your agent talks to mcp-all once and can reach a managed set of child MCP servers with a single TRANSPORT configuration.
- Single MCP entry that proxies or runs configured child MCP servers
- Repeatable local stack for stdio or localhost streamable-http
- Fewer manual edits to per-tool MCP client configuration
Recommended MCP Servers
Journey fit
Canonical shelf is Build because installing mcp-all is part of wiring the agent’s local tooling layer before feature work, not a one-off launch or growth task. agent-tooling fits meta-MCP orchestration: spawning, routing, and transport switching (stdio vs streamable-http) for other servers.
How it compares
MCP orchestration layer, not a domain integration like databases or Sitecore.
Common Questions / FAQ
Who is io.github.Antonytm/mcp-all for?
It is for developers who run multiple MCP servers and want one parent server to start and connect them for Claude Code, Cursor, or similar agents.
When should I use io.github.Antonytm/mcp-all?
Use it during Build when you are assembling agent-tooling—especially when switching between stdio and streamable-http or adding servers without redoing the whole client config.
How do I add io.github.Antonytm/mcp-all to my agent?
Install @antonytm/mcp-all from npm, set TRANSPORT for your chosen mode, register the server in your agent’s MCP config (stdio or http://localhost:3001/mcp), then restart the client.