MCP Access Point Details

MCP Access Point is a lightweight gateway that turns existing HTTP services into MCP (Model Context Protocol) endpoints with zero code changes. Built on high-performance Pingora proxy, it enables seamless protocol conversion between HTTP and MCP, supporting both SSE and Streamable HTTP. Designed for multi-tenant deployments, it offers a RESTful Admin API for real-time configuration management, dynamic updates, and resource administration without restarting the service. This repository provides a clear Quick Start, multi-tenancy guidance, and admin operations to manage upstreams, services, routes, and more, making it easy to expose legacy HTTP APIs to MCP clients like Cursor Desktop and MCP Inspectors.

Use Case

Use MCP Access Point to bridge existing HTTP services into the MCP ecosystem. It supports multi-tenancy, dynamic runtime configuration, and admin-controlled resource management. Example use case: you have several internal HTTP microservices and want to expose them to MCP clients without touching code. Define mcps and upstreams in config.yaml, start the gateway, and optionally manage configurations via the Admin API. Key workflow includes configuring routes with operation_id, such as get_weather, to map MCP operations to backend HTTP endpoints. Example from the docs: - operation_id: get_weather - uri: /points/{latitude},{longitude} - method: GET - meta includes name: Get Weather and description with inputSchema enforcing latitude and longitude ranges.

Available Tools (1)

Examples & Tutorials

From the documentation:

Config snippet showing a route using operation_id get_weather:

