mcp-telemetry

# mcp-telemetry [](LICENSE) [](#) [](#) Zero-config observability for MCP servers. OTel GenAI conventions. **Redaction on by default.** MCP hit **97 million monthly SDK downloads** — and the production playbook is still being written. OWASP's MCP Top 10 puts **"Lack of Audit and Telemetry"** at the top of the risk list. This repo is that gap, filled in three lines. ## Install ```bash pip install mcp-telemetry # core — zero dependencies pip install 'mcp-telemetry[otlp]' # + OTLP/HTTP export (httpx) ``` ## Use — no changes to your server logic ```python import mcp_telemetry as mt mt.auto() # patches the official `mcp` SDK, writes JSONL @mt.wrap_tool_call("issues.fetch", server="gh") def fetch_issue(issue_id, token=""): ... ``` Every call emits an OTel GenAI `gen_ai.client.tool_call` span with: - **input fingerprint** — SHA-256 hash, never the raw payload - **secret scrubbing** — `token`, `secret`, `api_key`-style keys → `[REDACTED]` - latency, status, error type, server name Manual spans and traces work too: ```python with mt.session(): # one trace for the whole agent turn with mt.span("chat.step"): ... ``` ## Distributed traces cross servers Propagation is built in. A `traceparent` header on an inbound MCP request starts a **continuation**, not a new trace — the span stamps `parent_span_id` and the trace id carries through: ```python from mcp_telemetry.propagator import parse_traceparent store.start(parse_traceparent(my_header).trace_id) ``` Pair with [`mcp-hub`](https://github.com/threadwire/mcp-hub): the gateway relays W3C `traceparent` verbatim to every upstream, and the responder below records the far side. One trace, end to end. See [`examples/responder.py`](examples/…