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