# Let a coding agent read traces over MCP or SQL

> Let a coding agent read traces over MCP or SQL: 2 companies fully do it, 14 with a limit, 24 carry the tag. Every listing in Agent observability & evals with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/agent-observability.agent-queries-traces/
- Markdown: https://www.anchorterminal.com/niches/agent-observability.agent-queries-traces/index.md (~1,950 tokens)
- Slim: https://www.anchorterminal.com/niches/agent-observability.agent-queries-traces/index.min.md (~430 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/agent-observability.agent-queries-traces/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 14 | 24 | 6 | 7 |

## What counts as done

The agent lists tools, discovers the schema and returns the matching traces or an aggregate, on a read-only credential, without the whole trace body in context.

Measured, for our own tests: it takes under 3 tool calls.

How agents ask for it: ask Claude Code why errors spiked; query the traces with SQL; connect the MCP server read-only; fix this failing span from my editor

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Overmind (Overmind Technology Ltd (England and Wales, company 16585996))**: MCP over OAuth or API keys with a read scope that exposes only inspection tools: query_traces, query_failures, inspect_capability_health and project resources, plus overmind://interface/current for the catalogue.
- **Respan API + MCP (Keywords AI Inc. (d/b/a Respan))**: A hosted MCP at mcp.respan.ai with a readonly endpoint and Read-scope keys, tool_search to find tools and log_list with filters; the CLI lists logs and traces and gets one by id.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **agents-tree (No legal entity found. The LICENSE and pyproject.toml name Karel Blavka)**: agents-tree --json emits a schema-versioned document of sessions and agents that an orchestrating agent can read; no MCP, SQL or credential scope, and prompts appear unredacted.
- **Arize Phoenix (Arize AI, Inc.)**: Remote MCP at /mcp (beta) with search, get_schema and execute code-mode tools, OAuth or API key, and a viewer role for read-only accounts; px CLI prints JSON. Up to 50 call_tool invocations per execute and the endpoint is still labelled beta.
- **Braintrust API + MCP (Braintrust Data, Inc.)**: sql_query over project_logs with spans, traces or summary shapes, 10 rows by default and large results as signed URLs; resolve_object maps names to IDs. No read-only mode, all 50 tools load with the key's full permissions and hosted BTQL allows 20 queries a minute.
- **Galileo API + MCP (Galileo Technologies, Inc.)**: The MCP server mostly creates datasets and prompts; Get Signals is the only read of production data, with a Galileo-API-Key header and no read-only scope. Traces are read through the REST API instead.
- **Helicone AI Gateway + MCP (Helicone, Inc.)**: MCP query_requests and query_sessions take filters, time ranges and optional bodies; HQL is SQL with row-level security but only for selected workspaces. A use_ai_gateway tool can spend money and no read-only key scope is documented.
- **HoneyHive (HoneyHive Inc.)**: No trace MCP, only a docs MCP; a coding agent reads traces through the CLI with HH_PROJECT_API_KEY or the events search API on a read-only hh_ro_ key. No SQL.
- **Laminar API + MCP (LMNR AI, Inc.)**: Three MCP tools: ask_agent, query_laminar_sql (SELECT only, project-scoped) and get_trace_context, authenticated with a project API key over HTTP. No read-only key scope is documented and one user's MCP authentication kept failing (issue 1515).
- **Langfuse API + MCP (Langfuse GmbH (a ClickHouse, Inc. company))**: MCP server with listObservations, selectable fields and an isRootObservation filter on project-scoped keys, but 98 tools load read and write by default and read-only needs a client allowlist; one self-hoster found no trace read tools at all (issue 15142).
- **LangSmith API + MCP (LangChain, Inc.)**: Remote MCP over OAuth or X-Api-Key with runs, traces, threads and datasets tools, scoped to the account's permissions; fetch_runs pages by a character budget. No read-only mode beyond roles, four write-named tools return documentation, and GET /runs/:id allows 30 calls a minute.
- **LangWatch (Reasoning Engine B.V. (doing business as LangWatch))**: discover_schema then search_traces returns a model-sized digest, and Restricted keys limit a category to read. All 110 tools load by default, deletes and key creation included, with no annotations.
- **MLflow Tracing (MLflow Project, a Series of LF Projects, LLC)**: The experimental MCP server has search_traces with filter_string status='ERROR' and extract_fields to keep bodies out of context, and MLFLOW_MCP_TOOLS=traces trims the set. Read-only needs an RBAC user; delete_traces runs without confirmation.
- **Opik API + MCP (Comet ML, Inc.)**: Five MCP tools: read returns a trace with its span tree, list filters by status with a time window, schema gives the filter vocabulary, nothing can be deleted. No read-only mode and the key carries the user's full rights; listing is capped at 30 requests a minute.
- **Pydantic Logfire (Pydantic Services Inc.)**: Remote MCP with a project:read key or OAuth, query_schema_reference before query_run SQL, and an Enterprise-only org-wide read-only policy; queries draw on an unpublished daily budget and return 429. The Fix AI command errored for one user (issue 1485) and another wants psql (1451).
- **W&B Weave (Weights and Biases, LLC)**: The Weights & Biases MCP server at mcp.withwandb.com answers questions about traces and evaluations with a Forge API key; no read-only scope or trace-summary tool is documented on the page read.

- not this job: Agent Tree (No legal entity found. The LICENSE, plugin.json and marketplace.json name "Mike Pollow, Digitalroots"): No MCP, SQL or JSON output.
- not this job: BotGauge (BotGauge AI Inc. (Delaware, United States)): No MCP or SQL; the REST API covers evaluators and rules, not trace reads.
- not this job: DeepEval (Confident AI, Inc.): No MCP or SQL read path over traces.
- not this job: Gauge CLI (Gauge): The API reads eval results with a read-only key, not traces.
- not this job: Navige (Navige Ltd): The MCP route governs tool servers; there is no read surface over recorded calls for a coding agent.
- not this job: Prefactor (Prefactor Pty Ltd): No MCP or SQL; a read_only token can list spans over REST, but there is no schema discovery or summary tool for a coding agent.

## What stops agents finishing

- MCP server with no read-only mode
- MCP exposes no trace read tools
- MCP auth fails for self-hosted
- query budget per day with no published number

## Around it

Before: agent-harnesses.pair-in-terminal. After: agent-observability.debug-failed-run.

## Where this comes from

Weight 6 of 100 in Agent observability & evals: 7 of 86 accounts: Logfire issues on psql and the Fix AI command, the Tiger Data post on Logfire MCP from Claude Code, Langfuse's MCP without trace reads, Laminar MCP auth, the Phoenix export request, the sub-agent cost CLI

As data: https://www.anchorterminal.com/api/v1/use-cases/agent-observability.agent-queries-traces.json, or the MCP tool get_use_case with id agent-observability.agent-queries-traces. Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
