Skip to main content
Mcpjungle emits Prometheus-compatible metrics using OpenTelemetry and exposes them at the /metrics endpoint. This gives you a simple operational view of tool traffic and latency across your registered MCP servers.

When metrics are enabled

  • In enterprise mode, metrics are enabled by default.
  • In development mode, metrics are disabled by default.
To enable them in development mode:
You can also set OTEL_ENABLED=false in enterprise mode if you explicitly want to disable metrics, but that is not the recommended operating posture for shared deployments.

Metrics endpoint

Once Mcpjungle is running with telemetry enabled:
The response uses standard Prometheus text exposition format.

Available metrics

Both metrics include these labels:

Example output

Prometheus

The production Compose path ships with a Prometheus service already configured to scrape Mcpjungle:
If you run your own Prometheus stack, scrape the gateway’s /metrics endpoint directly.

Feedback

If you want to see more metrics or have feedback on the current ones, please share your thoughts in the GitHub discussions or open an Issue.

Production deployment

Run Mcpjungle in enterprise mode with the right operational defaults.

Database

Back your shared deployment with PostgreSQL.

Governance overview

Understand the enterprise operating model around authentication and client access.

Reference: environment variables

See the full environment variable reference for telemetry and deployment tuning.