mcp-supervisor

<h4 align="center">MCP server that dynamically starts and manages other MCP servers</h4>

<h1 align="center"> <br/> MCP Supervisor </h1>

<p align="center"> <a href="#why">Why</a> ⚙ <a href="#install">Install</a> ⚙ <a href="#configure">Configure</a> ⚙ <a href="#skills">Skills</a> ⚙ <a href="#tools">Tools</a> ⚙ <a href="https://modelcontextprotocol.io">About MCP ↗</a> </p>

<p align="center"> <a href="https://github.com/miyamiyaz/mcp-supervisor/actions/workflows/ci.yml"></a> <a href="https://github.com/miyamiyaz/mcp-supervisor/releases/latest"></a> <a href="https://github.com/miyamiyaz/mcp-supervisor/blob/main/LICENSE"></a> </p>

MCP client configs are static. If a child MCP server needs dynamic arguments (e.g. a CDP endpoint that changes every launch), you have to edit the config and restart your client every time.

mcp-supervisor solves this. Configure it once as your MCP server. It starts child MCP servers on demand with whatever arguments you need, and proxies their tools through a single fixed connection.

Also, statically configured MCP servers load all their tools into context at startup — even when you don't need them. With mcp-supervisor, child MCPs are started only when needed and stopped when done, keeping your context window clean.

Paste this into your agent:

> Install mcp-supervisor using https://github.com/miyamiyaz/mcp-supervisor and register it with claude mcp add supervisor -- supervisor-mcp

mise use -g "github:miyamiyaz/mcp-supervisor[exe=supervisor-mcp]"