A community driven registry service for Model Context Protocol (MCP) servers.
This project is being built in the open and is currently in the early stages of development. Please see the overview discussion for the project scope and goals. If you would like to contribute, please check out the contributing guidelines.
The MCP Registry service provides a centralized repository for MCP server entries. It allows discovery and management of various MCP implementations with their associated metadata, configurations, and capabilities.
RESTful API for managing MCP registry entries (list, get, create, update, delete)
Health check endpoint for service monitoring
Support for various environment configurations
Graceful shutdown handling
MongoDB and in-memory database support
Comprehensive API documentation
Pagination support for listing registry entries
Go 1.18 or later
MongoDB
Docker (optional, but recommended for development)
The easiest way to get the registry running is to use docker compose. This will setup the MCP Registry service, import the seed data and run MongoDB in a local Docker environment.
# Build the Docker image
docker build -t registry .# Run the registry and MongoDB with docker compose
docker compose up
This will start the MCP Registry service and MongoDB with Docker, exposing it on port 8080.
If you prefer to run the service locally without Docker, you can build and run it directly using Go.
# Build a registry executable
go build ./cmd/registry
This will create the registry binary in the current directory. You'll need to have MongoDB running locally or with Docker.
By default, the service will run on http://localhost:8080.
├── api/ # OpenApi specification
├── cmd/ # Application entry points
├── config/ # Configuration files
├── internal/ # Private application code
│ ├── api/ # HTTP server and request handlers
│ ├── config/ # Configuration management
│ ├── model/ # Data models
│ └── service/ # Business logic
├── pkg/ # Public libraries
├── scripts/ # Utility scripts
└── tools/ # Command line tools
└── publisher/ # Tool to publish MCP servers to the registry
The API is documented using Swagger/OpenAPI. You can access the interactive Swagger UI at:
This provides a complete reference of all endpoints with request/response schemas and allows you to test the API directly from your browser.
Returns the health status of the service:
List Registry Server Entries
Lists MCP registry server entries with pagination support.
Query parameters:
limit: Maximum number of entries to return (default: 30, max: 100)
cursor: Pagination cursor for retrieving next set of results