Magg MCP Aggregator

Example Use Cases

• 1

  Discover and dynamically add new MCP servers and tools at runtime without human intervention.

• 2

  Aggregate and proxy tools from multiple backend MCP servers under unified prefixes so calls are routed transparently.

• 3

  Persistent, reloadable configuration and operational features like health checks, JWT authentication, kits, and Docker/HTTP/stdio transports.

Description

Magg acts as a central hub for managing multiple Model Context Protocol (MCP) servers, enabling LLMs to search for, install, configure, enable/disable, and proxy tools at runtime. It supports dynamic configuration reloading, automatic tool proxying with configurable prefixes, kit-based grouping of servers, persistent configs, optional JWT bearer auth, and multiple transport modes (stdio, HTTP, in-memory). Magg is intended as a self-service tool manager for agents to extend their capabilities without human intervention and includes tooling for health checks, monitoring, and a CLI (mbro) for exploration.