MCPJungle Details

MCPJungle is a self-hosted MCP Gateway and Registry for AI agents. It serves as a central registry and gateway to manage Model Context Protocol (MCP) servers and the tools they expose. By consolidating MCP server registration, tool discovery, and access control, MCPJungle enables AI agents and clients to discover, group, and securely invoke tools from a single, unified gateway. The project provides a CLI, Docker-based deployment options, and enterprise-ready features such as tool grouping, access control, and observability to streamline MCP-based workflows across organizations.

Use Case

MCPJungle acts as a centralized registry and gateway for MCP servers and their tools. It supports both Streamable HTTP and STDIO transports, enabling you to register remote MCP servers and invoke their tools through a single endpoint. It also lets you create Tool Groups to expose a curated subset of tools to specific clients, manage enabling/disabling of tools and prompts, and integrate with clients like Claude or Cursor. Example use cases include registering a calculator MCP server (streamable_http) and a filesystem MCP server (stdio), listing and invoking tools, and creating Claude-specific tool groups.

Example usage from the docs:

  • Register a streamable HTTP MCP server:

  • mcpjungle register --name calculator --description "Provides some basic math tools" --url http://127.0.0.1:8000/mcp

  • Access tools via MCPJungle:

  • mcpjungle list tools

    <h1 class="text-2xl font-semibold mt-5 mb-3">Check tool usage</h1>
    mcpjungle usage calculator__multiply

    <h1 class="text-2xl font-semibold mt-5 mb-3">Call a tool</h1>
    mcpjungle invoke calculator__multiply --input '{"a": 100, "b": 50}'


  • Connect Claude to MCPJungle (example config):

  • {
    "mcpServers": {
    "mcpjungle": {
    "command": "npx",
    "args": [
    "mcp-remote",
    "http://localhost:8080/mcp",
    "--allow-http"
    ]
    }
    }
    }

  • Register a STDIO MCP server (filesystem):

  • {
    "name": "filesystem",
    "transport": "stdio",
    "description": "filesystem mcp server",
    "command": "npx",
    "args": ["-y", "@modelcontextprotocol/server-filesystem", "."]
    }

  • Example tool group usage:

  • $ mcpjungle create group -c ./claude-tools-group.json

    Tool Group claude-tools created successfully
    It is now accessible at the following streamable http endpoint:

    http://127.0.0.1:8080/v0/groups/claude-tools/mcp


    Available Tools (7)

    Examples & Tutorials

    Real example code and usage patterns directly from the documentation:

  • Quickstart: Start the server using Docker Compose and verify health

  • curl -O https://raw.githubusercontent.com/mcpjungle/MCPJungle/refs/heads/main/docker-compose.yaml
    docker compose up -d

  • Start a local MCPJungle server via CLI installation (Homebrew)

  • brew install mcpjungle/mcpjungle/mcpjungle
    mcpjungle version

  • Register an MCP server (streamable HTTP)

  • mcpjungle register --name calculator --description "Provides some basic math tools" --url http://127.0.0.1:8000/mcp

  • Register a server via config file

  • cat ./calculator.json
    {
    "name": "calculator",
    "transport": "streamable_http",
    "description": "Provides some basic math tools",
    "url": "http://127.0.0.1:8000/mcp"
    }

    mcpjungle register -c ./calculator.json


  • List tools, check usage, and invoke

  • mcpjungle list tools

    <h1 class="text-2xl font-semibold mt-5 mb-3">Check tool usage</h1>
    mcpjungle usage calculator__multiply

    <h1 class="text-2xl font-semibold mt-5 mb-3">Call a tool</h1>
    mcpjungle invoke calculator__multiply --input '{"a": 100, "b": 50}'


  • Register a STDIO-based MCP server (filesystem)

  • {
    "name": "filesystem",
    "transport": "stdio",
    "description": "filesystem mcp server",
    "command": "npx",
    "args": ["-y", "@modelcontextprotocol/server-filesystem", "."]
    }

  • Deregister servers

  • mcpjungle deregister calculator
    mcpjungle deregister filesystem

  • Claude integration config

  • {
    "mcpServers": {
    "mcpjungle": {
    "command": "npx",
    "args": [
    "mcp-remote",
    "http://localhost:8080/mcp",
    "--allow-http"
    ]
    }
    }
    }

  • Cursor integration config

  • {
    "mcpServers": {
    "mcpjungle": {
    "url": "http://localhost:8080/mcp"
    }
    }
    }

  • Enabling/Disabling tools and prompts

  • <h1 class="text-2xl font-semibold mt-5 mb-3">disable a specific tool</h1>
    mcpjungle disable tool context7__get-library-docs
    <h1 class="text-2xl font-semibold mt-5 mb-3">re-enable the tool</h1>
    mcpjungle enable tool context7__get-library-docs

    <h1 class="text-2xl font-semibold mt-5 mb-3">disable all tools in a server</h1>
    mcpjungle disable tool context7

    <h1 class="text-2xl font-semibold mt-5 mb-3">disable the whole server</h1>
    mcpjungle disable server context7

    <h1 class="text-2xl font-semibold mt-5 mb-3">disable a prompt</h1>
    mcpjungle disable prompt "huggingface_Model Details"
    <h1 class="text-2xl font-semibold mt-5 mb-3">disable all prompts in a server</h1>
    mcpjungle disable prompt context7


  • Prompts examples

  • $ mcpjungle list prompts --server huggingface

    $ mcpjungle get prompt "huggingface__Model Details" --arg model_id="openai/gpt-oss-120b"


  • Tool Groups examples

  • {
    "name": "claude-tools",
    "description": "This group only contains tools for Claude Desktop to use",
    "included_tools": [\
    "filesystem__read_file",\
    "deepwiki__read_wiki_contents",\
    "time__get_current_time"\
    ]
    }

  • Example 2: Including entire servers with exclusions

  • {
    "name": "claude-tools",
    "description": "All tools from time and deepwiki servers except time__convert_time",
    "included_servers": ["time", "deepwiki"],
    "excluded_tools": ["time__convert_time"]
    }

  • Example 3: Mixing approaches

  • {
    "name": "comprehensive-tools",
    "description": "Mix of manual tools, server inclusion, and exclusions",
    "included_tools": ["filesystem__read_file"],
    "included_servers": ["time"],
    "excluded_tools": ["time__convert_time"]
    }

  • Tool Group access endpoint example

  • $ mcpjungle create group -c ./claude-tools-group.json

    Tool Group claude-tools created successfully
    It is now accessible at the following streamable http endpoint:

    http://127.0.0.1:8080/v0/groups/claude-tools/mcp


    Installation Guide

    Step-by-step installation instructions from the docs:

  • Install via Homebrew:

  • brew install mcpjungle/mcpjungle/mcpjungle

  • Verify installation:

  • mcpjungle version

  • Alternative: Docker image for production deployment:

  • docker pull mcpjungle/mcpjungle

  • Quick start with Docker Compose (local development):

  • curl -O https://raw.githubusercontent.com/mcpjungle/MCPJungle/refs/heads/main/docker-compose.yaml

    docker compose up -d


  • Health check:

  • curl http://localhost:8080/health

  • Register a remote STDIO or Streamable HTTP MCP server (examples in docs) as part of setup.

  • Integration Guides

    Frequently Asked Questions

    Is this your MCP?

    Claim ownership and get verified badge

    Repository Stats

    Sponsored

    Ad Space Available
    Important Notes

    Notes and warnings from the docs:

  • SSE support exists but is not yet mature.

  • Prompts are supported and registered when MCP servers provide them.

  • Enterprise mode enables stricter security policies, including authentication, ACLs, and observability; development mode disables telemetry by default.

  • OpenTelemetry metrics are available at /metrics when enabled; in enterprise mode, OTEL is enabled by default, while in development mode you must enable it via OTEL_ENABLED.

  • Tool Groups can expose only a subset of tools; prompts are not currently supported in Tool Groups; you cannot update an existing group—delete and recreate instead.
  • Prerequisites

    MCPJungle is distributed as a stand-alone binary. Install it via Homebrew or download from the Releases page. Docker-based deployments are supported via docker-compose. For persistence, a Postgres DSN can be supplied; otherwise a SQLite database file mcpjungle.db is created by default. No Node.js prerequisite is required for MCPJungle itself.

    Details
    Last Updated1/1/2026
    Websitegithub.com
    SourceGitHub

    Compare Alternatives

    Similar MCP Tools

    9 related tools
    Skyvern MCP

    Skyvern MCP

    Skyvern is the complete browser MCP for AI agents. 75+ tools for clicking, filling forms, extracting structured data, logging in with 2FA, uploading files, drag-and-drop, running JavaScript, inspecting network traffic, multi-tab browsing, and building reusable cached workflows. First workflow run uses AI; subsequent runs replay a cached script with zero LLM calls.

    pageguard-mcp

    pageguard-mcp

    pageguard-mcp is an MCP (Model Context Protocol) server that exposes PageGuard privacy compliance scanning as a set of tools for AI coding assistants. It enables seamless integration with Claude Code, Cursor, Windsurf, ChatGPT, and any MCP-compatible environment. The server supports local scans, live URL scans, and AI-generated privacy-related documents, helping developers identify tracking technologies, cookies, and third-party data processing, while also producing tailored privacy policies and compliance materials. With its straightforward MCP configuration and free local scanning capability, pageguard-mcp is designed to empower teams to maintain privacy compliance across their projects and websites.

    Prop Firm Deal Finder

    Prop Firm Deal Finder (PFDF) is a free MCP server that gives AI assistants real-time access to live discount codes across 20+ proprietary trading firms. It provides 6 tools: get_deals (all current discounts), search_firms (search by name/asset class), compare_firms (side-by-side comparison of challenges), find_cheapest (cheapest challenge by account size with PFDF code applied), get_firm_details (15+ data points per firm), and get_discount_code (universal PFDF code). Covers firms like Topstep, Apex Trader Funding, MyFundedFutures, FTMO, The Funded Trader, and 14 more. No API key required. Install via npx propfirmdealfinder-mcp-server or connect remotely at https://web-production-6607c.up.railway.app/mcp

    mcp-server-with-spring-ai

    mcp-server-with-spring-ai

    mcp-server-with-spring-ai is a Spring Boot integrated MCP (Model Context Protocol) server example that showcases how to expose executable tools from an MCP server to clients (including LLMs) and how to wire a MCP client to consume those tools. The documentation explains MCP at a high level, outlines the three-layer MCP Java SDK architecture (Client/Server Layer, Session Layer, Transport Layer), and demonstrates two sample tools implemented in SellerAccountTools. This repo emphasizes how an MCP server can connect to external data sources (e.g., a PostgreSQL DB) and expose tools that an AI model can invoke to retrieve data, with the example illustrating tool invocation and automatic tool selection by prompts.

    OpenClaw MCP Server

    OpenClaw MCP Server

    OpenClaw MCP Server is a secure Model Context Protocol (MCP) bridge that connects Claude.ai with a self-hosted OpenClaw assistant, enabling OAuth2 authentication and safe, controlled communication between the Claude AI ecosystem and your local or hosted OpenClaw deployment. This MCP server acts as an orchestration layer that exposes MCP tools to Claude.ai, manages authentication, and enforces security boundaries like CORS and transport options. It is designed to be deployed via Docker or run locally, with detailed installation, configuration, and security guidance provided in the documentation. By serving as a bridge, it enables Claude.ai to delegate tasks to your OpenClaw bot while preserving control over data flow and access controls, in line with MCP specifications and best security practices.

    Graphiti MCP Server

    Graphiti MCP Server

    Graphiti MCP Server is an experimental implementation that exposes Graphiti's real-time, temporally-aware knowledge graph capabilities through the MCP (Model Context Protocol) interface. It enables AI agents and MCP clients to interact with Graphiti's knowledge graph for structured extraction, reasoning, and memory across conversations, documents, and enterprise data. The server supports multiple backends (FalkorDB by default and Neo4j), a variety of LLM providers (OpenAI, Anthropic, Gemini, Groq, Azure OpenAI), and multiple embedder options, all accessible via an HTTP MCP endpoint at /mcp/ for broad client compatibility. It also includes queue-based asynchronous episode processing, rich entity types for structured data, and flexible configuration through config.yaml, environment variables, or CLI arguments.

    Context7 MCP Server

    Context7 MCP Server

    Context7 MCP Server delivers up-to-date, code-first documentation and examples for LLMs and AI code editors by pulling content directly from the source. It supports multiple MCP clients and exposes tools that help you resolve library IDs and retrieve library documentation, ensuring prompts use current APIs and usage patterns. The repository provides installation and integration guides for Cursor, Claude Code, Opencode, and other clients, along with practical configuration samples and OAuth options for remote HTTP connections. This MCP server is designed to keep prompts in sync with the latest library docs, reducing hallucinations and outdated code snippets.

    TrendRadar MCP

    TrendRadar MCP

    TrendRadar MCP is an AI-driven Model Context Protocol (MCP) based analysis server that exposes a suite of specialized tools for cross-platform news analysis, trend tracking, and intelligent push notifications. It integrates with TrendRadar’s multi-platform data aggregation (RSS and trending topics) and provides advanced AI-powered insights, sentiment analysis, and cross-platform correlation. The MCP server enables developers to query, analyze, and compare news across platforms using a consistent toolset, with ongoing updates that expand capabilities such as RSS querying, date parsing, and multi-date trend analysis. This documentation references the MCP module updates, tool additions, and architecture changes that enhance extensibility, cross-platform data handling, and AI-assisted reporting.

    ChainAware Behavioural Prediction MCP

    ChainAware Behavioural Prediction MCP

    The ChainAware Behavioural Prediction MCP is an MCP-based server that provides AI-powered tools to analyze wallet behaviour prediction, fraud detection, and rug pull prediction. Designed for Web3 security and DeFi analytics, it enables developers and platforms to integrate risk assessment, predictive wallet behavior insights, and rug-pull detection through MCP-compatible clients. The server exposes three specialized tools and uses Server-Sent Events (SSE) for real-time responses, helping safeguard DeFi users, monitor liquidity risks, and score wallet or contract trustworthiness. Access to production endpoints is API-key gated, reflecting a private backend architecture that supports secure, scalable risk analytics across wallets, contracts, and pools.