1. Home
  2. Servers
  3. MCP Gateways & Proxies
  4. MCP Proxy Server

Server profile

MCP Proxy Server

MCP Proxy Server combines multiple MCP backends behind one HTTP entrypoint. It aggregates tools, prompts, and resources while connecting to stdio, SSE, or streamable HTTP servers.

View repositoryInstall & configure

Server facts

MCP Proxy Server

Tech

Runtime / language
goGo
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
737
Last commit
Data as of

Tags

  • Aggregation
  • Go
  • Http
  • Mcp Proxy
  • Sse

Overview

MCP Proxy Server is an aggregation layer for installations that need several MCP servers reachable through one HTTP entrypoint. Instead of treating each backend as a separate client connection, the proxy combines their tools, prompts, and resources. It can connect to stdio, SSE, and streamable HTTP backends, and serve clients using SSE or streamable HTTP. This makes it relevant when local process-based integrations and network-accessible services need to participate in a common MCP access layer. The implementation uses Go and carries an MIT license.

The README documents source builds, installation through Go, and a Docker image. That image includes support for launching backend servers through npx and uvx. Docker examples either mount a local JSON configuration or supply a remote configuration URL. The supplied configuration facts also illustrate per-server settings, authentication-token options, and a tool filter. Those examples are configuration evidence, not a promise of particular upstream services being present in every deployment. Similarly, the structured GitHub tool catalog in the input represents a configured backend rather than native GitHub functionality implemented by the proxy. Actual exposed tools depend on the selected servers and filters. The README links to fuller endpoint and authentication documentation, but does not reproduce it. A hosted configuration converter is available for adapting Claude configurations, while deployment remains controlled by the proxy's own configuration file.

Install & configure

Requirements

  • Go and make for the documented source build
  • A JSON configuration describing the proxy and backends
  • Required runtimes or connectivity for chosen backend servers
Documented launch / install command
./build/mcp-proxy --config path/to/config.json

Run make build in the cloned repository first, then replace the configuration path. The README also offers Go installation and Docker. Serving supports SSE or streamable HTTP; the exact client URL depends on deployment configuration. Listed GitHub tools are backend examples, and the sample blocks create_or_update_file.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.

No install command stated in the README — see repo. Check the client documentation for a supported connection method.

Read the Claude Desktop setup guide

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.

No install command stated in the README — see repo. Check the client documentation for a supported connection method.

Read the Cursor setup guide

Config file · Workspace: .vscode/mcp.json

For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.

No install command stated in the README — see repo. Check the client documentation for a supported connection method.

Read the VS Code setup guide

Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json

Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json

Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.

No install command stated in the README — see repo. Check the client documentation for a supported connection method.

Read the Windsurf setup guide

Config file · Project scope: .mcp.json at the repository root

The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.

No install command stated in the README — see repo. Check the client documentation for a supported connection method.

Read the Claude Code setup guide

Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.

Tools

Source: repository tool metadata. Tool descriptions are a documented snapshot, not a live capability check.

ToolWhat it does
create_or_update_fileConfigured GitHub backend: create or replace one repository file.
search_repositoriesConfigured GitHub backend: find repositories.
create_repositoryConfigured GitHub backend: create a repository.
get_file_contentsConfigured GitHub backend: read repository files or directories.
push_filesConfigured GitHub backend: commit several file changes together.
create_issueConfigured GitHub backend: open an issue.
create_pull_requestConfigured GitHub backend: open a pull request.
fork_repositoryConfigured GitHub backend: fork a repository.
create_branchConfigured GitHub backend: add a repository branch.
list_commitsConfigured GitHub backend: inspect branch commits.
list_issuesConfigured GitHub backend: list issues with filters.
update_issueConfigured GitHub backend: change an issue.
add_issue_commentConfigured GitHub backend: comment on an issue.
search_codeConfigured GitHub backend: search repository code.
search_issuesConfigured GitHub backend: search issues and pull requests.
search_usersConfigured GitHub backend: find GitHub users.
get_issueConfigured GitHub backend: inspect an issue.
get_pull_requestConfigured GitHub backend: inspect a pull request.
list_pull_requestsConfigured GitHub backend: list and filter pull requests.
create_pull_request_reviewConfigured GitHub backend: submit a pull-request review.
merge_pull_requestConfigured GitHub backend: merge a pull request.
get_pull_request_filesConfigured GitHub backend: list changed files in a pull request.
get_pull_request_statusConfigured GitHub backend: inspect combined pull-request check status.
update_pull_request_branchConfigured GitHub backend: update a branch from its base.
get_pull_request_commentsConfigured GitHub backend: read review comments.
get_pull_request_reviewsConfigured GitHub backend: list pull-request reviews.

