Browse
→ Infrastructure
→ MCPJungle
MCPJungle
Self-hosted MCP gateway and registry for managing multiple MCP servers from a single endpoint. Built in Go with centralized tool discovery, access control, and multi-transport support for both Streamable HTTP and stdio. Agents connect to one gateway instead of multiple endpoints. Supports enterprise workflows with authentication, observability, and registry metadata. Deploys via Docker with a Postgres backend. Works with Claude Desktop, Cursor, and any MCP-compatible client. 1.1K GitHub stars. Open source under MIT license.
MCP unverified
Integration
| Transport | http |
| Auth | api-key |
| Endpoint | mcpjungle-mcp |
Use Cases
| 01 | Centralize access to multiple MCP servers behind a single gateway endpoint with built-in authentication and tool discovery for enterprise AI agent deployments |
| 02 | Register and manage MCP servers and their tools through a self-hosted registry so teams can discover available agent capabilities without scattered configurations |
| 03 | Route AI agent requests across multiple MCP servers with access control and observability from one Docker-deployed gateway |
Tags
gateway registry self-hosted enterprise multi-server access-control open-source go
Machine-readable: /api/servers.json
· JSON-LD schema embedded in <head>