sxhxliang/mcp-access-point

Overview

This tool converts any existing web server into an MCP server without requiring code changes. It works by proxying HTTP requests through a Rust-based adapter that exposes the server's endpoints as MCP tools. Users can set it up with a single command, making it trivial to integrate legacy or third-party web services into MCP-compatible workflows.

Best for

Best for
Developers who need to quickly expose existing web services as MCP tools without modifying source code

Use cases

• Expose a REST API as an MCP tool for AI agents
• Integrate legacy web services with MCP clients without rewriting
• Quickly prototype MCP servers from existing HTTP endpoints

How to use

Install

cargo run -- -c config.yaml

Tested with

Cursor Desktop, Windsurf, VS Code, Trae

Example client config

mcps:\n  - id: service-1 # Unique identifier, accessible via /api/service-1/sse or /api/service-1/mcp\n    upstream_id: 1\n    path: config/openapi_for_demo_patch1.json # Local OpenAPI spec path\n  - id: service-2 # Unique identifier\n    upstream_id: 2\n    path: https://petstore.swagger.io/v2/swagger.json # Remote OpenAPI spec\n  - id: service-3 \n    upstream_id: 3\n    routes: # Custom routing\n      - id: 1\n        operation_id: get_weather\n        uri: /points/{latitude},{longitude}\n        method: GET\n        meta:\n          name: Get Weather\n          description: Retrieve weather information by coordinates\n          inputSchema: # Optional input validation\n            type: object\n            required:\n              - latitude\n              - longitude\n            properties:\n              latitude:\n                type: number\n                minimum: -90\n                maximum: 90\n              longitude:\n                type: number\n                minimum: -180\n                maximum: 180\nupstreams: # Required upstream configuration\n  - id: 1\n    headers: # Headers to send to upstream service\n      X-API-Key: "12345-abcdef"        # API key\n      Authorization: "Bearer token123" # Bearer token\n      User-Agent: "MyApp/1.0"          # User agent\n      Accept: "application/json"       # Accept header\n    nodes: # Backend nodes (IP or domain)\n      "127.0.0.1:8090": 1 # Format: address:weight\n  - id: 2 \n    nodes:\n      "127.0.0.1:8091": 1\n  - id: 3 \n    nodes:\n      "api.weather.gov": 1\n    type: roundrobin # Load balancing algorithm\n    scheme: https # Protocol\n    pass_host: rewrite # Host header handling\n    upstream_host: api.weather.gov # Override Host

Notes

This tool converts any existing web server into an MCP server without requiring code changes. It works by proxying HTTP requests through a Rust-based adapter that exposes the server’s endpoints as MCP tools. Users can set it up with a single command, making it trivial to integrate legacy or third-party web services into MCP-compatible workflows.

174 stars on GitHub. Last updated 2026-03-11. Licensed MIT.

Use cases

• Expose a REST API as an MCP tool for AI agents
• Integrate legacy web services with MCP clients without rewriting
• Quickly prototype MCP servers from existing HTTP endpoints

Pros

• No code modifications needed on the target web server
• One-click setup reduces integration friction
• Rust implementation offers low overhead and fast performance

Cons

• Only works with HTTP-based web servers, not other protocols
• May not handle complex authentication or streaming responses
• Relatively new project with limited community and documentation

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.