mcp-gateway-registry

Enterprise-ready MCP Gateway & Registry that centralizes AI development tools with secure OAuth authentication, dynamic tool discovery, and unified access for both autonomous AI agents and AI coding assistants. Transform scattered MCP server chaos into governed, auditable tool access with Keycloak/Entra integration.

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

View docs

Command

claude mcp add --transport stdio agentic-community-mcp-gateway-registry node server.js \
  --env PORT="Port to run the gateway-registry (e.g., 3000)" \
  --env LOG_LEVEL="Logging level (e.g., info, debug)" \
  --env MCP_REGISTRY_URL="URL of the MCP registry (e.g., https://registry.example.com)"

How to use

The MCP Gateway & Registry acts as a unified access point for MCP servers and AI agents. It registers MCP servers, makes them discoverable, and also handles agent registration and discovery. Through this gateway, developers can centrally manage which MCP servers are available to tools and agents, while agents themselves can discover other agents via the integrated Agent Registry. The platform supports agent-to-agent communication (A2A) directly between agents once they are discovered, with authentication and access governed by centralized policies. Start by running the gateway-registry service to expose a single control plane for your MCP ecosystem, then register your MCP servers and agents so tools and agents can locate and connect to them through the gateway.

How to install

Prerequisites:

Node.js (14.x or newer) and npm/yarn installed
Git installed
Access to an MCP Registry (if you want to register servers/agents centrally) or can operate in standalone mode

Clone the repository
- git clone https://github.com/agentic-community/mcp-gateway-registry.git
- cd mcp-gateway-registry
Install dependencies
- npm install or
- yarn install
Configure environment
- Create a .env file or set environment variables as needed (see mcp_config.env in documentation). Example: MCP_REGISTRY_URL=https://registry.example.com PORT=3000 LOG_LEVEL=info
Run the server
- npm run start or
- node server.js
Verify the gateway is running
- Open http://localhost:3000 (or your configured port) to confirm the gateway/registry API is available.

Additional notes

Tips and common considerations:

Ensure your MCP registry URL is reachable from the gateway host; use a load balancer or reverse proxy if needed.
Configure proper authentication for both server and agent registration to avoid unauthorized access.
Use environment-specific config (development, staging, production) to separate credentials and endpoints.
If you enable A2A communication, ensure firewall rules allow direct peer-to-peer traffic between agents as required by your security posture.
Check logs regularly (LOG_LEVEL) to diagnose registration or discovery issues; enable debug in early setups for troubleshooting.
When upgrading Node.js versions, verify compatibility with the gateway-registry codebase.
Back up registry configurations and consider using a centralized vault for credentials if you integrate external services.

Related MCP Servers

ruflo

16.9k

🌊 The leading agent orchestration platform for Claude. Deploy intelligent multi-agent swarms, coordinate autonomous workflows, and build conversational AI systems. Features enterprise-grade architecture, distributed swarm intelligence, RAG integration, and native Claude Code / Codex Integration

bytebot

10.5k

Bytebot is a self-hosted AI desktop agent that automates computer tasks through natural language commands, operating within a containerized Linux desktop environment.

valuecell

9.3k

ValueCell is a community-driven, multi-agent platform for financial applications.

solace-agent-mesh

2.1k

An event-driven framework designed to build and orchestrate multi-agent AI systems. It enables seamless integration of AI agents with real-world data sources and systems, facilitating complex, multi-step workflows.

LLMTornado

563

The .NET library to build AI agents with 30+ built-in connectors.

a2a-x402

460

The A2A x402 Extension brings cryptocurrency payments to the Agent-to-Agent (A2A) protocol, enabling agents to monetize their services through on-chain payments. This extension revives the spirit of HTTP 402 "Payment Required" for the decentralized agent ecosystem.