/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.
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:Available metrics
| Metric | Type | Description |
|---|---|---|
mcpjungle_tool_calls_ratio_total | Counter | Total number of tool calls handled by Mcpjungle. |
mcpjungle_tool_call_latency_seconds | Histogram | Latency for tool calls, in seconds. |
| Label | Description |
|---|---|
mcp_server_name | Name of the upstream MCP server that owns the tool. |
tool_name | Canonical tool name, for example calculator__add. |
outcome | success or error. |
Example output
Prometheus
The production Compose path ships with a Prometheus service already configured to scrape Mcpjungle:/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.Related pages
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.
