OpenTelemetry MCP Server (Traceloop)
Queries OpenTelemetry traces across Jaeger, Tempo and Traceloop from one server.
Add it to your client
Communitypipx run opentelemetry-mcp
- Transport
- both
- Runtime
- Python
- Auth
- Not required
- Tools
- 10
- License
- Apache-2.0
Maintained by Traceloop rather than by the OpenTelemetry project, this Python server sits in front of a trace backend and answers trace and span lookups, error hunting and service listing. Because it understands OpenLLMetry conventions it can also report token usage, per-model breakdowns and the slowest or most expensive traces in an LLM application. Jaeger and Tempo need only a URL; the Traceloop backend is the one that asks for an API key.
Similar MCP servers
OpenRouter MCP Server
MCP serverRoutes chat requests to OpenRouter's model catalogue over MCP.
SigNoz MCP Server
MCP serverQueries an open-source SigNoz instance for traces, metrics and logs in one place.
Opik MCP Server
MCP serverReads Opik traces, spans and experiments, writes prompts, and runs evaluations from the agent side.
Comments(0)
Sign in to comment