Recommended Setup
Most users should set up all three:CLI
Terminal access to traces, experiments, datasets, and prompts.
MCP
In-editor Phoenix documentation lookup and optional direct Phoenix instance operations.
Skills
Reusable instructions so agents apply Phoenix best practices consistently.
Shared Environment Configuration
Set environment variables to connect to your Phoenix instance:CLI
Install the Phoenix CLI globally:px:
- investigate trace failures and performance regressions
- inspect and compare experiment runs
- list and fetch datasets for evaluation workflows
- inspect and retrieve prompt versions and content
MCP
MCP has two different Phoenix integrations, and they serve different goals.| MCP Integration | Purpose | When to use |
|---|---|---|
Phoenix Docs MCP | Search Phoenix documentation from your coding agent | Recommended for all users |
Phoenix MCP Server | Operate directly on your Phoenix instance (projects, traces, sessions, prompts, datasets, experiments, and more) | Use when you want agent-driven Phoenix data operations |
Phoenix Docs MCP (Documentation Access)
Phoenix Docs MCP URL:- Claude Code
- Cursor
- VS Code
- Windsurf
Project scope:User scope:Verify:
Reference docs: Claude Code MCP, Cursor MCP, VS Code MCP servers, Windsurf MCP.
Phoenix MCP Server (Direct Phoenix Operations)
For direct operations against your Phoenix instance (traces, sessions, prompts, datasets, experiments, and more), use the dedicated setup guide:Install both MCP integrations if you want your coding agent to both look up docs and perform direct Phoenix instance operations.
Skills
Install Phoenix skills using skills add:.claude/skills/, .cursor/skills/, or .github/skills/).
Available Skills
phoenix-cli
Debug LLM apps using Phoenix CLI for traces, experiments, datasets, and prompts. Recommended.
phoenix-evals
Build and run evaluators for AI/LLM apps across code-based and LLM-as-judge workflows.
phoenix-tracing
Implement OpenInference tracing conventions and instrumentation in Python and TypeScript.
skills add Options
| Option | Description |
|---|---|
-g, --global | Install to user directory instead of project |
-a, --agent <agents...> | Target specific agents (for example, claude-code, cursor) |
-s, --skill <skills...> | Install specific skills by name |
-l, --list | List available skills without installing |
-y, --yes | Skip confirmation prompts |
Examples
Docs and Source Code in node_modules
Phoenix’s TypeScript packages ship docs and source code inside node_modules once installed. Coding agents can inspect version-matched docs, examples, and source code directly under node_modules, without relying on the public website.
Common paths:
Related
CLI Reference
Full command reference for Phoenix CLI.
Retrieve Traces via CLI
Detailed guide for fetching traces from Phoenix.
Phoenix MCP Server
Interact with projects, traces, sessions, prompts, datasets, and experiments via the Phoenix MCP Server.

