MCP Proxy Hub MCP Server

An MCP proxy hub that aggregates and serves multiple MCP resource servers through a single interface

Local serverstdio

What is the MCP Proxy Hub MCP server?

MCP Proxy Hub becomes available to MCP clients through the mcp proxy hub mcp server. An MCP proxy hub that aggregates and serves multiple MCP resource servers through a single interface.

What MCP Proxy Hub does

An MCP proxy server that aggregates and serves multiple MCP resource servers through a single interface. This server acts as a central hub that can:

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

  • Server — specific variables take precedence over global variables with the same name
  • Stdio — type Server**:
  • command — Command to execute (required)
  • args — Command line arguments (optional)
  • env — Environment variables (optional)
  • exposedTools — Array of tools to expose (optional)
  • hiddenTools — Array of tools to hide (optional)
  • envVars — Environment variable configuration for tool arguments and responses (optional)
  • timeout — Request timeout in seconds for downstream tool calls (optional, overrides the top-level timeout; 0 disables the timeout)
  • enable — Whether to enable the server (optional, default: true)
  • SSE — type Server**:
  • type — "sse" (required)
  • url — URL of the SSE server (required)
  • headers — Object of HTTP headers to send with the SSE connection (optional)

Installing the mcp proxy hub mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 7 environment variables: MCP_PROXY_CONFIG_PATH, KEEP_SERVER_OPEN, USER_ID, GLOBAL_API_KEY, MCP_PROXY_AUTH_TOKEN, MCP_PROXY_LOG_DIRECTORY_PATH, MCP_PROXY_PATH. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. MCP Proxy Hub sits in that group, and the shape of its toolset — Server, Stdio, command among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use MCP Proxy Hub.
  • Maintained by naotaka3.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the mcp proxy hub mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
Serverspecific variables take precedence over global variables with the same name
Stdiotype Server**:
commandCommand to execute (required)
argsCommand line arguments (optional)
envEnvironment variables (optional)
exposedToolsArray of tools to expose (optional)
hiddenToolsArray of tools to hide (optional)
envVarsEnvironment variable configuration for tool arguments and responses (optional)
timeoutRequest timeout in seconds for downstream tool calls (optional, overrides the top-level timeout; 0 disables the timeout)
enableWhether to enable the server (optional, default: true)
SSEtype Server**:
type"sse" (required)
urlURL of the SSE server (required)
headersObject of HTTP headers to send with the SSE connection (optional)

How to install the MCP Proxy Hub MCP server

{
  "timeout": 30,
  "mcpServers": {
    "slow-server": { "command": "...", "timeout": 0 },
    "fast-server": { "command": "...", "timeout": 5 }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
MCP_PROXY_CONFIG_PATHFilesystem location the server is allowed to use.Optional
KEEP_SERVER_OPENConfiguration value read at startup.Optional
USER_IDConfiguration value read at startup.Optional
GLOBAL_API_KEYCredential the server authenticates with.Yes
MCP_PROXY_AUTH_TOKENCredential the server authenticates with.Yes
MCP_PROXY_LOG_DIRECTORY_PATHFilesystem location the server is allowed to use.Optional
MCP_PROXY_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use MCP Proxy Hub to Server.
  • Use MCP Proxy Hub to Stdio.
  • Use MCP Proxy Hub to command.

Frequently asked questions

It connects MCP Proxy Hub to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Server, Stdio, command, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Proxy Hub directly.