MCP SSE Proxy

Bridges STDIO MCP clients to remote SSE MCP servers, enabling access to tools, resources, templates, and prompts via HTTP(S).

javascript

9

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

You can connect STDIO-based MCP clients to remote MCP servers that expose SSE endpoints by using the MCP SSE Proxy. It bridges local, console-driven clients with remote servers over HTTP/S, enabling you to leverage remote MCP capabilities without changing your client software.

How to use

Run the proxy from your terminal and point it at the remote SSE MCP server. You provide a server name, the SSE URL, and an optional API key when you launch the process. The proxy will accept STDIO connections from your MCP client and translate them to SSE requests to the remote server, then relay responses back to you.

How to install

Prerequisites: you need Node.js version 18.0.0 or newer and npm or yarn.

Install dependencies for the proxy projects you plan to run locally.

Run the proxy server instance using the provided command line.

Configuration and usage details

Authentication is optional. If you provide an API key, the proxy sends it as a Bearer token in HTTP requests and in EventSource connections.

The proxy supports all MCP capabilities exposed by the remote SSE server, including Tools, Resources, Resource Templates, and Prompts. You can configure your MCP client to target this proxy as if it were a local STDIO MCP server that forwards requests to the remote SSE server.

Troubleshooting and notes

Common issues include connection failures to the remote SSE server, invalid URLs, authentication errors, and problems when the remote server doesn’t provide expected MCP capabilities. Enable verbose logging to see connection status, request/response details, and error stack traces. When terminating, the proxy performs a graceful shutdown to clean up resources.

Security considerations

When using an API key, protect the key as you would any credential. Do not expose it in client code or in shared configuration files. The proxy forwards the API key to the remote server in a secure manner over HTTP/S.

Example startup command

node server/index.js "My Remote MCP Server" "https://api.example.com/mcp/sse" "your-api-key"

Available tools

Tools

List and invoke MCP tools available on the remote SSE server.

Resources

List and read MCP resources exposed by the remote server.

ResourceTemplates

List resource templates provided by the remote server.

Prompts

List and fetch prompts from the remote MCP server.