repowiseagentic-community/mcp-gateway-registry

agentic-community / 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.

Python★ 961
Use in your agentAsk this codebase

github.com/agentic-community/mcp-gateway-registryIndexed at 00f55ecUp to date with upstream

What is mcp-gateway-registry?

mcp-gateway-registry is a unified platform for centralizing access to MCP servers and AI agents through the Model Context Protocol. It provides a gateway, registries for servers and agents, and an A2A communication hub with discovery, governance, authentication, and access control. The project is primarily written in Python.

Written by a model from the README and the source

Start reading

Code health

Health scores land with the first index: complexity, duplication, coverage, churn and ownership across every file.

Use agentic-community/mcp-gateway-registry in your agent

Point Claude Code, Cursor, Codex or VS Code at this repository. Your agent gets the index this page is built from: cited answers, callers, history and health for any file.

  1. 1.In Claude, open Customize → Connectors, click +, then Add custom connector. On a Team or Enterprise plan an owner adds it first under Organization settings → Connectors.
  2. 2.Paste the server URL below as the Remote MCP server URL, then click Add.
  3. 3.Click Connect. A Repowise sign-in window opens. Approve access.
  4. 4.Repowise's tools are now available in your Claude chats.

Connect with one click. Sign in with Repowise (OAuth), no API key to copy. Works in Claude on the web, desktop, and mobile.

Docs
bash
https://api.repowise.dev/mcp/agentic-community/mcp-gateway-registry
Editors need an API key: sign in to create one.Sign in to connect

This repo is public, so anyone with a Repowise account and an API key can connect.

Try asking

  • get_overview()
  • get_answer("how is mcp-gateway-registry put together?")
  • get_why("why is mcp-gateway-registry structured this way?")

Explore mcp-gateway-registry

Key features of mcp-gateway-registry

  • mcp-gateway-registry provides a unified gateway for access to multiple MCP servers.
  • mcp-gateway-registry supports registration, discovery, and governance for MCP servers and AI agents.
  • mcp-gateway-registry supports secure agent-to-agent discovery and communication through the A2A Protocol.
  • mcp-gateway-registry provides semantic search across MCP servers, tools, and registered agents.
  • mcp-gateway-registry supports Keycloak and Microsoft Entra ID authentication and access control.
  • mcp-gateway-registry provides MCP server security scanning and registry-wide scan reports.

How agentic-community/mcp-gateway-registry works

AI agents and development tools connect to the unified gateway, which provides access to registered MCP servers. The registry manages server registration, discovery, governance, and access, while the Agent Registry manages agent discovery and permissions. Agents communicate directly with other agents through A2A after the registry handles discovery, authentication, and access control. The registry directory provides the main application code, and cli provides command-line access to registry functions. The frontend directory provides the user interface, while metrics-service supports metrics and observability. Terraform and charts provide deployment configuration for the platform.

agentic-community/mcp-gateway-registry FAQ

What is mcp-gateway-registry?

mcp-gateway-registry is a unified platform for centralizing MCP servers and AI agents through the Model Context Protocol. It provides a gateway, registries, and an A2A communication hub.

How does mcp-gateway-registry work?

mcp-gateway-registry lets agents and development tools connect to one gateway for access to registered MCP servers. Its registries handle discovery, governance, authentication, and access control.

What language is mcp-gateway-registry written in?

mcp-gateway-registry is primarily written in Python.

How is the mcp-gateway-registry code organized?

mcp-gateway-registry organizes its code into registry, cli, frontend, metrics-service, Terraform, and charts directories. The registry provides core application code, cli provides command-line access, and frontend provides the user interface.

Who is mcp-gateway-registry for?

mcp-gateway-registry is for teams that need governed access to MCP servers and AI agents. It supports AI agents, developers, and enterprise authentication and access-control workflows.

What license does mcp-gateway-registry use?

mcp-gateway-registry uses the Apache-2.0 license.

The summary, features and answers on this page are written by a model from the README and the source, and refreshed with each index.

About this page

Get a page like this for your own codebase

Repowise built this map of agentic-community/mcp-gateway-registry from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.

Index your repo freeSee how Repowise worksFree for 2 public repos, with a page like this one.

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed.