MCP.so
Sign In

MCP2HTTP

@tekorex

About MCP2HTTP

MCP2HTTP is a minimal transport adapter that bridges MCP clients using stdio with stateless HTTP servers.

Basic information

Category

Other

License

MIT

Runtime

node

Transports

stdio

Publisher

tekorex

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp2http": {
      "command": "npx",
      "args": [
        "-y",
        "mcp2http",
        "<endpoint-url>",
        "[Header: Value...]"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP2HTTP?

MCP2HTTP is a minimal transport adapter that bridges Model Context Protocol (MCP) clients using stdio transport to stateless HTTP MCP servers. It replaces the typical SSE transport with plain HTTP, enabling integration with serverless platforms and legacy systems while preserving protocol semantics.

How to use MCP2HTTP?

Configure your MCP client to run npx -y mcp2http <endpoint-url> ["Header: Value"...]. Optional HTTP headers can be added as arguments (e.g., "Authorization: Bearer token123"). You need a functional MCP HTTP endpoint.

Key features of MCP2HTTP

  • Bridges stdio MCP clients to stateless HTTP servers.
  • Automatic client-generated UUID session tracking via Session-Id header.
  • Blocks requests for capabilities the server does not advertise.
  • Silently drops notification messages (no ID).
  • Supports custom HTTP headers via command-line arguments.

Use cases of MCP2HTTP

  • Connecting MCP clients to serverless or stateless HTTP endpoints.
  • Integrating MCP with legacy systems that lack SSE support.
  • Reducing unnecessary load by filtering unsupported capability polls.

FAQ from MCP2HTTP

What does MCP2HTTP do?

It converts stdio-based MCP client communication to regular HTTP requests, allowing clients to talk to servers over stateless HTTP without SSE.

What are the dependencies or runtime requirements?

You need Node.js and npx (bundled with npm). The adapter is run via npx -y mcp2http.

How does session tracking work?

The adapter generates a UUID and adds it as a Session-Id header to every request. Servers may ignore this header; it is optional.

What happens to notification messages?

Notifications (messages with no ID) are silently dropped because they don’t fit HTTP’s request/response model.

Can I pass authentication headers?

Yes. Add any number of "Header: Value" arguments after the endpoint URL, e.g., "Authorization: Bearer token123".

Comments

More Other MCP servers