MCPJungle and mcp-gateway
These are competitors offering alternative approaches to MCP gateway infrastructure—MCPJungle emphasizes self-hosted deployment while mcp-gateway focuses on centralized registry and REST-to-MCP translation, requiring teams to choose one architectural pattern for their MCP server management.
About MCPJungle
mcpjungle/MCPJungle
Self-hosted MCP Gateway for AI agents
This tool helps developers and organizations centralize access to various AI agent tools. You register your existing Model Context Protocol (MCP) servers and their tools with MCPJungle, and then your AI agents (like Claude or Cursor) can access all of them through a single connection. It's designed for managing AI agent interactions in a private, secure environment.
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