mcp-broker

Name: mcp-broker
Author: doricstack

제작자: doricstack버전 2.1.1i★ –i내 컴퓨터에서 실행

레지스트리 이름io.github.doricstack/mcp-broker

설치

개요

제작자가 쓴 설명(영어 원문)

Local MCP broker that exposes one compact entry for many upstream servers.

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

사용자 의견i아직 리뷰가 없어요리뷰는 다음 단계에서 계정 기능과 함께 열려요
우리의 기본 점검i1개 중 1개 통과공개된 정보로 점검했으며, 코드는 아직 스캔하지 않았어요
사용 정도i아직 측정 안 함★ –

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

연결 방식: 내 컴퓨터에서 실행
전송 방식: stdio
카테고리: 기타

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

기본 점검: 1개 중 1개 통과
내 컴퓨터에서 내 사용자 계정의 권한(파일, 네트워크, 앱)으로 실행돼요.
레지스트리에 입력해야 할 키가 나와 있지 않아요.

필요한 것

PyPIPython의 uv 설치(uvx 명령어용)

어떤 앱을 쓰세요?

ClaudeClaude CodeCursorVS CodeChatGPT

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요

{
  "mcpServers": {
    "broker": {
      "command": "uvx",
      "args": [
        "mcp-broker"
      ]
    }
  }
}

터미널에서 이 명령어를 실행하세요

claude mcp add broker -- uvx mcp-broker

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

