MCP Concierge logo

MCP Concierge

mdonnalley/mcp-concierge
0 starsUpdated 2025-08-20Community

Is this your server?

Add your score badge to your README and get your server in front of 45k+ builders a month.

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

A local stdio MCP concierge that aggregates multiple remote MCP servers, forwarding their tools with name-prefix routing to avoid conflicts.

README.md

MCP Concierge (POC)

A local stdio MCP concierge that connects over stdio to your MCP client and forwards to one or more remote MCP servers over HTTP or SSE using a static Authorization: Bearer token.

Usage

  • Put a registry at ~/.mcp-concierge/registry.json or pass --registry.
  • Start single remote: mcp-concierge --server <name> [--verbose]
  • Start multiple remotes (aggregator): mcp-concierge --server <name1> --server <name2> or --server name1,name2
  • Requires JWT_TOKEN env var for any remote that is not open: true.

When multiple remotes are selected, tools are aggregated and exposed with name-prefix routing using a safe delimiter: <remote>__<tool> (no slashes). Call tools using that full name. If you call a bare tool name and it is ambiguous across remotes, the server will suggest the fully qualified options.

Example client config:

{ "mcpServers": { "data-cloud-queries": { "command": "mcp-concierge", "args": ["--server", "data-cloud-queries"], "env": { "JWT_TOKEN": "${env:JWT_TOKEN}" } } } }

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Other servers.