MCP Proxy Server MCP Server

An MCP proxy server that aggregates and serves multiple MCP resource servers through a single interface with stdio/sse support

Local serverstdioGo

What is the MCP Proxy Server MCP server?

Most file and storage access work still happens through a UI a human drives. MCP Proxy Server MCP server moves it into the conversation instead. An MCP proxy server that aggregates and serves multiple MCP resource servers through a single interface with stdio/sse support.

The short version

This server acts as a central hub for Model Context Protocol (MCP) resource servers. It can:

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

The tools it exposes

The server publishes 14 tools. What each one is for:

  • mcpServers — (Required) An object where each key is a unique identifier for a backend server
  • name — (Optional) A user-friendly display name for the server (used in Admin UI)
  • active — (Optional, default: true) Set to false to prevent the proxy from connecting to this server
  • type — (Required) Specifies the transport type. Must be one of "stdio", "sse", or "http"
  • command — (Required if type is "stdio") The command to execute the server process
  • args — (Optional if type is "stdio") An array of string arguments to pass to the command
  • env — (Optional if type is "stdio") An object of environment variables (KEY: "value") to set for the server process. These are merged with the proxy
  • url — (Required if type is "sse" or "http") The full URL of the backend server's endpoint (e.g., SSE endpoint for "sse", MCP endpoint for "http")
  • apiKey — (Optional if type is "sse" or "http") An API key to send in the X-Api-Key header when the proxy connects to this specific backend server
  • bearerToken — (Optional if type is "sse" or "http") A token to send in the Authorization: Bearer header when connecting to this specific backend server
  • installDirectory — (Optional if type is "stdio") The absolute path where the server itself should be installed (e.g., /opt/my-server-files). Used by the Admin UI's
  • installCommands — (Optional for Stdio type) An array of shell commands executed sequentially by the Admin UI's installation feature if the target server directory

What it needs from you

Configuration is passed through the environment: API_KEY, PORT, ALLOWED_KEYS, MCP_PROXY_SSE_ALLOWED_TOKENS, ENABLE_ADMIN_UI, ADMIN_USERNAME, ADMIN_PASSWORD, SESSION_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP Proxy Server.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the file and storage access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Proxy Server's toolset — mcpServers, name, active and 11 more — is a fair guide to whether it matches your workflow. It is maintained by ptbsare; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP Proxy Server's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
mcpServers(Required) An object where each key is a unique identifier for a backend server.
name(Optional) A user-friendly display name for the server (used in Admin UI).
active(Optional, default: true) Set to false to prevent the proxy from connecting to this server.
type(Required) Specifies the transport type. Must be one of "stdio", "sse", or "http".
command(Required if type is "stdio") The command to execute the server process.
args(Optional if type is "stdio") An array of string arguments to pass to the command.
env(Optional if type is "stdio") An object of environment variables (KEY: "value") to set for the server process. These are merged with the proxy server's environment.
url(Required if type is "sse" or "http") The full URL of the backend server's endpoint (e.g., SSE endpoint for "sse", MCP endpoint for "http").
apiKey(Optional if type is "sse" or "http") An API key to send in the X-Api-Key header when the proxy connects to *this specific backend* server.
bearerToken(Optional if type is "sse" or "http") A token to send in the Authorization: Bearer <token> header when connecting to *this specific backend* server. (If both apiKey and bearerToken are provided, bearerToken generally tak
installDirectory(Optional if type is "stdio") The absolute path where the server *itself* should be installed (e.g., /opt/my-server-files). Used by the Admin UI's installation feature.
installCommands(Optional for Stdio type) An array of shell commands executed sequentially by the Admin UI's installation feature if the target server directory (derived from installDirectory or defaults) does not exist. Commands are ex
enabled(Optional, default: true) Set to false to hide this tool from clients connecting to the proxy.
displayName(Optional) Override the tool's name in client UIs.

How to install the MCP Proxy Server MCP server

{
  "mcpServers": {
    "unique-server-key1": {
      "type": "stdio",
      "name": "My Stdio Server",
      "active": true,
      "command": "/path/to/server/executable",
      "args": ["--port", "1234"],
      "env": {
        "API_KEY": "server_specific_key"
      },
      "installDirectory": "/custom_install_path/unique-server-key1",
      "installCommands": [
        "git clone https://github.com/some/repo unique-server-key1",
        "cd unique-server-key1 && npm install && npm run build"
      ]
    },
    "another-sse-server": {
      "type": "sse",
      "name": "My SSE Server",
      "active": true,
      "url": "http://localhost:8080/sse",
      "apiKey": "sse_server_api_key"
    },
    "http-mcp-server": {
      "type": "http",
      "name": "My Streamable HTTP Server",
      "active": true,
      "url": "http://localhost:8081/mcp",
      "bearerToken": "some_secure_token_for_http_server"
    },
    "stdio-default-install": {
        "type": "stdio",
        "name": "Stdio Server with Default Install Path",
        "active": true,
        "command": "my_other_server",
        "installCommands": ["echo 'Installing to default location...'"]
    }
  }
}

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

Configuration

VariableDescriptionRequired
API_KEYCredential the server authenticates with.Yes
PORTConfiguration value read at startup.Optional
ALLOWED_KEYSCredential the server authenticates with.Yes
MCP_PROXY_SSE_ALLOWED_TOKENSCredential the server authenticates with.Yes
ENABLE_ADMIN_UIConfiguration value read at startup.Optional
ADMIN_USERNAMEConfiguration value read at startup.Optional
ADMIN_PASSWORDConfiguration value read at startup.Optional
SESSION_SECRETCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP Proxy Server to mcpServers.
  • Use MCP Proxy Server to name.
  • Use MCP Proxy Server to active.

Frequently asked questions

It connects MCP Proxy Server to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (mcpServers, name, active, 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 Server directly.