KO
|
EN
gitlite — search
Search
#python
#java
#python3
#arduino
#golang
#machine-learning
#rust
#html
#flask
#javascript
#seismology
#nodejs
http-mcp-bridge
★ 17
Open GitHub ↗
No description available.
Download README (.md)
Explore Similar Repositories
OpenKWS
:
开源自定义唤醒词
lippia-mobile
:
No description available.
CMD
:
No description available.
WebGS
:
webgpu implementation of 3D/4D gaussian viewer
tide
:
Typst IDE
// repository documentation
Was this content helpful?
★ 0
(0 ratings)
Select Rating:
★
★
★
★
★
Submit Feedback
Recent Feedback
×
Download README
Do you want to download the
README.md
file for
http-mcp-bridge
?
Download (.md)
# HTTP MCP Bridge This project implements an HTTP server that acts as a bridge between HTTP/1.1 requests and a remote MCP server, using the `mcp` python library ([GitHub](https://github.com/modelcontextprotocol/python-sdk/)). The main purpose of this initiative is to be able to use HTTP security tools to test remote MCP servers using the remote transport mechanisms (HTTP+SSE or Streamable HTTP). ## IMPORTANT NOTE! It has been observed that when sending JSON-RPC-V2 messages with the same id, using concurrent threads, it may happen that responses are merged. Please keep that in mind when using the tool in your assessment. In the meanwhile we fix this issue, make sure that you are testing using a single thread. ## Installation To get started, clone the repository and install the required dependencies: ```bash git clone <repository-url> cd http-mcp-bridge pip install -r requirements.txt ``` ## Running The Bridge To run the HTTP server, execute the following command: ```bash python3 main.py --remote-url="http://127.0.0.1:8787/mcp" ``` The HTTP server will be listening in the default interface and port (`http://127.0.0.1:8000`), and the MCP connection will be established to the provided remote URL. A remote MCP server implementing a supported transport mechanism should exist in the given url. The HTTP server used to automatically detect the right transport mechanism, Streamable HTTP or HTTP+SSE, but it was creating issues with some production environments, so it is now disabled. It used the Streamable HTTP transport mechanism by default. We'll create a flag to enforce the usage of HTTP+SSE but, in the meanwhile, you can simply edit the code and enable that transport mechanism. You can then send HTTP requests to the server, which will relay them to the SSE/Streamable HTTP clients. ## Remote MCP Servers (for testing purposes) * [Cloudflare - Build a Remote MCP server](https://developers.cloudflare.com/agents/guides/remote-mcp-server/) ## Usage The mechanism implemented in the python SDK establishes a read channel and a write channel to communicate with the endpoint using the corresponding transport mechanism. This HTTP to MCP Bridge forwards HTTP requests to the write channel, and waits for the response (if applicable) in the read channel. Once received, that response is forwarded as the response of the HTTP request. HTTP requests support the parameter `timeout`, which limits the maximum amount of seconds that the bridge waits for the response in the read channel before returning and error message. If timeout is zero, the HTTP to MCP Bridge does not wait at all. ### Obtaining Bridge Session ID Since the HTTP to MCP Bridge supports several sessions with the MCP server, the first step is to obtain a session id, which will be used in further requests. Request: ```http GET /mcp/messages HTTP/1.1 Host: 127.0.0.1:8000 Accept-Encoding: gzip, deflate, br Connection: keep-alive User-Agent: python-httpx/0.28.1 Content-Type: application/json Cache-Control: no-store Content-Length: 0 ``` Response: ```http HTTP/1.1 400 Bad Request date: Fri, 02 May 2025 15:40:32 GMT server: uvicorn content-length: 87 content-type: application/json ``` ```json {"detail":"Invalid session id. Try /mcp/messages/7fc2cce5-3b0b-4d63-9df6-e703c1df091c"} ``` This session id is different and independent than the session id established between the MCP client and the server. The latter is handled by the `mcp` library under the hood. ### Ping There is a ping method than can be invoked to verify that the MCP service is there and the chosen transport mechanism is correct. Request: ```http POST /mcp/messages/7fc2cce5-3b0b-4d63-9df6-e703c1df091c HTTP/1.1 Host: 127.0.0.1:8000 Accept-Encoding: gzip, deflate, br Connection: keep-alive User-Agent: python-httpx/0.28.1 Content-Type: application/json Cache-Control: no-store Authorization: Bearer [REDACTED] Content-Length: 40 ``` ```json {"method":"ping","jsonrpc":"2.0","id":2} ``` Response: ```json [{"jsonrpc":"2.0","id":2,"result":{}}] ``` ### Initialization Handshake The first step in an MCP communication is the initialization handshake, where both peers share their available capabilities. Request: ```http POST /mcp/messages/7fc2cce5-3b0b-4d63-9df6-e703c1df091c HTTP/1.1 Host: 127.0.0.1:8000 Accept-Encoding: gzip, deflate, br Connection: keep-alive User-Agent: python-httpx/0.28.1 Content-Type: application/json Cache-Control: no-store Authorization: Bearer [REDACTED] Content-Length: 213 ``` ```json {"method": "initialize", "params": {"protocolVersion": "2024-11-05", "capabilities": {"sampling": {}, "roots": {"listChanged": true}}, "clientInfo": {"name": "mcp", "version": "0.1.0"}}, "jsonrpc": "2.0", "id": 0} ``` Response: ```json [{"jsonrpc":"2.0","id":0,"result":{"protocolVersion":"2024-11-05","capabilities":{"tools":{}},"serverInfo":{"name":"Demo","version":"1.0.0"}}}] ``` ### Handshake ACK Notification The handshake needs to be closed using this message, which does not have a response, so we can use `timeout=0` at this time. We will receive a timeout error message, but that is expected. Request: ```http POST /mcp/messages/7fc2cce5-3b0b-4d63-9df6-e703c1df091c?timeout=0 HTTP/1.1 Host: 127.0.0.1:8000 Accept-Encoding: gzip, deflate, br Connection: keep-alive User-Agent: python-httpx/0.28.1 Content-Type: application/json Cache-Control: no-store Authorization: Bearer [REDACTED] Content-Length: 54 ``` ```json {"method":"notifications/initialized","jsonrpc":"2.0"} ``` Response: ```json {"message":"Timeout waiting for messages"} ``` ### Tool Listing Once the handshake has been completed, we can invoke the methods available, such as `tools/list` (listing tools). Request: ```http POST /mcp/messages/7fc2cce5-3b0b-4d63-9df6-e703c1df091c HTTP/1.1 Host: 127.0.0.1:8000 Accept-Encoding: gzip, deflate, br Connection: keep-alive User-Agent: python-httpx/0.28.1 Content-Type: application/json Cache-Control: no-store Content-Length: 46 ``` ```json {"method":"tools/list","jsonrpc":"2.0","id":1} ``` Response: ```json [{"jsonrpc":"2.0","id":1,"result":{"tools":[{"name":"add","inputSchema":{"type":"object","properties":{"a":{"type":"number"},"b":{"type":"number"}},"required":["a","b"],"additionalProperties":false,"$schema":"http://json-schema.org/draft-07/schema#"}}]}}] ``` ### Tool Calling Finally, we can invoke tools or make use of other capabilities. Request: ```http POST /mcp/messages/7fc2cce5-3b0b-4d63-9df6-e703c1df091c HTTP/1.1 Host: 127.0.0.1:8000 Accept-Encoding: gzip, deflate, br Connection: keep-alive User-Agent: python-httpx/0.28.1 Content-Type: application/json Cache-Control: no-store Content-Length: 100 ``` ```json {"method":"tools/call","params":{"name":"add","arguments":{"a":1, "b":2 }},"jsonrpc":"2.0","id":2} ``` Response: ```json [{"jsonrpc":"2.0","id":2,"result":{"content":[{"type":"text","text":"3"}]}}] ``` ## Contributing Contributions are welcome! Please open an issue or submit a pull request for any enhancements or bug fixes. ## License This project is licensed under the MIT License. See the LICENSE file for more details.
