mcp-gateway-registry and mcp-gateway
Tool A appears to be an enterprise-ready, feature-rich evolution or robust rewrite of Tool B, both serving as an MCP Gateway and Registry, with Tool A offering advanced capabilities like secure OAuth and dynamic tool discovery.
About 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.
This platform helps AI development teams centralize access to their AI development tools and autonomous AI agents. It takes a chaotic collection of individual tool configurations and agent connections and turns them into a secure, governed, and easily discoverable system. AI platform engineers and enterprise architects can use this to manage all their AI development resources in one place.
About mcp-gateway
aarora79/mcp-gateway
MCP Gateway and Registry
Provides centralized access to multiple Model Context Protocol (MCP) servers through an Nginx reverse proxy, enabling AI agents to discover and invoke tools dynamically across distributed backends. The Registry component offers both UI and programmatic interfaces for service discovery, health monitoring, and dynamic tool exploration via natural language queries. Supports multiple transport mechanisms (SSE and Streamable HTTP) with deployments spanning EC2 instances, EKS clusters, and AWS Lambda functions.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work