Self-hosted MCP gateway for registering HTTP and stdio MCP servers once, exposing them through a unified MCP endpoint, and using tool groups, access-control, and upstream authentication for shared agent deployments.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
5 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.
Safety & privacy surface
5 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, third-party handling.
Disclosure: MPL-2.0-licensed open-source MCP gateway. It is a management and proxy layer, not a replacement for reviewing the safety of every upstream MCP server it exposes.
{
"mcpServers": {
"mcpjungle": {
"type": "http",
"url": "https://<mcpjungle-host>/mcp",
"headers": {
"Authorization": "Bearer <mcpjungle-client-token>"
}
}
}
}MCPJungle is a self-hosted MCP gateway for registering upstream MCP servers and
exposing them through a single MCP endpoint. It discovers tools, prompts, and
resources from registered servers, rewrites names into canonical
server__tool and server__prompt formats, and proxies client calls to the
correct upstream server.
Use it when an individual or team has more MCP servers than they want to wire into every client separately, or when a shared deployment needs tool groups, client allow-lists, upstream authentication, and centralized observability.
These sources were reviewed on 2026-06-06. Prefer the live repository, quickstart, license, core concepts, registration guides, tool-group guide, access-control guide, upstream-authentication guide, and MCP proxy source for current setup and behavior.
Run MCPJungle with Docker Compose or the standalone binary, register upstream MCP servers, and expose the gateway behind TLS before sharing it with agents:
brew install mcpjungle/mcpjungle/mcpjungle
mcpjungle register --name context7 --url https://mcp.context7.com/mcp
Connect Claude or another MCP client to the gateway endpoint:
{
"mcpServers": {
"mcpjungle": {
"type": "http",
"url": "https://<mcpjungle-host>/mcp",
"headers": {
"Authorization": "Bearer <mcpjungle-client-token>"
}
}
}
}
For local development deployments that use a plain local endpoint, follow the upstream quickstart and keep that configuration out of shared or production clients.
server__tool tool names.MCPJungle concentrates capability. Treat access to the gateway as access to the registered upstream tools, prompts, resources, and credentials. In shared deployments, use enterprise mode, create one client identity per integration, avoid wildcard allow-lists, and prefer tool groups that expose only the tools a client needs.
Be careful with stdio servers because they run as child processes on the MCPJungle host or container and may receive environment variables or mounted filesystem access. Upstream HTTP registrations can store bearer tokens, custom headers, or OAuth credentials. Protect the gateway database, CLI config files, dashboard, logs, metrics, resource URIs, tool payloads, and client access tokens.
No mcpjungle/MCPJungle, MCPJungle gateway, MCPJungle proxy, or matching source
URL entry was found in content/mcp or README.md. The existing MCPHub Server
Manager entry covers a different server-management project; it does not cover
MCPJungle's gateway, canonical proxying, tool groups, enterprise client
allow-lists, and upstream-authentication model.
Show that MCPJungle Gateway is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/mcpjungle-gateway)MCPJungle Gateway side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Self-hosted MCP gateway for registering HTTP and stdio MCP servers once, exposing them through a unified MCP endpoint, and using tool groups, access-control, and upstream authentication for shared agent deployments. Open dossier | PortSwigger's Burp Suite MCP Server extension connects Burp Suite to MCP clients through an SSE server or packaged stdio proxy for request, Repeater, Intruder, history, scanner, Collaborator, and configuration workflows. Open dossier | MCP server for Coolify infrastructure management, diagnostics, deployments, logs, projects, environments, applications, databases, services, env vars, storage, scheduled tasks, private keys, cloud tokens, teams, and docs search. Open dossier | Self-hostable calendar MCP service for Keeper.sh that lets Claude list calendars and accounts, read events, create or update events, delete events, respond to invites, and retrieve iCal feed URLs through Keeper's API. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | Not reviewed | Not reviewed | Not reviewed | Not reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| Submitter | oktofeesh1 | oktofeesh1 | oktofeesh1 | oktofeesh1 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | ||||
| Category | mcp | mcp | mcp | mcp |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | mcpjungle | PortSwigger | Stuart Mason | ridafkih |
| Added | 2026-06-06 | 2026-06-06 | 2026-06-06 | 2026-06-06 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓MCPJungle centralizes access to many upstream MCP servers, so a broad gateway token can expose every registered tool, prompt, and resource. Registered stdio MCP servers run as child processes on the MCPJungle host or container and inherit the configured command, args, environment, and mounted filesystem access. Upstream HTTP servers can store bearer tokens, custom headers, and beta OAuth credentials in gateway configuration. Tool groups can reduce context and capability exposure, but they must be reviewed whenever upstream servers or tools change. Use enterprise mode, explicit client allow-lists, least-privilege upstream credentials, TLS, and audit/observability controls for shared deployments. | ✓Burp Suite MCP Server can send HTTP/1.1 and HTTP/2 requests, create Repeater tabs, send requests to Intruder, toggle Proxy Intercept, pause or resume Burp's task execution engine, and update the active message editor. In Burp Suite Professional it can also expose scanner issues and generate or poll Collaborator payloads for out-of-band testing. The extension includes approval flows for outbound HTTP requests and sensitive data access, but users can configure always-allow targets and disable some approval requirements. Configuration editing tools can import project-level or user-level Burp options when enabled in the extension, which can change proxy, scanner, target, and other Burp behavior. Use only on systems and applications where testing is authorized; active requests, Intruder traffic, scanner workflows, and Collaborator payloads can affect third-party services. Keep the MCP server bound to trusted local interfaces and avoid exposing the SSE server to untrusted networks. | ✓Coolify MCP Server can start, stop, restart, redeploy, cancel deployments, update env vars, create or delete projects, environments, applications, databases, services, backups, storages, scheduled tasks, private keys, GitHub apps, and cloud tokens depending on API permissions. Batch tools such as `restart_project_apps`, `bulk_env_update`, `stop_all_apps`, and `redeploy_project` can affect multiple production services at once. Deployment, control, backup, storage, private key, cloud token, GitHub app, and scheduled-task operations should require explicit confirmation. Custom `--header` values may carry auth-proxy secrets; never let an agent invent, log, or modify them casually. Test on non-production projects or staging resources before allowing Claude to operate live Coolify infrastructure. | ✓Keeper's MCP tools can read calendar data and perform write operations including event creation, event updates, event deletion, and RSVP changes. The MCP handler requires an authenticated bearer token and checks for the Keeper MCP read scope before exposing tools. Tool calls proxy to Keeper API endpoints with the caller's bearer token, so the MCP client inherits the user's connected calendar permissions. Start by listing calendars and reading bounded date ranges; require human confirmation before modifying or deleting events. Review Google, Microsoft, iCloud, CalDAV, ICS, and self-hosted calendar account permissions before exposing them to an agent. |
| Privacy notes | ✓MCPJungle can store registered server URLs, command arguments, environment variables, headers, bearer tokens, OAuth tokens, client access tokens, tool schemas, prompt names, resource URIs, and gateway database state. Tool calls, prompts, resources, logs, metrics, CLI output, dashboard views, and upstream responses may contain sensitive project data or third-party service data. The proxy source strips client-sent headers before forwarding upstream calls, but configured upstream credentials and tool payloads remain sensitive. Redact gateway URLs, access tokens, upstream tokens, OAuth client secrets, command args, environment values, resource URIs, and tool outputs before sharing logs or screenshots. | ✓Proxy HTTP history, WebSocket history, Organizer items, scanner issues, request and response bodies, headers, cookies, tokens, session identifiers, and Collaborator interaction data may be returned to the MCP client. The extension can read project-level and user-level Burp configuration; upstream code filters some configuration credentials when configured, but users should still treat exported options as sensitive. MCP prompts, responses, Burp logs, and client transcripts can retain target URLs, credentials, payloads, vulnerability details, and proprietary application behavior. The stdio proxy and SSE server bridge Burp traffic into the MCP client process; keep client configs, proxy paths, and Burp project files protected. | ✓Coolify access tokens, base URLs, custom headers, application UUIDs, server IPs, domains, logs, env vars, deployment logs, private keys, cloud-provider tokens, GitHub app data, team membership, backups, database metadata, and service configuration can be exposed to the MCP client. Application and deployment logs may contain secrets, customer data, build output, container metadata, private repository details, and runtime errors. Environment variable and cloud-token tools can reveal or mutate sensitive infrastructure credentials. Documentation search is local to the server, but Coolify API calls contact the configured Coolify instance. Keep tokens and auth-proxy headers in local MCP client configuration only, and avoid sharing transcripts that include infrastructure identifiers or logs. | ✓Calendar events can expose titles, descriptions, locations, free/busy status, account names, provider names, calendar names, calendar URLs, and iCal feed URLs. OAuth tokens, CalDAV credentials, session tokens, bearer tokens, auth secrets, encryption keys, database URLs, and MCP URLs are sensitive deployment data. Keeper stores and syncs calendar data across connected providers; logs, MCP transcripts, API responses, and monitoring traces can include private schedule details. Redact event ids, calendar ids, account names, feed URLs, bearer tokens, event text, locations, and provider details before sharing debug output. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Connect Burp Suite to Claude through an MCP extension for HTTP requests, Repeater, Intruder, proxy history, scanner issues, and Collaborator.
Connect Claude to Coolify for supervised self-hosted PaaS diagnostics, deployments, resource management, logs, env vars, cloud tokens, and docs.
Source-backed guides for putting this to work.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.