Names, permissions, and defaults can change. Check the current upstream documentation before granting access.

Use cases

  • Present several MCP backends through one HTTP access point.
  • Combine local stdio integrations with remote MCP services.
  • Deploy a configured aggregation gateway in Docker.
  • Apply a configured tool filter to a backend tool surface.

Strengths

  • Aggregates tools, prompts, and resources rather than tools alone.
  • Connects to three documented backend transport types.
  • Docker image includes npx and uvx support.

Limitations

  • Requires a configuration file describing the backends.
  • Available tools depend on configured servers and filters.
  • Detailed endpoints and authentication instructions are not reproduced in the supplied README.

Frequently asked questions

No. They come from the structured catalog for a configured GitHub backend; exposure depends on backend configuration and filters.

The README lists stdio, SSE, and streamable HTTP.

Prompts and resources are also aggregated.

The README says the image includes npx and uvx support for launching MCP servers.

Yes. A Docker example passes a remote configuration URL using --config.

Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.

Related MCP servers

MCP for Unity

Games & 3D

MCP for Unity links AI assistants to the Unity Editor for scene work, asset management, script editing, testing, and builds. It targets game developers who want to direct editor workflows through natural language.

c#stdio15,026 GitHub stars

Supergateway

MCP Gateways & Proxies

Supergateway bridges MCP transports so stdio servers can reach network clients and remote services can appear locally over stdio. It supports SSE, WebSockets, and Streamable HTTP modes through command-line configuration.

nodestdio2,904 GitHub stars

Unla MCP Gateway

MCP Gateways & Proxies

Unla is a Go gateway that exposes existing APIs and MCP servers through MCP endpoints using configuration. It includes a management interface, recoverable sessions, multi-tenant support, and deployment options for containers or Kubernetes.

nodestdio2,241 GitHub stars

mcp-proxy

MCP Gateways & Proxies

mcp-proxy bridges MCP transport mismatches between clients and servers. It can connect a stdio client to a remote SSE or Streamable HTTP server, or expose local stdio servers through network endpoints.

pythonstdio2,791 GitHub stars

mcpo

MCP Gateways & Proxies

mcpo makes MCP tools available through an OpenAPI-compatible HTTP server. It is for agents and applications that consume OpenAPI endpoints rather than communicating with MCP servers directly.

pythonstdio4,403 GitHub stars

MCPHub

MCP Gateways & Proxies

Organize multiple MCP servers behind shared HTTP or SSE endpoints. MCPHub adds a management dashboard, group-level visibility controls, semantic routing, authentication, and a terminal interface.

nodestdio2,539 GitHub stars

ContextForge

MCP Gateways & Proxies

ContextForge registers and proxies tools, agents, and APIs behind a unified gateway. It targets teams that need discovery, authentication, observability, and policy controls across MCP, A2A, REST, and gRPC services.

pythonstdio4,646 GitHub stars

MCP Hub

MCP Gateways & Proxies

MCP Hub coordinates multiple MCP servers behind one client endpoint. It provides a REST management API and web UI, with server lifecycle controls, authentication handling, and live capability updates.

nodestdio521 GitHub stars