Skip to main content
Phoenix speaks MCP, so you can wire assistants like Claude Code, Cursor, and VS Code into Phoenix. There are two things you might want your assistant to do — pick the server that matches, or run both.

Work with your Phoenix data

Remote MCP Server — query and operate on your projects, traces, sessions, datasets, experiments, prompts, and annotations. Built into the Phoenix server at /mcp; nothing to install.Recommended · beta

Search the Phoenix docs

Phoenix Docs MCP — let your assistant answer questions from the Phoenix documentation in real time. A hosted URL you point your client at.
The two are complementary. Run the Docs MCP alongside the Remote MCP Server to give your assistant both your live Phoenix data and the documentation.
For most coding-agent workflows, the px CLI is the recommended interface — fetching traces, debugging failures, inspecting experiments, and managing datasets and prompts. Use the MCP servers for ad-hoc data access from your IDE. See Coding Agents for setting them up together.

​
Older Phoenix versions

If your Phoenix version doesn’t yet serve the built-in /mcp endpoint, use the @arizeai/phoenix-mcp npm package — a local stdio server that connects to the same Phoenix data. It’s in maintenance mode: it still receives bug fixes, but new capabilities land in the Remote MCP Server. Prefer the Remote MCP Server whenever your Phoenix version serves /mcp.