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
    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

    6 related tools
    Anki MCP Server

    Anki MCP Server

    A Model Context Protocol (MCP) server that enables AI assistants to interact with Anki, the spaced repetition flashcard application. The Anki MCP Server allows AI models to access Anki's card data, enabling features like automated flashcard creation, review, and management.

    1MCP Agent

    1MCP Agent

    A unified Model Context Protocol server implementation that aggregates multiple MCP servers into one. The 1mcp-app/agent is an open-source project that provides a single entry point for multiple MCP servers, making it easier to manage and interact with various AI models and tools.

    Roundtable AI MCP Server

    Roundtable AI MCP Server

    Roundtable AI MCP Server is a zero-configuration local MCP server that unifies multiple AI coding assistants (Codex, Claude Code, Cursor, Gemini) through intelligent auto-discovery and a standardized interface. It coordinates specialized sub-agents from within your IDE to solve engineering problems in parallel, sharing context and synthesizing responses into a single, high-quality output. This documentation details installation, available MCP tools, integration with popular IDEs, and a broad ecosystem of specialized tools and CLIs that can be invoked as part of a roundtable-powered workflow, enabling developers to delegate tasks to the right AI for each facet of a problem without leaving their development environment.

    MCPJungle

    MCPJungle

    MCPJungle is a self-hosted MCP Gateway and Registry for AI agents. It serves as a central registry and gateway to manage Model Context Protocol (MCP) servers and the tools they expose. By consolidating MCP server registration, tool discovery, and access control, MCPJungle enables AI agents and clients to discover, group, and securely invoke tools from a single, unified gateway. The project provides a CLI, Docker-based deployment options, and enterprise-ready features such as tool grouping, access control, and observability to streamline MCP-based workflows across organizations.

    mcpmcp-server

    mcpmcp-server

    mcpmcp-server is a focused solution for discovering, setting up, and integrating MCP servers with your favorite clients to unlock AI-powered workflows. It streamlines how you connect MCP-powered servers to popular clients, enabling seamless AI-assisted interactions across your daily tools. The project emphasizes an approachable, config-driven approach to linking MCP servers with clients like Claude Desktop, while directing you to the homepage for variations across apps and platforms. This README highlights a practical JSON configuration example and notes on supported environments, helping you get started quickly and confidently.

    Imagen3-MCP

    Imagen3-MCP

    Imagen3-MCP is an image generation service based on Google's Imagen 3.0 that exposes its functionality through MCP (Model Control Protocol). The project provides a server to run a local MCP service that accesses Google Gemini-powered image generation, enabling developers to integrate advanced image synthesis into their applications. The documentation covers prerequisites (Gemini API key), installation steps for Cherry Studio, and a Cursor-based JSON configuration example for embedding the MCP server in broader tooling. This MCP is designed to be deployment-friendly, with configurable environment variables and optional proxy settings to adapt to various network environments.