VOOZH about

URL: https://glama.ai/mcp/servers/moondef/otel-mcp

⇱ otel-mcp by moondef | Glama

otel-mcp

👁 npm version
👁 CI
👁 License: MIT

MCP server that gives AI agents access to your application's OpenTelemetry traces.

Agent calls: list_traces { has_errors: true }

Recent Traces (2 of 847)

TRACE ID SERVICE DURATION SPANS ERRORS ROOT
a]b7f2e9d4c8 checkout-api 2.34s 12 1 POST /checkout
f3e1a8b2c6d9 checkout-api 1.87s 8 1 POST /checkout

Agent calls: get_trace { trace_id: "a]b7f2e9d4c8" }

Trace ab7f2e9d4c8

Services: checkout-api, inventory-service, postgres
Duration: 2.34s
Spans: 12, 1 error

SPAN TREE
----------------------------------------------------------------
[2.34s] POST /checkout
 [1.92s] OrderService.create
 [1.87s] InventoryService.reserve ← HTTP 500
 [45ms] POST inventory-service/reserve
 [23ms] pg.query SELECT * FROM products...
 [412ms] PaymentService.charge
 [401ms] stripe.charges.create

The agent can query traces, find errors, identify slow operations - without you copying logs into chat.

Why This Exists

AI agents can read code, but they can't see how it executes. When debugging locally, you end up checking traces yourself and explaining what you found. That's the bottleneck.

otel-mcp removes that step by letting agents query execution data directly.

Read more:

Related MCP server: iris-eval/mcp-server

Architecture

flowchart LR
 subgraph app["Your Application"]
 OTel["OpenTelemetry SDK"]
 end

 subgraph otel-mcp
 Receiver["OTLP Receiver\n/v1/traces"]
 Store[("Trace Store\n(in-memory)")]
 MCP["MCP Server\n(stdio)"]
 HTTP["HTTP API\n/mcp/*"]
 end

 subgraph client["Client Mode"]
 MCP2["MCP Server\n(stdio)"]
 end

 Agent["AI Agent\n(Claude, Cursor)"]

 OTel -->|"OTLP/HTTP\n:4318"| Receiver
 Receiver --> Store
 Store --> MCP
 Store --> HTTP
 MCP <-->|"MCP protocol"| Agent
 HTTP <-->|"HTTP proxy"| MCP2
 MCP2 <-->|"MCP protocol"| Agent

Primary mode: First instance runs the OTLP receiver and MCP server. Traces are stored in memory with LRU eviction.

Client mode: Additional instances detect the primary via health check and proxy MCP tool calls over HTTP. Multiple AI agents can share the same trace data.

Quick Start

Prerequisites: Node.js 18+

1. Add to your MCP client

Go to Cursor Settings → MCP → Add new global MCP server and paste:

{
 "mcpServers": {
 "otel": { "command": "npx", "args": ["otel-mcp"] }
 }
}

Or add to ~/.cursor/mcp.json directly.

claude mcp add otel -- npx otel-mcp

Add to your MCP config:

{
 "mcpServers": {
 "otel": { "command": "npx", "args": ["otel-mcp"] }
 }
}

2. Try it out

Run the example app to generate test traces:

# Clone and run example
git clone https://github.com/moondef/otel-mcp.git
cd otel-mcp/examples/node-app
npm install && npm start

Then ask your AI agent: "Show me recent traces" or "Are there any errors?"

3. Instrument your app

Point your OpenTelemetry exporter at http://localhost:4318/v1/traces:

import { NodeSDK } from '@opentelemetry/sdk-node';
import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-http';
import { getNodeAutoInstrumentations } from '@opentelemetry/auto-instrumentations-node';

const sdk = new NodeSDK({
 traceExporter: new OTLPTraceExporter({
 url: 'http://localhost:4318/v1/traces',
 }),
 instrumentations: [getNodeAutoInstrumentations()],
});
sdk.start();
from opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter
exporter = OTLPSpanExporter(endpoint="http://localhost:4318/v1/traces")

OpenTelemetry is a standard for collecting traces from applications. A trace shows the path of a request through your system - which functions ran, how long each took, what failed.

Getting started: Node.js · Python · Go · Java

Tools

Tool

Description

list_traces

List recent traces. Filter by service, has_errors, min_duration_ms, since_minutes.

get_trace

Get span tree for a trace ID (prefix match supported).

query_spans

Search spans with where expressions: duration > 100, status = error, http.status_code >= 400.

get_summary

Service overview with trace counts and recent errors.

clear_traces

Clear all collected traces.

Multiple sessions

Multiple MCP clients share the same traces. First instance runs the collector on port 4318, others connect to it. Filter by service to focus on specific apps.

Configuration

Variable

Default

Description

OTEL_MCP_PORT

4318

Collector port

OTEL_MCP_MAX_TRACES

1000

Max traces to retain

OTEL_MCP_MAX_SPANS

10000

Max spans to retain

License

MIT

A
license - permissive license
A
quality
D
maintenance

Maintenance

–Maintainers
–Response time
–Release cycle
–Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/moondef/otel-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server