広告掲載
MCP.so
ログイン

Mcpjungle MCP Gateway

@mcpjungle

リポジトリホームページ

基本情報

カテゴリ

その他

ライセンス

MPL-2.0

トランスポート

stdio

作者

mcpjungle

投稿者

Raghav

Mcpjungle MCP Gateway について

One place to manage & connect to all your MCP servers

#mcpjungle#mcp-gateway#ai-agents

Mcpjungle MCP Gateway の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "mcpjungle-mcpjungle": {
      "command": "docker",
      "args": [
        "pull",
        "mcpjungle/mcpjungle"
      ]
    }
  }
}

Mcpjungle MCP Gateway のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Mcpjungle Mcp Gateway?

Mcpjungle Mcp Gateway (MCPJungle) is a self-hosted gateway that lets developers and teams run all their MCP (Model Context Protocol) servers behind a single endpoint. It consolidates scattered client configurations, reduces duplicated setup, and provides centralized access control and observability.

How to use Mcpjungle Mcp Gateway?

Start the gateway with Docker Compose (docker compose up -d) or run the binary directly (mcpjungle start). Use the CLI (mcpjungle register --name ... --url ...) to add MCP servers. Connect AI clients like Claude, Cursor, or Copilot by pointing them to the unified MCP endpoint at http://localhost:8080/mcp.

Key features of Mcpjungle Mcp Gateway

  • Single MCP endpoint for multiple AI clients
  • Centralized server registration and management
  • Unified discovery of tools, prompts, and resources
  • Optional tool groups to restrict client access
  • Access control and OpenTelemetry for shared deployments

Use cases of Mcpjungle Mcp Gateway

  • Local development: keep personal MCP setup clean and reproducible
  • Team infrastructure: share a central MCP gateway with discovery and access control
  • Multi‑client integration: connect Claude, Cursor, Copilot, and custom agents to one endpoint
  • Production deployments: deploy with Postgres and enterprise‑grade observability

よくある質問

1

What is the difference between MCPJungle and a typical MCP server?

MCPJungle is a gateway that aggregates multiple MCP servers behind a single endpoint, offering centralized management, access control, and tool grouping—not just a single MCP server.

2

What dependencies or runtime does Mcpjungle Mcp Gateway require?

It runs as a standalone binary or Docker image. For development, it uses a SQLite database (default) or optional PostgreSQL. Docker images are available with or without stdio‑tool dependencies.

3

Where does my data live?

All registered server data and gateway state are stored in a configurable database (SQLite file or PostgreSQL). Deleting the database removes all configuration.

4

What transports does Mcpjungle Mcp Gateway support?

It supports Streamable HTTP (primary), stdio, and SSE (SSE support is not yet mature).

5

How does authentication work?

Authentication is an enterprise feature. In development mode, the gateway runs without authentication; production/enterprise mode enables access control and other enterprise features.

コメント

「その他」の他のコンテンツ

FastMCP v2 🚀

jlowin

🚀 The fast, Pythonic way to build MCP servers and clients.

26.0K

Screenpipe

screenpipe

YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context

22.0K

Soar Flight Booking MCP

Soar Flight Booking MCP is a remote MCP server available at https://mcp.soar.flights.

Lemon.io

lemon-io

Request dedicated senior developers to work on your project, write job descriptions, and prep technical interviews — all without leaving your Claude chat. Just describe what you need, and Lemon.io MCP does the rest. 1–3

Handl

Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.

広告掲載