MCP2HTTP

by tekorex

2 stars

278 downloads

Not rated

GitHub

Other

About

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

Details

Author: tekorex
GitHub stars: 2
Downloads: 278
Categories: Other

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

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name MCP2HTTP

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

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

JSON

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

JSON

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

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

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

JSON

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

JSON

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

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

From the repository

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.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

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

McpServers

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

MCP2HTTP

A minimal transport adapter for connecting stdio MCP clients to stateless HTTP MCP servers.

Overview

MCP2HTTP enables Model Context Protocol clients using stdio transport to communicate with MCP servers over stateless HTTP. While MCP typically uses either stdio (for local processes) or Server-Sent Events (SSE) transport, this adapter bridges to regular HTTP endpoints, enabling new integration possibilities. The adapter only handles basic transport layer conversion while providing optional state tracking through a client-generated UUID Session-Id header. It preserves protocol semantics, allowing clients and servers to interact directly without the need for SSE, thus working seamlessly with serverless platforms and legacy systems.

Usage

Configure your MCP client to call this command with arguments in this format: ``

sh
npx -y mcp2http <endpoint-url> ["Header: Value"...]



For example, in your Claude Desktop configuration file (

claude_desktop_config.json

):

json
{
  "mcpServers": {
    "my-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp2http",
        "http://localhost:3000/mcp"
      ]
    }
  }
}



You may additionally include any number of HTTP headers as arguments. For example, to include an auth token:

json
{
  "mcpServers": {
    "my-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp2http",
        "https://example.com/mcp",
        "Authorization: Bearer token123"
      ]
    }
  }
}



You will need a functional MCP HTTP endpoint. An example server will be provided soon.

Features


Client-Generated Session Tracking


The adapter automatically generates a UUID and includes it as a

Session-Id header with each request. While having clients generate session IDs might seem counterintuitive, this aspect resembles a 1996 proposal for Session-Id

 never formally adopted into HTTP standards. This mechanism offers remarkable simplicity and is intended to complement (not replace) proper authentication.

The 128-bit hex UUID format provides collision resistance and leverages a ubiquitous identifier standard, making it ideal for correlating requests in stateless HTTP environments. To prevent fragmentation and ensure consistent behavior, server implementations conforming with this design should reject non-128-bit hex

Session-Id

 values (with or without dashes).

Servers can safely ignore the

Session-Id header entirely if they don't need session tracking.

 This feature is optional and provided as a convenience for implementations that want correlation between requests without additional complexity.

Capability Filtering


The adapter tracks server capabilities from the

initialize response and blocks requests for unsupported capabilities.

 This feature addresses an issue with some MCP clients that repeatedly poll for unadvertised capabilities several times per minute. By filtering these requests before they reach the server, this adapter reduces unnecessary load when a server only supports specific capabilities, i.e.

tools

, while the client silently continues its polling behavior.

Notification Handling


Notifications (messages with no ID) are silently dropped. This approach naturally aligns with HTTP's request/response architecture. When implementing MCP over stateless HTTP, dropping notifications emerges as a sensible choice, a conclusion reached by other implementations like the mcp-golang HTTP transport. While

notifications/initialized` may give pause, the practical benefits of consistent notification handling should triumph. Nevertheless, HTTP MCP servers may still desire to handle notifications gracefully, in case other implementations do forward them.

License

MIT

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

MCP2HTTP

About

Details

Jump to

Setting up with Highlight

Setting up with Cursor

JSON

JSON

JSON

Setting up with Claude Desktop

JSON

JSON

JSON

Setting up with Windsurf

JSON

JSON

JSON

Setting up with Cline

JSON

JSON

JSON

Setting up with Goose

JSON

JSON

JSON

From the repository

Claude Desktop / Cursor

McpServers

MCP2HTTP

Overview

Usage

Features

Client-Generated Session Tracking

Capability Filtering

Notification Handling

License

Install

About

Details

Jump to

Setting up with Highlight

From the repository

Claude Desktop / Cursor

McpServers

MCP2HTTP

Overview

Usage

Features

Client-Generated Session Tracking

Capability Filtering

Notification Handling

License

Install

More like this

Sequential Thinking

Filesystem

EverArt

Google Drive

Reactive Resume

FastMCP v2 🚀