Before you start, verify the MCPJungle server is reachable after step 1 by running:The server is ready when this returns a
200 response.Start the gateway server
Download the official Docker Compose file and start the MCPJungle server with a persistent Postgres database:This starts MCPJungle on port
8080. The Docker Compose file is optimized for local development — the server runs in development mode, which requires no additional initialization.Install the CLI
The Verify the installation:For other installation methods, see the Installation page.
mcpjungle CLI is how you register servers, manage tools, and configure the gateway from your local machine.Install it with Homebrew:Register an MCP server
Add your first MCP server to the gateway. This example registers context7, a remote MCP server that provides up-to-date library documentation:MCPJungle connects to the server, loads its tools, and makes them available through the gateway. You can confirm the tools are registered:
Connect Claude Desktop
Open your Claude Desktop configuration file and add MCPJungle as an MCP server. Claude connects to the MCPJungle gateway over HTTP using the Restart Claude Desktop to apply the configuration. Once connected, Claude can call any tool registered in MCPJungle. Try asking it:Claude will call the
mcp-remote bridge:context7__get-library-docs tool through MCPJungle and return the Lodash documentation.Next steps
Register more servers
Add HTTP and STDIO-based MCP servers to your gateway.
Connect other clients
Configure Cursor, Copilot, or a custom agent to use MCPJungle.
Tool Groups
Expose curated subsets of tools to specific agents or clients.
Deploy to production
Run MCPJungle in enterprise mode with access control and observability.