FREE & OPEN SOURCE · MIT LICENSE

One MCP config.
Every agent.

Your tools, shared across Claude Code, Codex, Cursor and beyond. Configure once. Load less context. Decide exactly what each agent can do.

YOUR AGENTS
Claude CodeCodexCursorAny MCP client
mcpμ
ONE SHARED CONFIG
NamespacesCompressionPermissions
DocumentationFilesystemGitHubYour servers
LOCAL STDIO + REMOTE HTTP
Runs on your machineTerminal + web UINo subscription
01 / SHAREStop maintaining the same setup everywhere.

Configure your servers.
Connect your agents.

Add a server to mcpmu once. Point each agent at the gateway and share the same server definitions, authentication and tool rules.

Keep work, personal and project tools in separate namespaces. Each agent gets the right view of the same configuration.

Explore namespaces ↗
ONE SETUP. MULTIPLE CLIENTS.μ
# Add your server once
mcpmu add context7 -- npx -y @upstash/context7-mcp

# Connect Claude Code
claude mcp add mcpmu -- mcpmu serve --stdio

# Connect Codex to the same setup
codex mcp add mcpmu -- mcpmu serve --stdio
Use stdio locally, or a persistent Streamable HTTP endpoint.
02 / COMPRESSMore room for the work that matters.

Your context is precious.
Spend it on the task.

A large tool catalog can fill your context with schemas before an agent starts working. mcpmu replaces that upfront payload with three wrapper tools and a compact catalog.

Your agent discovers what’s available, fetches full schemas when needed, and calls the underlying tools. You choose how much detail the catalog includes.

FULL TOOL SURFACE
100schemas in context

Every tool. Every schema. Up front.

WITH MCPMU COMPRESSIONlist_toolsget_tool_schemainvoke_tool
3schemas in context

Compact catalog. Full schemas on demand.

lowFull descriptions
highNames + arguments
maxTool names only
mcpmu namespace set-compression work medium

Opt-in, per namespace. Example counts are from a setup with 8 servers and 100 tools. Actual context savings depend on your tool catalog and compression level. How compression works ↗

03 / CONTROLA shared config doesn’t mean shared access.

The right tools.
For the right agent.

Give a research agent read access. Allow a development agent to make changes. Block a dangerous tool across every namespace.

mcpmu enforces permissions at the gateway, including calls through compression. Denied tools stay out of discovery and their calls are blocked before dispatch.

Understand tool permissions ↗
EXAMPLE ACCESS POLICY
Example permissions for research and development namespaces
ToolResearchDevelopment
read_file✓ Allow✓ Allow
write_file− Deny✓ Allow
delete_file− Deny− Deny
Global deny rules always take precedence.

With compression enabled, clients see wrapper tools. Set permissions for the underlying tools in mcpmu.

BUILT FOR YOUR WORKFLOW

See what you’re sharing.

Manage servers, namespaces and permissions in your terminal or browser.

mcpmu web
mcpmu web interface showing configured servers and management controls
Browser UIServers, namespaces, registry and metrics
mcpmu
mcpmu terminal interface with the namespace tool permissions editor
Terminal UIKeyboard-driven, everything from the terminal
YOUR TOOLS. YOUR CONFIG. YOUR RULES.

One small gateway.
A better MCP setup.

Free and open source. No account or subscription required.

View source on GitHub ↗
INSTALL WITH HOMEBREW · MACOS / LINUX
brew tap Bigsy/tap
brew install mcpmu