MCP Broker mark

Open-source tool

MCP Broker

Free / open source

MCP Broker: Unified Context Infrastructure

Stars1LicenseMITLatest releasev1.2.0Primary languagePython
View public repo

Product identity

MCP Broker

one ingress. many servers. safe by profile.

MCP Broker brand header with product tagline
Profilessafe by default
Brokerone ingress
Toolsmany servers

Routing proof

One local entry before the tool sprawl.

MCP Broker makes the product promise concrete: one local entry point, a profile-gated tool view, and only the allowlisted tools the active client should see.

01

Client entry

Codex, Claude Code, Gemini CLI, or another MCP client talks to one local broker facade.

02

Profile gate

The active profile decides which upstreams and mutating tools are visible.

03

Allowlisted tools

Search, describe, call, and status stay compact instead of flooding every session.

Before broker

Every client repeats server lists, context expands, and upstream lifecycle becomes each tool's problem.

After broker

One broker owns profile exposure, namespace routing, upstream startup, and safe invocation.

Product brief

What it does and why it exists.

Curated from the product README. GitHub owns install commands, release details, and the full operator docs.

01

Why it exists

MCP clients tend to repeat server lists, start duplicate upstream processes, spread OAuth and browser state across tools, and spend context on raw tool definitions before the task needs them.

  • One local entry point replaces repeated per-client MCP server lists.
  • Profile gates keep each client view small and intentional.
  • Broker-owned lifecycle keeps shared and per-session upstreams predictable.

02

What it owns

MCP Broker runs a local daemon behind a stdio client shim. It owns profile exposure, namespace routing, upstream startup, reuse, cleanup, status, and safe tool calls.

  • Search, describe, call, and status are exposed through a compact broker facade.
  • Mutating upstreams stay hidden unless a profile allowlist grants access.
  • Runtime state stays under $HOME/mcp/mcp-broker, outside the repo.

03

Who it is for

Use it when Codex, Claude Code, Gemini CLI, or another MCP client has more tools than you want loaded into every session.

  • Local developers with many MCP tools across more than one client.
  • Teams that want shared local MCP servers without duplicate startup.
  • Operators who want one place for sockets, logs, OAuth state, and cleanup.

Launch status

A process broker for Model Context Protocol clients. Consolidate local agent infrastructure, optimize context windows, and manage tool access across AI sessions through a single endpoint.

Current focus

  • Reduce token overhead by exposing a compact tool facade rather than dumping every integration into the prompt.
  • Prevent orphaned background processes and duplicate startups with central server routing and cleanup.
  • Enforce tool budgets and isolate stateful sessions while protecting sensitive integrations behind explicit access gates.

Repository signals

Use the public project source.

GitHub remains the source for code, releases, issues, and operator documentation. This page explains where the project fits in the Doric Stack portfolio.

Back to products