MCP Access Point is a lightweight protocol conversion gateway tool designed to establish a communication bridge between traditional HTTP services and MCP (Model Context Protocol) clients. It enables MCP clients to interact directly with existing HTTP services without requiring any server-side interface modifications.
Turn a web server into an MCP server in one click without making any code changes.
Sterne
184
Tools
—
Uptime
—
Introduction
This project is built on Pingora - an ultra-high performance gateway proxy library capable of supporting massive-scale request proxy services. Pingora has been used to build services that handle core traffic for the Cloudflare platform, consistently serving over 40 million requests per second across the internet for years. It has become the technical cornerstone supporting a significant proportion of traffic on the Cloudflare platform.
HTTP to MCP
This mode allows clients like Cursor Desktop to communicate with remote HTTP servers through SSE, even when the servers themselves don't support the SSE protocol.
Example setup includes two services:
Service 1 runs locally at 127.0.0.1:8090
Service 2 runs remotely at api.example.com
Through the MCP Access Point, both services can be converted to MCP services without any code modifications.
Clients communicate with Service 1 and Service 2 via the MCP protocol. The MCP Access Point automatically distinguishes MCP requests and forwards them to the appropriate backend services.
graph LR
A["Cursor Desktop"] <--> |SSE| B["MCP Access Point"]
A2["Other Desktop"] <--> |Streamable Http| B["MCP Access Point"]
B <--> |http 127.0.0.1:8090| C1["Existing API Server"]
B <--> |https//api.example.com| C2["Existing API Server"]
style A2 fill:#ffe6f9,stroke:#333,color:black,stroke-width:2px
style A fill:#ffe6f9,stroke:#333,color:black,stroke-width:2px
style B fill:#e6e6af,stroke:#333,color:black,stroke-width:2px
style C1 fill:#e6ffe6,stroke:#333,color:black,stroke-width:2px
style C2 fill:#e6ffd6,stroke:#333,color:black,stroke-width:2px
Transport Type (Specification)
Currently supports SSE and Streamable HTTP protocols:
✅ Streamable HTTP (stateless) 2025-03-26
All services: ip:port/mcp
Single service: ip:port/api/{service_id}/mcp
✅ SSE 2024-11-05
All services: ip:port/sse
Single service: ip:port/api/{service_id}/sse
use IP:PORT/sse for SSE
use IP:PORT/mcp for Streamable HTTP
Protocol Conversion: Seamless conversion between HTTP and MCP protocols
Zero-Intrusive Integration: Full compatibility with existing HTTP services
Client Empowerment: Enables MCP clients to directly call standard HTTP services
Lightweight Proxy: Minimalist architecture with efficient protocol conversion
Multi-tenancy: Independent configuration and endpoints for each tenant
Runtime Configuration Management: Dynamic configuration updates without service restart
Admin API: RESTful API for real-time configuration management
Quick Start
Installation
# Install from source
git clone https://github.com/sxhxliang/mcp-access-point.git
cd mcp-access-point
cargo run -- -c config.yaml
# Use inspector for debugging (start service first)
npx @modelcontextprotocol/inspector node build/index.js
# Access http://127.0.0.1:6274/
# Select "SSE" and enter 0.0.0.0:8080/sse, then click connect
# or select "Streamable HTTP" and enter 0.0.0.0:8080/mcp
Multi-tenancy Support
The MCP Access Gateway supports multi-tenancy, where each tenant can configure multiple MCP services accessible via:
/api/{mcp-service-id}/sse (for SSE)
/api/{mcp-service-id}/mcp (for Streamable HTTP)
Example configuration:
# config.yaml example (supports multiple services)
mcps:
- id: service-1 # Access via /api/service-1/sse or /api/service-1/mcp
... # Service configuration
- id: service-2 # Access via /api/service-2/sse or /api/service-2/mcp
... # Service configuration
- id: service-3 # Access via /api/service-3/sse or /api/service-3/mcp
... # Service configuration
To access all services simultaneously, use:
0.0.0.0:8080/mcp (Streamable HTTP)
0.0.0.0:8080/sse (SSE)
Configuration Details
-c config.yaml
-c (or --config) specifies the configuration file path (config.yaml).
This file defines the APIs that the MCP Access Point will proxy and convert.
config.yaml Example
The configuration file supports multi-tenancy, allowing independent configuration of upstream services and routing rules for each MCP service. Key configuration items include:
mcps - MCP service list
id: Unique service identifier used to generate access paths
upstream_id: Associated upstream service ID
path: OpenAPI specification file path. Supports local files (e.g., config/openapi.json) and remote HTTP/HTTPS URLs (e.g., https://petstore.swagger.io/v2/swagger.json). Both JSON and YAML formats are supported.
routes: Custom routing configuration (optional)
upstream: Upstream service specific configuration (optional)
# Using environment variables (service running on host)
# Note: Replace /path/to/your/config.yaml with 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 \
liangshihua/mcp-access-point:latest
Environment Variables
port: MCP Access Point listening port (default: 8080)
Typical Use Cases
Progressive Architecture Migration: Facilitate gradual transition from HTTP to MCP
Hybrid Architecture Support: Reuse existing HTTP infrastructure within MCP ecosystem
Protocol Compatibility: Build hybrid systems supporting both protocols
Example Scenario:
When MCP-based AI clients need to interface with legacy HTTP microservices, the MCP Access Gateway acts as a middleware layer enabling seamless protocol conversion.
The MCP Access Point now supports dynamic configuration management through a RESTful Admin API, allowing you to update configurations without restarting the service.
Admin API Features
Real-time Configuration Updates: Modify upstreams, services, routes, and other resources on-the-fly
Dependency Validation: Automatic validation of resource dependencies before changes
Configuration Validation: Dry-run mode to validate changes before applying
Resource Statistics: Monitor and track configuration state
Admin API Configuration
Add the following to your config.yaml to enable the Admin API:
access_point:
admin:
address: "127.0.0.1:8081" # Admin API listening address
api_key: "your-api-key" # Optional API key for authentication
Admin API Endpoints
Resource Management
GET /admin/resources - Get resource summary and statistics
GET /admin/resources/{type} - List all resources of a specific type
GET /admin/resources/{type}/{id} - Get a specific resource
POST /admin/resources/{type}/{id} - Create a new resource
PUT /admin/resources/{type}/{id} - Update an existing resource
DELETE /admin/resources/{type}/{id} - Delete a resource
Advanced Operations
POST /admin/validate/{type}/{id} - Validate resource configuration
POST /admin/batch - Execute batch operations
POST /admin/reload/{type} - Reload a specific resource type
POST /admin/reload/config - Reload full configuration from file (defaults to config.yaml). Optional JSON body: { "config_path": "path/to/config.yaml" }
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Fragen
Wie installiere ich MCP Access Point?
Kopieren Sie auf dieser Seite die stdio-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Benötigt MCP Access Point einen API-Schlüssel?
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Welchen Transport verwendet MCP Access Point?
MCP Access Point läuft lokal über stdio.
Wann wurde MCP Access Point zuletzt geprüft?
Zuletzt geprüft: 2026-10-28. Turn a web server into an MCP server in one click without making any code changes.