Arize Phoenix has a built-in MCP server that lets your agents query traces with SQL
Blog post from Arize
Arize Phoenix has added a built-in Model Context Protocol server with read-only SQL tools that let coding agents query telemetry traces directly rather than retrieve and manually aggregate paginated span data. The describeSqlSchema and executeSql tools run through a restricted code-mode sandbox, keeping intermediate results out of model context and returning only final outputs, while SQL is parsed, rebuilt, limited to approved telemetry tables, checked by database controls, and bounded by runtime and result-size limits. In an eight-question benchmark involving counts, durations, trends, joins, and breakdowns, SQL plus code mode averaged about $0.23 per question versus $3.97 for retrieval-only tools, a roughly 17-fold cost reduction, with one error-count query falling from 89 turns, 14 minutes, and $10.35 to 7 turns, 33 seconds, and $0.23. Phoenix argues that database-side aggregation is particularly useful for verbose LLM trace data, though retrieval may remain cheaper for simple lookups, and the feature is available in Phoenix versions 20.2.0 and later through OAuth-connected MCP clients such as Claude Code, Cursor, and other supported agents.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.