Evaluate Phoenix MCP server for trace exploration #7
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/otel-a2a-relay#7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-05-06T23:56:19Z - https://github.com/coilysiren/otel-a2a-relay/issues/3
Arize publishes a Phoenix MCP server. Phoenix is already a first-class viewer for the OTel traces this relay emits, so an MCP-driven loop on top of it could turn relayed A2A traffic into something an agent (or Claude Code) can query directly.
What to evaluate
Out of scope
Outcome
A short writeup (yes / no / with-caveats) plus a recorded demo session if it works. If it works, follow-up issue to document the wiring in the README.
Iceboxed in the 2026-05-29 backlog burn-down: Evaluate/explore Phoenix MCP server, speculative. Reopen anytime if it becomes real.