LABSCO SUMMARY

The REST-to-MCP wrapper is the working half.

The repo is explicit about where it stands: the gateway server, the REST API, the API wrapper and the admin UI are described as working, while federating several MCP servers into one endpoint is described as a framework that still needs client integration. Install it for the wrapper — a REST API you already have, reachable as a tool — and treat federation as work in progress.

What it is

A Python gateway that sits between MCP clients and the things you want them to reach. It exposes MCP operations over a REST API, wraps existing HTTP endpoints as callable tools, and ships an admin UI for registering servers and wrappers.

What you get

REST endpoints under /api/v1 for the core MCP operations — list and call tools, list and get prompts, list and read resources
An API wrapper that converts a REST endpoint into an MCP tool from a declaration of base URL, auth type and endpoint definitions
Admin endpoints to add, update and remove MCP servers and API wrappers at /admin
A WebSocket endpoint at /api/v1/ws that accepts MCP JSON-RPC messages
An admin dashboard and an OpenAPI/Swagger UI at /docs
A bundled sample MCP server with a note store, a summarize-notes prompt and an add-note tool

Requirements

Python 3.10 or higher and uv (or pip install -e .). Start it with uv run python -m mcpilot.main, or run it under uvicorn; it listens on port 8000 by default. Configuration comes from environment variables or a .env file — MCPILOT_HOST, MCPILOT_PORT, MCPILOT_DEBUG, MCPILOT_CORS_ORIGINS and MCPILOT_LOG_LEVEL. MIT licensed.

Setup effort

Build from source

See installation options

USE CASES

01

Exposing an internal REST API to an assistant without writing a server

Declare the base URL, auth and endpoints; the gateway registers each endpoint as a callable tool.

02

Driving MCP operations from ordinary HTTP

List and call tools over /api/v1 from any language that can POST JSON, no MCP client library needed.

03

Trying MCP plumbing end to end on one machine

Start the gateway, open the Swagger UI, and call the bundled note-store tools to see the request and response shapes.

1 tool

Listed in project docs. Your client may show a different list.

add-note

BEFORE YOU INSTALL

What to know first

Tools you get

1 tool named in the project's documentation.

Requires

Python 3.10 or higher

Where it runs

The documented client runs the server on your machine.

INSTALLATION

Connect your client

Server setup

TERMINAL

git clone https://github.com/ferrary7/MCPilot
cd MCPilot
uv sync
uv run python -m mcpilot.main

MCP Clients

Claude Desktop

CLAUDE DESKTOP · JSON

{
  "mcpServers": {
    "MCPilot": {
      "command": "uv",
      "args": [
        "--directory",
        "<YOUR_PATH_TO_MC_PILOT>",
        "run",
        "mcpilot"
      ]
    }
  }
}

<YOUR_PATH_TO_MC_PILOT> is the full path of your clone. This starts the bundled MCP server (the note store with add-note) over stdio; the uv run python -m mcpilot.main step starts the HTTP gateway and admin dashboard on port 8000, which MCP clients do not connect to through this block.

MCPilot