MCP MCP Server

Fast rust MCP proxy between stdio and SSE

Local serverstdioPython

What is the MCP MCP server?

MCP MCP server exists for a simple reason — assistants are far more useful when they can act on MCP directly instead of describing what you should do. Fast rust MCP proxy between stdio and SSE.

What you get

Connect to a remote MCP server and expose it as a local stdio server. Supports both SSE and Streamable HTTP transports with automatic detection.

  • Multiple transports — SSE and Streamable HTTP
  • OAuth authentication — Full OAuth flow with automatic token refresh
  • Bidirectional proxy — Connect remote servers to local clients or expose local servers remotely
  • Fast and lightweight — Built in rust for performance

What the assistant can call

Once MCP is connected, these are the calls the assistant has available:

  • Installing — The Installing tool exposed by this server
  • Building — The Building tool exposed by this server
  • Running — The Running tool exposed by this server
  • Logging — Control log verbosity with the RUST_LOG environment variable:

Setting it up

The server ships on npm as @modelcontextprotocol/server-everything, 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.

Configuration and credentials

You will need one environment variable: ANOTHER_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP's toolset — Installing, Building, Running and 1 more — is a fair guide to whether it matches your workflow. It is maintained by stephenlacy; worth a glance at recent repository activity before you build anything load-bearing on it.

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

Before you rely on it

  • 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.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
InstallingThe Installing tool exposed by this server.
BuildingThe Building tool exposed by this server.
RunningThe Running tool exposed by this server.
LoggingControl log verbosity with the RUST_LOG environment variable:

How to install the MCP MCP server

##### Using with Claude or Cursor

```json
{
  "mcpServers": {
    "my-remote-server": {
      "command": "mcp-proxy",
      "args": ["http://example.com/mcp/instances_abc123"]
    },
    "sse-server": {
      "command": "mcp-proxy", 
      "args": ["--transport", "sse", "http://example.com/sse"]
    }
  }
}

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

Configuration

VariableDescriptionRequired
ANOTHER_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP to Installing.
  • Use MCP to Building.
  • Use MCP to Running.

Frequently asked questions

SSE (Server-Sent Events) and Streamable HTTP.