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

MCP Proxy

MCP Proxy is a Python command-line tool that bridges Model Context Protocol (MCP) connections between stdio and HTTP-based transports, including SSE and Streamable HTTP. It can connect a stdio-based client to a remote MCP endpoint or expose a local stdio MCP server through an SSE listener.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

MCP Proxy — 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 the MCP client and server communicate over different supported transports and you need a configured bridge between them.

Who it is for

  • Developers configuring MCP clients and servers that use different transports.
  • MCP users who need a client such as Claude Desktop to reach a remote SSE or Streamable HTTP endpoint through stdio.
  • Developers who need remote clients to connect to a local stdio MCP server over SSE.

Documented uses

  • Bridge a stdio MCP client to a remote SSE or Streamable HTTP server.
  • Expose a local stdio MCP server through an SSE endpoint.
  • Set connection details such as endpoint URL, authentication headers, listening port, host, and server environment variables.
Before you choose

Requirements & limits

  • The tool is a transport bridge; it does not replace the MCP server that provides the tools or the client that uses them.
  • Remote-server mode needs an endpoint URL, while local-server mode needs a runnable stdio command and an SSE listening configuration.
  • Remote authentication can be configured using headers, OAuth2-related options, or the documented API access token environment variable.
  • The repository identifies the project as Python-based and licensed under MIT.

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

Connect a stdio client to a remote MCP endpoint

Configure an MCP client to launch MCP Proxy and connect through it to a remote SSE or Streamable HTTP MCP endpoint.

Before you start

  • MCP Proxy installed and available as the mcp-proxy command.
  • A remote MCP server endpoint URL.
  • An MCP client that can be configured to start a stdio command.

Steps

  1. Add an MCP server entry to the client configuration with mcp-proxy as the command and the remote endpoint URL as its argument.

  2. If the endpoint uses Streamable HTTP, add --transport=streamablehttp to the proxy arguments.

  3. If authentication is required, configure the documented headers or OAuth2 options, or provide API_ACCESS_TOKEN as an environment variable.

  4. Save the client configuration so the client starts the proxy for this connection.

Expected outcome

The client communicates with the remote MCP server through the proxy’s stdio-to-SSE or stdio-to-Streamable-HTTP bridge.

Guide limitations

  • This mode requires the remote endpoint URL; authentication values depend on the server.
  • The README describes client configuration but does not establish support for every MCP client.
Documentation 1 ↗
Source-based practical guide

Expose a local stdio MCP server over SSE

Configure MCP Proxy to start a local stdio MCP server and listen for SSE connections.

Before you start

  • MCP Proxy installed and available as the mcp-proxy command.
  • A runnable local MCP server command.

Steps

  1. Run mcp-proxy with the local server command as its argument.

  2. Set --port for the listening port; set --host if a specific listening address is needed.

  3. Pass environment variables to the local server with --env when required.

  4. Put arguments intended for the local server after the -- separator.

Expected outcome

MCP Proxy starts the local stdio server and exposes it through an SSE listener for remote connections.

Guide limitations

  • This configuration exposes a listening endpoint; the README does not establish network reachability or deployment suitability for a particular environment.
  • The local MCP server must be available as a runnable command.
Documentation 1 ↗
Evidence and transparency

Sources & review

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