{"id":"mcpjungle","name":"MCPJungle","homepage":"https://github.com/mcpjungle/MCPJungle","repo_url":"https://github.com/mcpjungle/MCPJungle","category":"gateway","subcategories":["mcp-gateway","aggregator","self-hosted"],"tags":["gateway","self-hosted","aggregator","stdio","http","sqlite","postgresql","docker","homebrew"],"what_it_does":"MCPJungle is a self-hosted MCP gateway that aggregates multiple MCP servers behind a single endpoint, enabling AI clients and agents to access all registered tools through one connection with canonical tool naming.","use_cases":["Centralizing access to multiple MCP servers for Claude Desktop or Cursor without per-client configuration","Organizations deploying AI agents in production needing unified tool management and monitoring","Teams requiring a single MCP endpoint with security controls and privacy isolation across multiple backend servers"],"not_for":["Users who only need one MCP server (no aggregation benefit)","Fully managed/cloud-hosted MCP infrastructure (MCPJungle is self-hosted only)","Non-technical users who cannot operate a server or Docker container"],"best_when":"You manage several MCP servers and want AI clients to connect to a single endpoint, or you need centralized control and logging over agent tool access.","avoid_when":"You need a SaaS/hosted solution, your setup only involves a single MCP server, or you require advanced RBAC and observability beyond basic bearer token auth.","alternatives":["metamcp","mesh","mcpo"],"af_score":65.1,"security_score":60.0,"reliability_score":null,"package_type":"mcp_server","discovery_source":["github","github_awesome"],"priority":"low","status":"evaluated","version_evaluated":"latest","last_evaluated":"2026-03-01T09:50:05.925373+00:00","performance":{"latency_p50_ms":null,"latency_p99_ms":null,"uptime_sla_percent":null,"rate_limits":null,"data_source":"llm_estimated","measured_on":null}}