convez.ai
MCP ServerIntegração & APIsAvançado
pandaGaume

MCP Broker

pandaGaume/mcp-broker

Roteia clientes MCP para múltiplos provedores através de um único host

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP que roteia múltiplos clientes para diversos provedores de Model Context Protocol através de um único endpoint. Suporta transporte WebSocket, HTTP Streamable, SSE e stdio, funcionando como camada de relay centralizada para ecossistemas MCP complexos em produção.

Instalação

$npx convez-ai pandaGaume/mcp-broker

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
1
Forks
0
Acompanhando
0
Saúde
28%
Último commit
há 2 dias
Versão
node-v1.14.0
Issues abertas
0
Contribuidores
1

Casos de uso

  • Centralizar acesso a múltiplos servidores MCP em arquitetura corporativa
  • Integrar assets industriais (PLCs, SCADA, telemetria) como servidores MCP
  • Conectar agentes distribuídos (containers, RPA bots) a fontes de dados comuns
  • Abstrair topologia de provedores MCP para clientes genéricos

Veredito

MCP Broker é uma solução robusta e bem arquitetada para orquestração de protocolo MCP em ambientes complexos. Implementação madura em TypeScript com pipeline CI/CI claro e planejamento multi-linguagem (dotnet), adequada para deployments corporativos que precisam centralizar múltiplos provedores MCP.

README

A tradução para o português deste README ainda está na fila.

npm CI License

mcp-broker

Routes MCP clients to multiple Model Context Protocol providers through a single host. WebSocket, Streamable HTTP, SSE, and stdio transports on both sides. The broker registers itself as an MCP server under the reserved slot _broker, so any client can discover what is routable through standard MCP tools.

Why a broker

Real-world MCP deployments rarely consist of a single isolated server. An organization typically wants to expose, behind one endpoint:

  • industrial assets (PLCs, SCADA, machine telemetry) wrapped as MCP servers
  • sensor and data sources that an agent can query on demand
  • agent hosts (micro-containers, headless engines, RPA bots) reachable as tools

mcp-broker is the relay layer that lets all of those connect to a central point and be reached by MCP clients without each client having to know every backend.

Repository layout

This repo is a multi-implementation reference. Each language lives under its own folder, with its own build, dependencies, and release pipeline.

mcp-broker/
├── node/              ← TypeScript implementation (current)
├── dotnet/            ← .NET implementation (planned)
├── docs/              ← protocol, architecture, endpoints
├── .github/workflows/ ← CI + release pipelines per implementation
└── mcp-broker.code-workspace

Open mcp-broker.code-workspace in VSCode for a multi-root workspace with the right tooling per folder.

Implementation status

ImplementationStatusPackageTag prefix
node/published@cyanmycelium/mcp-broker on npmnode-v*
dotnet/plannedCyanMycelium.Mcp.Broker on NuGetdotnet-v*

Quick start (Node)

npx @cyanmycelium/mcp-broker

The broker starts on http://localhost:3000. Connect your MCP provider to ws://localhost:3000/provider/<name>, then point any MCP client at http://localhost:3000/<name>/mcp.

Full instructions, environment variables, and programmatic API in node/README.md.

Documentation

License

Apache-2.0. See LICENSE.

Ver o original no GitHub

Bom para

Relacionados