MCP Access Point

🚀 MCP Access Point

The MCP Access Point is a lightweight protocol conversion gateway tool designed to bridge the communication between traditional HTTP services and MCP (Model Context Protocol) clients. It enables MCP clients to directly interact with existing HTTP services without any modifications to the server-side interfaces.

🚀 Quick Start

The MCP Access Point is a tool that simplifies the interaction between MCP clients and traditional HTTP services. It acts as a bridge, allowing seamless communication without server-side changes.

✨ Features

Protocol Conversion

Seamlessly convert between HTTP and MCP protocols.

Zero-intrusive Integration

Fully compatible with existing HTTP services.

Client Enhancement

Empower MCP clients to directly call standard HTTP services.

Lightweight Proxy

Simple architecture for efficient protocol conversion.

📦 Installation

Build the Docker Image (Optional)

# Clone the repository
git clone https://github.com/sxhxliang/mcp-access-point.git
cd mcp-access-point

# Build the image
docker build -t liangshihua/mcp-access-point:latest .

Start the Docker Container

# Use environment variables (service runs on the host)
# Note: Replace /path/to/your/config.yaml with the actual path

docker run -d --name mcp-access-point --rm \
  -p 8080:8080 \
  -e port=8080 \
  -v /path/to/your/config.yaml:/app/config/config.yaml \
  sxhxliang/mcp-access-point:latest

Environment Variables

• port: The port on which the MCP Access Point listens (default: 8080).

💻 Usage Examples

HTTP to MCP

This mode allows clients like Cursor Desktop to communicate with remote HTTP servers via SSE (Server-Sent Events), even if the servers do not support the SSE protocol natively.

• Example setup includes two services:
  • Service 1 runs locally on localhost:8000.
  • Service 2 runs on a cloud server at example.com:9000.
• Clients can interact with these HTTP services through the MCP Access Point without dealing with the complexity of protocol conversion.

📚 Documentation

Typical Use Cases

• Gradual Architecture Migration: Support a smooth transition from HTTP to MCP.
• Hybrid Architecture Support: Reuse existing HTTP infrastructure in the MCP ecosystem.
• Protocol Compatibility: Build hybrid systems that support both protocols.

Example Scenario: When an MCP-based AI client needs to interface with legacy HTTP microservices, the MCP Access Gateway acts as an intermediary layer for seamless protocol conversion.

Project Foundation

This project is built on Pingora, a cost-effective gateway proxy library that supports large-scale request proxy services. Pingora has been used to build services that handle the core traffic of the Cloudflare platform, stably supporting over 40 million requests per second on the Internet for many years. It has become the technological foundation for a significant portion of the traffic on the Cloudflare platform.