mcp-gateway-registry and mcp-gateway
These are **competitors** — both provide centralized MCP gateway and registry functionality to manage and expose tools to LLMs, with overlapping core features (OAuth security, tool discovery, REST-to-MCP translation), though the agentic-community version appears more mature and enterprise-focused while theognis1002's version is a smaller independent implementation.
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
theognis1002/mcp-gateway
Model Context Protocol (MCP) Gateway & Registry - Central hub for managing tools, resources, and prompts for MCP-compatible LLMs. Translates REST APIs into MCP, builds virtual MCP servers with security and observability, and bridges multiple transports (stdio, SSE, streamable HTTP).
This is a central hub for managing and securing your interactions with various AI models. It takes your standard requests and translates them for different AI services, acting as a secure middle layer. AI solution architects, operations engineers, and IT managers can use this to integrate and govern their use of AI models across their organization.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work