CLI that turns MCP servers into terminal commands.
Companies invested years building MCP server integrations. 5,800+ servers, 10,000+ in production, 97M+ monthly SDK downloads. All that work exposes structured APIs over a standard protocol. Why MCP on the command line? explains why this matters and how mcp lets you reuse all of it from your terminal.
MCP servers are draining your hardware — Every MCP client spawns all backend processes at startup and keeps them alive forever. We built lazy initialization and adaptive idle shutdown so the proxy only keeps alive what you're actually using.
Are you new to mcp? Start here:
- Getting started — Install, configure your first server, call your first tool. 5 minutes from zero to working.
- Tutorial — A hands-on walkthrough that covers everything you need to use
mcpday-to-day.
Focused explanations for specific topics:
- Configuration — Config file format, environment variables, server types.
- Authentication — OAuth, API tokens, service-specific setup.
- Registry — Finding and adding servers from the MCP registry.
- Scripting — Using
mcpin shell scripts, piping, CI/CD. - Proxy mode — Expose all servers as a single MCP endpoint for LLM tools.
- Audit logging — Track every operation with queryable logs and real-time streaming.
Technical details and complete specifications:
- CLI reference — Every command, flag, and option.
- Config file reference — Full
servers.jsonspecification. - Environment variables — All supported env vars.
- Architecture — How the codebase is organized.
Recipes for common tasks:
- Supported services — Setup guides for Sentry, Slack, Grafana, GitHub, and more.
- Troubleshooting — Common errors and how to fix them.