Magg

What sitbon/magg MCP server does

The sitbon/magg MCP server provides a central management layer for other MCP servers. Agents can use it to search for MCP servers, inspect setup instructions, add servers, configure them, and turn them on or off. Tools from enabled servers are made available through Magg, using configurable prefixes to help distinguish their origins.

Configuration is persisted in .magg/config.json, so server selections and settings can remain available between sessions. Magg also supports kits, which group related MCP servers so they can be loaded or unloaded together.

How it works

Magg can connect to backend MCP servers through stdio, HTTP, or in-memory transports. It watches for configuration changes and reloads them without requiring a process restart. Backend tool, resource, and progress notifications can be passed through to the connected client.

The server includes a proxy tool for clients that do not support MCP notifications or dynamic tool updates. Health and connectivity checks are available through the magg_status and magg_check tools. MCP sampling can be used to help configure a server from a URL, although the README does not specify the exact sampling prompts or configuration workflow.

Magg can run in stdio mode for local clients, HTTP mode for system-wide access or web integrations, or hybrid mode to provide both transports at once. HTTP access can optionally use RSA-based JWT bearer-token authentication.

Setup and configuration

The sitbon/magg MCP server requires Python 3.12 or newer. The documented recommended installation uses uv:

uv tool install magg
magg serve

For a direct GitHub run without a separate installation, the README documents:

uvx --from git+https://github.com/sitbon/magg.git magg

Use magg serve --http for HTTP mode, or magg serve --hybrid for both stdio and HTTP. The HTTP port can be changed with --port. Docker images are also published to GitHub Container Registry, and Docker Compose files are provided for production, beta, and development workflows.

The documented Docker authentication option uses the MAGG_PRIVATE_KEY environment variable or a mounted private key file. Configuration can also be supplied through the .magg directory; the README gives examples for mounting a custom directory in Docker.

Tools and capabilities

• Search for MCP servers and discover installation instructions.
• Add, configure, enable, and disable backend servers.
• Aggregate backend tools under configurable prefixes.
• Check server status and health with magg_status and magg_check.
• Group servers into loadable kits.
• Proxy MCP traffic for clients with limited dynamic-update support.
• Explore and manage servers interactively or through scripts with the included MBro CLI.

Limitations and notes

The sitbon/magg MCP server manages and proxies other MCP servers; its available domain-specific tools depend on the backends that are added. The README does not provide a fixed catalog of those backend tools.

Dynamic updates and notifications depend partly on client support, which is why Magg includes its proxy tool. HTTP authentication is optional rather than a stated prerequisite for every deployment. The documented runtime requirement is Python 3.12 or later, and the supplied examples use uv, Docker, or a local development checkout.