MCP Proxy MCP Server

A TypeScript streamable HTTP and SSE proxy for MCP servers that use stdio transport.

Local serverstdio

What is the MCP Proxy MCP server?

Connect MCP Proxy to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A TypeScript streamable HTTP and SSE proxy for MCP servers that use stdio transport. The mcp proxy mcp server is what makes that connection.

What the server does

The mcp-proxy is a tool that lets you switch between server transports. There are two supported modes:

Installation

The server ships on PyPI as mcp-server-fetch, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Troubleshooting — The Troubleshooting tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: API_ACCESS_TOKEN, GITHUB_PERSONAL_ACCESS_TOKEN, YOUR_TOKEN, FILE_PATH, CLIENT_ID, CLIENT_SECRET, TOKEN_URL, ANOTHER_KEY. 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.

Worth knowing first

  • 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.
  • 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.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Proxy's toolset — Troubleshooting — is a fair guide to whether it matches your workflow. It is maintained by punkpeye; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
TroubleshootingThe Troubleshooting tool exposed by this server.

How to install the MCP Proxy MCP server

{
  "mcpServers": {
    "mcp-proxy": {
      "command": "mcp-proxy",
      "args": [
        "http://example.io/sse"
      ],
      "env": {
        "API_ACCESS_TOKEN": "access-token"
      }
    }
  }
}

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

Configuration

VariableDescriptionRequired
API_ACCESS_TOKENCredential the server authenticates with.Yes
GITHUB_PERSONAL_ACCESS_TOKENCredential the server authenticates with.Yes
YOUR_TOKENCredential the server authenticates with.Yes
FILE_PATHFilesystem location the server is allowed to use.Optional
CLIENT_IDConfiguration value read at startup.Optional
CLIENT_SECRETCredential the server authenticates with.Yes
TOKEN_URLCredential the server authenticates with.Yes
ANOTHER_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP Proxy to Troubleshooting.

Frequently asked questions

No, it works with any stdio-based MCP server without modifications. The proxy handles the protocol translation.