Skip to main content
Glama

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}" } } } }

F
license - not found
-
quality - not tested
D
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mdonnalley/mcp-concierge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server