ACTIVE DEVELOPMENT - WORK IN PROGRESS
About
MCP Gateway & Registry is a unified platform that combines centralized access control with intelligent tool discovery for Model Context Protocol (MCP) servers. It consists of a Registry providing visual and programmatic interfaces for exploring available MCP servers and tools…
Details
- License
- Apache-2.0 license
Explore
MCP Tool Discovery: Enables automatic tool discovery by AI Agents and Agent developers. Fetches and displays the list of tools (name, description, schema) based on natural language queries (e.g. _do I have tools to get stock information?_).
Unified access to a governed list of MCP servers: Access multiple MCP servers through a common MCP gateway, enabling AI Agents to dynamically discover and execute MCP tools.
Service Registration: Register MCP services via JSON files or the web UI/API.
Web UI: Manage services, view status, and monitor health through a web interface.
Authentication: Secure login system for the web UI and API access.
Health Checks:
Periodic background checks for enabled services (checks /sse endpoint).
Manual refresh trigger via UI button or API endpoint.
Real-time UI Updates: Uses WebSockets to push health status, tool counts, and last-checked times to all connected clients.
Dynamic Nginx Configuration: Generates an Nginx reverse proxy configuration file (registry/nginx_mcp_revproxy.conf) based on registered services and their enabled/disabled state.
Service Management:
Enable/Disable services directly from the UI.
Edit service details (name, description, URL, tags, etc.).
Filtering & Statistics: Filter the service list in the UI (All, Enabled, Disabled, Issues) and view basic statistics.
UI Customization:
Dark/Light theme toggle (persisted in local storage).
Collapsible sidebar (state persisted in local storage).
State Persistence: Enabled/Disabled state is saved to registry/server_state.json (and ignored by Git).
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
ACTIVE DEVELOPMENT - WORK IN PROGRESSCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
An Amazon EC2 machine (ml.t3.2xlarge) with a standard Ubuntu AMI for running this solution.
An SSL cert for securing the communication to the Gateway. _This Gateway uses a self-signed cert by default and is also available over HTTP_.
- One of the example MCP servers packaged in this repo uses the
PolygonAPI for stock ticker data. Get an API key from here. The server will still start without the API key but you will get a 401 Unauthorized error when using the tools provided by this server.
The Gateway and the Registry are available as a Docker container. The package includes a couple of test MCP servers as well.
1. Clone the repository:
git clone https://github.com/agentic-community/mcp-gateway-registry.git
cd mcp-gateway
1. Create local directories for saving MCP server logs and run-time data:
sudo mkdir -p /opt/mcp-gateway/servers
sudo cp -r registry/servers /opt/mcp-gateway/
sudo mkdir /var/log/mcp-gateway
1. Build the Docker container to run the Gateway and Registry:
docker build -t mcp-gateway .
1. Run the container:
export ADMIN_USER=admin
export ADMIN_PASSWORD=your-admin-password
export POLYGON_API_KEY=your-polygon-api-key
1. Enable access to TCP port 443 from the IP address of your MCP client (your laptop, or anywhere) in the inbound rules in the security group associated with your EC2 instance.
1. You would need to have an HTTPS certificate and private key to proceed. Let's say you use your-mcp-gateway.com as the domain for your MCP server then you will need an SSL cert for your-mcp-gateway.com and MCP servers behind the Gateway will be accessible to MCP clients as https://your-mcp-gateway.com/mcp-server-name/sse.
1. Rebuild the container using the same command line as before.
1. Run the container with the -v switch to map the local folder containing the cert and the private key to the container. Replace /path/to/certs/ and /path/private as appropriate in the command provided below.
docker run -p 80:80 -p 443:443 -p 7860:7860 \
-e ADMIN_USER=$ADMIN_USER \
-e ADMIN_PASSWORD=$ADMIN_PASSWORD \
-e POLYGON_API_KEY=$POLYGON_API_KEY \
-e SECRET_KEY=$(python3 -c 'import secrets; print(secrets.token_hex(32))') \
-v /path/to/certs:/etc/ssl/certs \
-v /path/to/private:/etc/ssl/private \
-v /var/log/mcp-gateway:/app/logs \
-v /opt/mcp-gateway/servers:/app/registry/servers \
--name mcp-gateway-container mcp-gateway
```
For production deployments you might want to run this solution on EKS, the Distributed Training and Inference on EKS repo contains the helm chart for running the gateway and registry on an EKS cluster. Refer to Serve MCP Gateway Registry README for step by step instructions.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"active development - work in progress": {
"mcp-gateway-registry": {
"command": "docker",
"args": [
"build",
"-t",
"mcp-gateway",
"."
]
}
}
}
}McpServers
{
"mcp-gateway-registry": {
"command": "docker",
"args": [
"build",
"-t",
"mcp-gateway",
"."
]
}
}> WARNING: This repository is under active development. Expect frequent updates and breaking changes as we improve functionality and refine APIs. We recommend pinning to specific versions for production use. Star the repository to track our progress!
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