<h1 class="text-2xl font-semibold mt-5 mb-3">config.yaml example (supports multiple services)</h1>
mcps:
  • id: service-1 # Unique identifier, accessible via /api/service-1/sse or /api/service-1/mcp

  • upstream_id: 1
    path: config/openapi_for_demo_patch1.json # Local OpenAPI spec path
  • id: service-2 # Unique identifier

  • upstream_id: 2
    path: https://petstore.swagger.io/v2/swagger.json # Remote OpenAPI spec
  • id: service-3

  • upstream_id: 3
    routes: # Custom routing
  • id: 1

  • operation_id: get_weather
    uri: /points/{latitude},{longitude}
    method: GET
    meta:
    name: Get Weather
    description: Retrieve weather information by coordinates
    inputSchema: # Optional input validation
    type: object
    required:
  • latitude

  • longitude

  • properties:
    latitude:
    type: number
    minimum: -90
    maximum: 90
    longitude:
    type: number
    minimum: -180
    maximum: 180

    upstreams: # Required upstream configuration

  • id: 1

  • headers: # Headers to send to upstream service
    X-API-Key: "12345-abcdef" # API key
    Authorization: "Bearer token123" # Bearer token
    User-Agent: "MyApp/1.0" # User agent
    Accept: "application/json" # Accept header
    nodes: # Backend nodes (IP or domain)
    "127.0.0.1:8090": 1 # Format: address:weight

    To run:

    cargo run -- -c config.yaml

    Quick Start (from docs):

    <h1 class="text-2xl font-semibold mt-5 mb-3">Install from source</h1>
    git clone https://github.com/sxhxliang/mcp-access-point.git
    cd mcp-access-point
    cargo run -- -c config.yaml

    <h1 class="text-2xl font-semibold mt-5 mb-3">Use inspector for debugging (start service first)</h1>
    npx @modelcontextprotocol/inspector node build/index.js
    <h1 class="text-2xl font-semibold mt-5 mb-3">Access http://127.0.0.1:6274/</h1>
    <h1 class="text-2xl font-semibold mt-5 mb-3">Select "SSE" and enter 0.0.0.0:8080/sse, then click connect</h1>
    <h1 class="text-2xl font-semibold mt-5 mb-3">or select "Streamable HTTP" and enter 0.0.0.0:8080/mcp</h1>

    Running via Docker (examples):

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

    Environment variable reference:

    - port: MCP Access Point listening port (default: 8080)

    Installation Guide

    Step-by-step (from the documentation):

    1) Install from source

    <h1 class="text-2xl font-semibold mt-5 mb-3">Install from source</h1>
    git clone https://github.com/sxhxliang/mcp-access-point.git
    cd mcp-access-point
    cargo run -- -c config.yaml

    2) Quick Start commands for debugging with Inspector

    <h1 class="text-2xl font-semibold mt-5 mb-3">Use inspector for debugging (start service first)</h1>
    npx @modelcontextprotocol/inspector node build/index.js
    <h1 class="text-2xl font-semibold mt-5 mb-3">Access http://127.0.0.1:6274/</h1>
    <h1 class="text-2xl font-semibold mt-5 mb-3">Select "SSE" and enter 0.0.0.0:8080/sse, then click connect</h1>
    <h1 class="text-2xl font-semibold mt-5 mb-3">or select "Streamable HTTP" and enter 0.0.0.0:8080/mcp</h1>

    3) Docker run example

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

    4) Docker image build (optional)

    <h1 class="text-2xl font-semibold mt-5 mb-3">Clone repository</h1>
    git clone https://github.com/sxhxliang/mcp-access-point.git
    cd mcp-access-point

    <h1 class="text-2xl font-semibold mt-5 mb-3">Build image</h1>
    docker build -t liangshihua/mcp-access-point:latest .

    5) Environment variable reference

    - port: MCP Access Point listening port (default: 8080)

    Frequently Asked Questions

    Is this your MCP?

    Claim ownership and get verified badge

    Repository Stats

    Sponsored

    Ad Space Available
    Important Notes

    Notes and important points from the documentation:

  • MCP Access Point supports multi-tenancy and dynamic runtime configuration via the Admin API.

  • The Admin API runs on port 8081 by default (see example in Admin API configuration).

  • Admin API endpoints allow resource management, batch operations, and reloading configurations.

  • The default public port for the MCP Access Point is 8080 unless overridden via -e port or in config.yaml.

  • The system supports both SSE and Streamable HTTP modes for MCP clients.

  • Configuration is provided via a config.yaml file (mcps and upstreams sections).

  • You can reload the full configuration from file using the Admin API (POST /admin/reload/config) with optional config_path in the body.

  • The README provides concrete examples for creating resources, batch operations, and getting resource statistics via the Admin API.

  • Prerequisites

    Rust toolchain with Cargo and Git are required. The Quick Start shows cloning the repository and starting the service with a config.yaml, or using Docker to run the prebuilt image. Optional: Inspector for debugging via Node.js (npx @modelcontextprotocol/inspector).

    Details
    Last Updated1/1/2026
    SourceGitHub

    Compare Alternatives

    Similar MCP Tools

    9 related tools
    Skyvern MCP

    Skyvern MCP

    Skyvern is the complete browser MCP for AI agents. 75+ tools for clicking, filling forms, extracting structured data, logging in with 2FA, uploading files, drag-and-drop, running JavaScript, inspecting network traffic, multi-tab browsing, and building reusable cached workflows. First workflow run uses AI; subsequent runs replay a cached script with zero LLM calls.

    pageguard-mcp

    pageguard-mcp

    pageguard-mcp is an MCP (Model Context Protocol) server that exposes PageGuard privacy compliance scanning as a set of tools for AI coding assistants. It enables seamless integration with Claude Code, Cursor, Windsurf, ChatGPT, and any MCP-compatible environment. The server supports local scans, live URL scans, and AI-generated privacy-related documents, helping developers identify tracking technologies, cookies, and third-party data processing, while also producing tailored privacy policies and compliance materials. With its straightforward MCP configuration and free local scanning capability, pageguard-mcp is designed to empower teams to maintain privacy compliance across their projects and websites.

    Prop Firm Deal Finder

    Prop Firm Deal Finder (PFDF) is a free MCP server that gives AI assistants real-time access to live discount codes across 20+ proprietary trading firms. It provides 6 tools: get_deals (all current discounts), search_firms (search by name/asset class), compare_firms (side-by-side comparison of challenges), find_cheapest (cheapest challenge by account size with PFDF code applied), get_firm_details (15+ data points per firm), and get_discount_code (universal PFDF code). Covers firms like Topstep, Apex Trader Funding, MyFundedFutures, FTMO, The Funded Trader, and 14 more. No API key required. Install via npx propfirmdealfinder-mcp-server or connect remotely at https://web-production-6607c.up.railway.app/mcp

    mcp-server-with-spring-ai

    mcp-server-with-spring-ai

    mcp-server-with-spring-ai is a Spring Boot integrated MCP (Model Context Protocol) server example that showcases how to expose executable tools from an MCP server to clients (including LLMs) and how to wire a MCP client to consume those tools. The documentation explains MCP at a high level, outlines the three-layer MCP Java SDK architecture (Client/Server Layer, Session Layer, Transport Layer), and demonstrates two sample tools implemented in SellerAccountTools. This repo emphasizes how an MCP server can connect to external data sources (e.g., a PostgreSQL DB) and expose tools that an AI model can invoke to retrieve data, with the example illustrating tool invocation and automatic tool selection by prompts.

    OpenClaw MCP Server

    OpenClaw MCP Server

    OpenClaw MCP Server is a secure Model Context Protocol (MCP) bridge that connects Claude.ai with a self-hosted OpenClaw assistant, enabling OAuth2 authentication and safe, controlled communication between the Claude AI ecosystem and your local or hosted OpenClaw deployment. This MCP server acts as an orchestration layer that exposes MCP tools to Claude.ai, manages authentication, and enforces security boundaries like CORS and transport options. It is designed to be deployed via Docker or run locally, with detailed installation, configuration, and security guidance provided in the documentation. By serving as a bridge, it enables Claude.ai to delegate tasks to your OpenClaw bot while preserving control over data flow and access controls, in line with MCP specifications and best security practices.

    Graphiti MCP Server

    Graphiti MCP Server

    Graphiti MCP Server is an experimental implementation that exposes Graphiti's real-time, temporally-aware knowledge graph capabilities through the MCP (Model Context Protocol) interface. It enables AI agents and MCP clients to interact with Graphiti's knowledge graph for structured extraction, reasoning, and memory across conversations, documents, and enterprise data. The server supports multiple backends (FalkorDB by default and Neo4j), a variety of LLM providers (OpenAI, Anthropic, Gemini, Groq, Azure OpenAI), and multiple embedder options, all accessible via an HTTP MCP endpoint at /mcp/ for broad client compatibility. It also includes queue-based asynchronous episode processing, rich entity types for structured data, and flexible configuration through config.yaml, environment variables, or CLI arguments.

    Context7 MCP Server

    Context7 MCP Server

    Context7 MCP Server delivers up-to-date, code-first documentation and examples for LLMs and AI code editors by pulling content directly from the source. It supports multiple MCP clients and exposes tools that help you resolve library IDs and retrieve library documentation, ensuring prompts use current APIs and usage patterns. The repository provides installation and integration guides for Cursor, Claude Code, Opencode, and other clients, along with practical configuration samples and OAuth options for remote HTTP connections. This MCP server is designed to keep prompts in sync with the latest library docs, reducing hallucinations and outdated code snippets.

    TrendRadar MCP

    TrendRadar MCP

    TrendRadar MCP is an AI-driven Model Context Protocol (MCP) based analysis server that exposes a suite of specialized tools for cross-platform news analysis, trend tracking, and intelligent push notifications. It integrates with TrendRadar’s multi-platform data aggregation (RSS and trending topics) and provides advanced AI-powered insights, sentiment analysis, and cross-platform correlation. The MCP server enables developers to query, analyze, and compare news across platforms using a consistent toolset, with ongoing updates that expand capabilities such as RSS querying, date parsing, and multi-date trend analysis. This documentation references the MCP module updates, tool additions, and architecture changes that enhance extensibility, cross-platform data handling, and AI-assisted reporting.

    ChainAware Behavioural Prediction MCP

    ChainAware Behavioural Prediction MCP

    The ChainAware Behavioural Prediction MCP is an MCP-based server that provides AI-powered tools to analyze wallet behaviour prediction, fraud detection, and rug pull prediction. Designed for Web3 security and DeFi analytics, it enables developers and platforms to integrate risk assessment, predictive wallet behavior insights, and rug-pull detection through MCP-compatible clients. The server exposes three specialized tools and uses Server-Sent Events (SSE) for real-time responses, helping safeguard DeFi users, monitor liquidity risks, and score wallet or contract trustworthiness. Access to production endpoints is API-key gated, reflecting a private backend architecture that supports secure, scalable risk analytics across wallets, contracts, and pools.