MCPJungle mcp gateway
Integrates with GitHub as a stdio-based MCP server, providing tools for Git and GitHub operations.
Supports integration with Hugging Face's MCP server, allowing access to AI models and tools through authentication with API tokens.
Demonstrated in the quickstart guide using context7 to retrieve Lodash documentation, showing how tools can access and return library documentation.
Supports PostgreSQL as a database backend for storing MCP server registrations and configuration data.
Provides SQLite as a default database option for storing MCP server registrations and configuration data.
Mentioned as an example of SaaS-provided MCP Servers that require API token authentication.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
MCPJungle is a self-hosted MCP gateway for developers and teams who want to manage multiple MCP servers without scattered client configurations, duplicated setup, or inconsistent access control.
Use it locally to keep your personal MCP setup clean, or run it as shared infrastructure for a team with centralized discovery, access control, and observability.

Instead of wiring every MCP server into every AI client, register your servers once in MCPJungle and let Claude, Cursor, Codex, or your own Agents connect to a single MCP endpoint.
Why MCPJungle?
MCP is powerful, but managing many MCP servers gets messy fast.
Without a gateway:
π Every client needs its own MCP server configuration
π§© Tools, prompts, and resources are scattered across different servers
π Access control is duplicated or missing
π₯ Teams have no shared view of available MCP tools
π οΈ Local setups become hard to reproduce
MCPJungle gives you a single control point:
π One MCP endpoint for Claude, Cursor, Copilot, and custom agents
ποΈ One place to register and manage MCP servers
π Unified discovery for tools, prompts, and resources
ποΈ Optional tool groups to expose only the tools a client should see
π Simple access-control and observability hooks for shared deployments
Start with a local setup. Scale to a shared team gateway when you need it.

Related MCP server: AuthMCP Gateway
Documentation
Mcpjungle documentation has a new home: https://docs.mcpjungle.com.
Please prefer the docs site over this README for the latest guides, reference, and operational details.
Your AI Clients can also access the docs using its MCP server https://docs.mcpjungle.com/mcp!
Quickstart
This quickstart guide will show you how to:
Start the mcpjungle server locally using
docker composeAdd an MCP server in mcpjungle
Connect your Claude Desktop to mcpjungle to access your MCP tools
Start the server
Fetch the docker-compose.yaml and start the mcpjungle server:
curl -O https://raw.githubusercontent.com/mcpjungle/MCPJungle/refs/heads/main/docker-compose.yaml
docker compose up -dThis exposes mcpjungle's streamable http mcp server at http://localhost:8080/mcp by default.
Add an MCP server
Download the
mcpjungleCLI on your local machine either using brew or directly from the Releases Page.
brew install mcpjungle/mcpjungle/mcpjungleAdd the context7 MCP server to mcpjungle using the CLI:
mcpjungle register --name context7 --url https://mcp.context7.com/mcpYou should see output similar to this:

Connect to mcpjungle
In your Claude Desktop, add the configuration for mcpjungle MCP server:
{
"mcpServers": {
"mcpjungle": {
"command": "npx",
"args": [
"mcp-remote",
"http://localhost:8080/mcp",
"--allow-http"
]
}
}
}Once you have added the configuration, try asking claude something simple:
Use context7 to get the documentation for `/lodash/lodash`Claude will then attempt to call the context7__get-library-docs tool via MCPJungle, which will return the documentation for the Lodash library.
You now have a working MCP setup with a single unified endpoint!
Next, explore the complete documentation at docs.mcpjungle.com and the public roadmap.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
This server cannot be deployed
Maintenance
Related MCP Connectors
Publish and discover MCP servers via the official MCP Registry. Powered by HAPI MCP server.
MCP gateway and cloud hosting for MCP servers, agents and apps like RAG, managed from your agent.
Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms.
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
Related MCP Servers
- AlicenseAqualityDmaintenanceA MCP server do create and deploy backend applications using https://heim.dev642 npm3MIT
- AlicenseNot gradedqualityCmaintenanceSecure MCP protocol proxy with OAuth2 + Dynamic Client Registration (DCR), JWT auth, RBAC, rate limiting, multi-server aggregation, and a monitoring/admin dashboard.156 PyPI13MIT
- AlicenseNot gradedqualityDmaintenanceSelf-hosted MCP proxy and aggregation platform. Register multiple upstream MCP servers and expose them through a single unified endpoint with namespace routing, multi-transport support (HTTP/SSE, stdio, OpenAPIβMCP), per-tool overrides, and a web admin UI.18MIT
- AlicenseNot gradedqualityDmaintenanceA universal MCP server that acts as a unified gateway for dynamically connecting and managing multiple MCP servers via a single HTTP endpoint.10 npm6MIT