Arize Phoenix plugin
A Claude Code plugin for the Phoenix LLM observability platform: remote MCP plus skills for traces, evals and instrumentation
- 12,064 ★ on the repository
- Last commit
Extended access
Why this level
- Reads traces that may contain user data
- The tracing skill changes project code and dependencies
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/arize-phoenixDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads traces that may contain user data
- The tracing skill changes project code and dependencies
This is third-party code. Review the repository files before installing.
What it does
Phoenix is an open-source, self-hosted platform for tracing and evaluating LLM apps. The plugin connects Claude Code to your Phoenix instance through its remote MCP server and adds three skills. phoenix-cli teaches the agent to fetch traces, analyze errors, inspect datasets and experiments and query GraphQL with the px CLI. phoenix-evals helps build and run evaluators, and phoenix-tracing instruments apps with OpenInference conventions. The CLI setup command detects your framework and provider and wires up trace export.
Who it is for. For developers of LLM apps and agents who debug and evaluate them in Phoenix.
Good fit when
- You want the agent to analyze failing LLM app traces itself
- You need to add OpenInference tracing to an existing project
- You need to build evaluators and run an experiment on a dataset
Not a fit when
- You do not use Phoenix and do not plan to deploy it
- You need observability for regular web services rather than LLMs
Example request
Find error traces in Phoenix from the last hour and explain what is breakingLimitations
Requires a deployed Phoenix 19.0.0 or later, defaulting to localhost:6006. The MCP server signs in via browser OAuth; for headless use register the server manually with an API key. The px CLI reads PHOENIX_ENDPOINT and PHOENIX_API_KEY from the environment.
How to disable. Run claude plugin uninstall arize-phoenix@arize-phoenix or disable the plugin via /plugin.
FAQ
How do I set my server address?
Claude Code asks when enabling the plugin; you can also pass --config endpoint=... on install or change it with /plugin configure.
Can I use it without the plugin?
Yes, run the CLI with npx @arizeai/phoenix-cli and point any MCP client at your instance's /mcp endpoint.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code plugin marketplace with ready sets of agents, slash commands, hooks and skills, plus a search site
AI Builder Club Skills
AI Builder Club — Skills
A Claude Code plugin marketplace to make a repo agent-ready and run compounding agent loops
Multi-agent orchestration for Claude Code: teams, roles, autopilot and task routing across skills and subagents
Plugin marketplace and CLI for Claude Code: agent swarms, background workers, vector memory, security review and test generation
A Claude Code plugin that runs one task across several external models and surfaces disagreements before you ship
A Claude Code plugin that asks several AI models the same question and shows their answers side by side with a synthesis of agreement and divergence
README in short
The README presents Phoenix as an open observability platform: OpenTelemetry tracing, evals, datasets, experiments, a prompt playground and a built-in agent. Run it locally via pip or uvx, deploy with Docker and Helm. For coding agents it offers three surfaces: CLI, skills and a remote MCP server. The plugin README covers install, endpoint configuration and OAuth sign-in.