{
  "mcpServers": {
    "broker": {
      "command": "uvx",
      "args": [
        "mcp-broker"
      ]
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

{
  "servers": {
    "broker": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-broker"
      ]
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검

✓ 통과
제작자와 저장소 일치
레지스트리 이름이 GitHub 계정 doricstack 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
… 아직 점검 안 함
계속 관리되고 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
… 아직 점검 안 함
라이선스 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
– 해당 없음
엔드포인트 응답
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
– 해당 없음
OAuth로 로그인
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
… 아직 점검 안 함
도구 설명에 숨겨진 지시 없음
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요

기타 카테고리의 다른 서버와 비교i

이 카테고리의 다른 서버 32435개 중 0%보다 스타가 많아요
이 카테고리의 다른 서버 32435개 중 34%보다 최근에 레지스트리에 공개됐어요
기본 점검 결과가 이 카테고리의 다른 서버 32435개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

mcp-broker, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(2.1.1)은 2개월 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Python (uv)도 있어야 해요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Apify MCP Server

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Spec Driven Development

제작자: formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

내 컴퓨터에서 실행★ 440MIT14개월 전 업데이트

설치

Remote Desktop Commander

제작자: desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

클라우드에서 실행★ 211어제 업데이트

설치

Apify MCP Server

제작자: apify

Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡

클라우드에서 실행오늘 업데이트

설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

mcp-broker

mcp-broker is a local Model Context Protocol process broker for MCP clients.

Think PgBouncer for MCP: one stable local endpoint in front of many upstream MCP servers. The broker owns upstream startup, reuse, cleanup, profile exposure, status, and safe tool routing.

The core idea is simple: do not make every agent session load every upstream tool definition before the user asks a task.

Why this exists

AI coding sessions with many MCP servers tend to accumulate the same problems:

every client config repeats the same MCP server list
every new session can start duplicate upstream processes
OAuth, browser state, local files, and database handles spread across tools
raw tool lists consume context before the task begins
hosted connector caches can duplicate local MCP tools
orphaned MCP processes survive after client sessions exit

mcp-broker puts a small broker facade in front of those upstreams. It is not a hosted workflow builder; it is local infrastructure for keeping MCP clients small, predictable, and under one config contract.

Client profile

| | one local MCP entry v mcp-broker-client | | Unix socket v mcp-broker-daemon | | profile gates, namespace routing, status, cleanup v upstream MCP servers

The client sees a small set of broker tools:

broker_search_tools

broker_describe_tool broker_call_tool broker_status broker_close_session

The upstream MCPs still exist. They are discovered and called through the broker when a task needs them.

Measured context reduction

On 2026-05-24, the measured Codex setup went from many raw MCP and hosted app tool definitions to one broker facade plus a pruned codex_apps cache.

Surface	Before	After	Reduction
Direct Codex MCP server entries	11	1	90.91%
MCP tool definitions	414	4	99.03%
Hosted `codex_apps` tool definitions	195	39	80.00%
Combined always-loaded tool definitions	609	43	92.94%
Combined serialized tool payload bytes	1,026,171	185,877	81.89%
Combined `o200k_base` tool tokens	276,989	45,281	83.65%

The 92.94% number is a tool-definition count reduction. The 83.65% number is a token reduction for canonical serialized tool payloads measured with tiktoken o200k_base.

See docs/context-reduction-measurement.md for evidence and caveats.

What it does

Runs one local broker daemon over a Unix socket.
Exposes one lightweight stdio client shim to MCP clients.
Starts upstream MCP servers on demand.
Reuses shared upstreams across sessions when configured.
Isolates per-session upstreams when state must not be shared.
Maps upstream tools into stable namespaces.
Exposes compact search, describe, call, status, and caller-bound session-close tools.
Enforces profile-level tool budgets and exposure gates.
Blocks mutating upstream exposure unless a profile allowlist grants it.
Stores runtime state under $HOME/mcp/mcp-broker, outside the repo.
Renders MCP client config entries with dry-run, backup, and rollback.
Provides LaunchAgent install and uninstall flows for macOS.
Provides Linux systemd user-service render, install, unload, and removal flows.
Provides Windows PowerShell Scheduled Task render, install, and removal flows.
Includes unit, journey, live, and e2e tests through Makefile targets.

Core differentiators:

Profile-scoped exposure: each MCP client gets a configured view of upstreams instead of every tool by default.
Mutating-tool gates: mutating upstreams stay hidden until a profile allowlist grants access.
Lifecycle ownership: shared and per-session upstreams are started, watched, stopped, and reaped by the broker.
Client parity checks: rendered profiles can be validated through the same compact broker facade before config is applied.

Who this is for

Use mcp-broker if you:

use Codex, Claude Code, AGY CLI, or other MCP clients
have more MCP tools than you want in every session
need shared local MCP servers without duplicate process startup
want one place for OAuth state, browser state, sockets, logs, and cleanup
need per-client profiles instead of the same tool list everywhere
want a small broker facade instead of raw upstream tool dumps

This repo is not an enterprise MCP control plane. It is local desktop infrastructure for developer-agent workflows.

Current status

Implemented:

YAML config loading from config/broker.private.yaml, created from config/broker.example.yaml.
Strict YAML contract validation for runtime, clients, profiles, upstreams, and policy blocks.
Public JSON Schema validation through config/broker.schema.json.
Runtime path derivation from runtime.root.
Tool namespace mapping from configured upstream prefixes.
Local upstream subprocess lifecycle management and process-group cleanup.
Broker daemon over Unix socket.
MCP client shim and renderers for configured MCP client profiles, including Codex, Claude, and AGY.
AGY profile rendering to .gemini/config/mcp_config.json, including its MCP allowed-server policy.
Dry-run client config rendering, apply-time backups, and rollback.
LaunchAgent render and install scripts with dry-run defaults.
Compact broker facade for search, describe, call, status, and caller-bound session close.
Profile validation from YAML smoke probes.
Discovery parity checks between compact client profiles.
Public and maintainer quality gates through Makefile targets.
Shared-runtime guardrail contracts through P3.8 E2E proof while hosted execution remains disabled by default.

Wiring status:

Codex is wired through the broker.
Claude is wired through the broker after profile validation and manual /mcp acceptance.
AGY is wired through the broker by rendering .gemini/config/mcp_config.json.

Public release status:

The repo is designed to stay public-safe.
Private upstream inventory, account paths, OAuth state, secrets, sockets, logs, and generated client configs stay outside git.
Stable release metadata is validated by make release-version-check; publication proof is tracked in docs/distribution.md.
Docker image support is available for container-friendly configs. Docker MCP Catalog submission still requires Docker review.
MCPB metadata is present at mcpb/manifest.json for local directory review.

See ROADMAP.md for public-facing release work.

Architecture

mcp-broker has three runtime layers:

Layer	Responsibility
Client shim	Presents one stdio MCP server entry to each MCP client and forwards JSON-RPC over the broker socket.
Broker daemon	Owns profile gates, namespace routing, upstream lifecycle, status, logging, and cleanup.
Upstream MCP servers	Run as configured `stdio`, HTTP, streamable HTTP, or SSE connectors with shared or per-session process policy.

The config file is the contract. Profiles decide exposure, upstreams define transport and lifecycle behavior, and smoke probes define safe read calls for validation.

Comparison

Approach	Best fit	Tradeoff
Raw MCP client config	Small setups with a few tools.	Every session loads the full tool list and each client repeats config.
Simple MCP proxy	Forwarding one server to one client.	Does not own upstream lifecycle, profile budgets, or cross-client cleanup.
Hosted app connectors	SaaS tools managed by the client provider.	Local MCP state and cross-client parity remain outside user control.
`mcp-broker`	Local developers with many upstream MCPs across MCP clients.	Adds a local daemon and config contract that must be installed and monitored.

Screenshots Or GIF

The quickstart flow should look like this:

make config-init

make config-validate make broker-status make codex-facade-smoke

In an MCP client, /mcp should show one mcp-broker entry. Use broker_status to inspect profile-visible upstream state.

Quickstart

Prerequisites:

macOS with launchctl for LaunchAgent use.
Python 3.10 or newer available as python3.
make.
Node.js and npx for npm-based upstream MCP servers.
A clone of this repo.

Package installs:

pipx install mcp-broker

uv tool install mcp-broker brew tap ${HOMEBREW_TAP_REF} brew install mcp-broker

Homebrew installs the same console scripts as the Python package. Package installs do not write MCP client config; client wiring stays an explicit Makefile action.

Docker is for container-friendly configs:

docker build -t mcp-broker:local .

docker run --rm -i mcp-broker:local

Local stdio clients and MCPB-style installs use the package-owned lifecycle:

mcp-broker stdio --init-if-missing

Create the local venv, install dependencies, and verify runtime layout:

make setup

Create private config from the public template:

make config-init

config-init creates the destination directory when needed and copies the public template as the starting point. It does not import local MCP inventory, user paths, or secrets.

Edit config/broker.private.yaml for local upstreams. Keep secret values out of config. Use environment variable names or files under:

$HOME/mcp/mcp-broker/secrets/

Run the quality gate:

make quality-gate

Validate the configured YAML contract:

make config-validate

Start the broker:

make broker-start

Check status:

make broker-status

For the full install flow, see docs/install.md. For a clone-to-running adoption flow, see docs/adoption-guide.md#clone-to-running-path. For shared-runtime boundaries, see docs/shared-runtime-guardrails.md. P3.8 E2E proof covers tenant isolation, authz denial, quota denial, session affinity, audit events, rollback, degraded mode, local-only routing, and shared-eligible routing. Hosted execution remains unsupported in the public local broker.

Runtime layout

Default runtime root:

$HOME/mcp/mcp-broker/

Runtime files are not repo files. Upstream OAuth state, browser state, secret files, sockets, logs, rendered client configs, backups, and daemon state belong under the runtime root.

See docs/runtime-layout.md.

Client wiring

Back up a client config:

make config-backup CLIENT=codex

Dry-run render:

make config-render CLIENT=codex CONFIG_RENDER_APPLY=0

Apply after reviewing the rendered file under $HOME/mcp/mcp-broker/renders/:

make config-render CLIENT=codex CONFIG_RENDER_APPLY=1

Rollback:

make config-rollback CLIENT=codex

Use CLIENT=claude or CLIENT=agy after that profile smoke passes and that client is intended to use the broker. For new JSON-based MCP clients, generate a starter block:

make profile-snippet NEW_PROFILE=local-client NEW_CLIENT_FORMAT=mcp-settings-json

See docs/add-profile.md for the full new-profile flow.

Compact broker facade

The compact facade keeps chat-facing profiles small:

Tool	Purpose
`broker_search_tools`	Search configured upstream tools by query. Results carry name, description, upstream, purpose, tags, and mutating flag; the heavy `inputSchema` is omitted and fetched on demand from `broker_describe_tool`.
`broker_describe_tool`	Return schema and metadata for one upstream tool.

| broker_call_tool | Call one upstream tool through br

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

mcp-broker

개요

PopNx MCP의 세 기둥

할 수 있는 일

설치

설치하기 전에

할 수 있는 일

기본 점검i

제작자와 저장소 일치

계속 관리되고 있음

라이선스 있음

엔드포인트 응답

OAuth로 로그인

도구 설명에 숨겨진 지시 없음

기타 카테고리의 다른 서버와 비교i

자주 묻는 질문

대안

Spec Driven Development

Remote Desktop Commander

Apify MCP Server

제작자의 README

mcp-broker

Why this exists

Measured context reduction

What it does

Who this is for

Current status

Architecture

Comparison

Screenshots Or GIF

Quickstart

Runtime layout

Client wiring

Compact broker facade