OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
MCP & Tooling

MCP Proxy — tbxark

MCP Proxy is a Go-based, self-hosted Model Context Protocol server proxy that aggregates multiple downstream MCP servers behind one HTTP entrypoint. It exposes their tools, prompts and resources to clients, supports stdio, SSE and streamable-HTTP downstream connections, and serves clients through SSE or streamable HTTP. It also supports OAuth authorization and token refresh for downstream servers that require interac

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

MCP Proxy — tbxark — OpenViST project profile in MCP & Tooling.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use MCP Proxy when an MCP client setup needs one HTTP entrypoint for resources from several downstream servers, or when the proxy's OAuth handling can centralize authorization for those servers.

Who it is for

  • Operators assembling multiple MCP servers behind one client-facing endpoint.
  • Teams that need to connect downstream MCP servers using different transport types.
  • Operators seeking a centralized OAuth flow for downstream MCP services that require interactive authorization.

Documented uses

  • Aggregate tools, prompts and resources from multiple configured MCP servers.
  • Expose downstream MCP services to clients over SSE or streamable HTTP.
  • Manage OAuth authorization and token refresh for supported downstream servers.
  • Build or run the proxy from source, through Go installation, or in Docker.
Before you choose

Requirements & limits

The project is public source code under the MIT License. The README documents source builds, Go installation and Docker deployment.

  • Downstream configuration supports stdio, SSE and streamable HTTP.
  • Client-facing transports include SSE and streamable HTTP.
  • OAuth support is described for downstream servers requiring interactive authorization, with the proxy holding and refreshing tokens.
  • The Docker image includes support for launching MCP servers through npx and uvx.
  • An online Claude configuration converter is linked from the project README.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Build and start MCP Proxy from source

Build the Go project and launch it with a configuration file.

Before you start

  • Git
  • Go build tooling and make
  • A configuration file for MCP Proxy

Steps

  1. Clone the tbxark/mcp-proxy repository.

  2. Change into the repository directory.

  3. Run make build.

  4. Start ./build/mcp-proxy with --config path/to/config.json, substituting the path to your configuration file.

Expected outcome

The built proxy starts using the supplied configuration file.

Guide limitations

  • The README does not specify configuration contents or downstream server setup in this quick-start sequence.
Documentation 1 ↗
Source-based practical guide

Start MCP Proxy with Docker and a configuration file

Launch the proxy container with a mounted local configuration file.

Before you start

  • Docker
  • A local MCP Proxy configuration file

Steps

  1. Mount the local configuration file at /config/config.json in the container.

  2. Run the ghcr.io/tbxark/mcp-proxy:latest image and publish port 9090 to port 9090.

Expected outcome

The Docker command starts the proxy container with the mounted configuration and published port.

Guide limitations

  • The command uses the latest image tag.
  • The deployment reference contains additional options, including docker-compose.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
13 October 2026
Original website title
tbxark/mcp-proxy · Official homepage title · retained in its source language
How we review sourcesSuggest a correction