The Arize Phoenix MCP Server provides a unified interface for interacting with the Arize Phoenix platform. With this server, you can:
Prompts Management: Create, list, update, and iterate on prompts, including their templates, model configurations, and invocation parameters. Get specific prompt versions (latest, by ID, by tag).
Datasets: Explore datasets, retrieve examples, and add synthetically generated examples to cover edge cases.
Experiments: List and retrieve experiment results, including metadata, outputs, and annotations for evaluating model performance.
Tags and Versions: Manage prompt versions by adding tags, listing versions, and fetching specific versions.
Integration: Easily integrate with clients like Claude Desktop and Cursor using
npx.Open-Source: Extend functionality by contributing to the open-source project.
Enables environment variable configuration for development, allowing secure management of API keys and base URLs
Provides open-source access to the Phoenix MCP implementation, allowing for contributions and customizations
Phoenix MCP Server is an implementation of the Model Context Protocol for the Arize Phoenix platform. It provides a unified interface to Phoenix's capabilites.
You can use Phoenix MCP Server for:
Projects Management: List and explore projects that organize your observability data
Spans & Annotations: Retrieve spans and their annotations for analysis and debugging
Prompts Management: Create, list, update, and iterate on prompts
Datasets: Explore datasets, and syntesize new examples
Experiments: Pull experiment results and visualize them with the help of an LLM
Don't see a use-case covered? @arizeai/phoenix-mcp is open-source! Issues and PRs welcome.
Installation
This MCP server can be used using npx and can be directly integrated with clients like Claude Desktop, Cursor, and more.
Related MCP server: MCP Server
Development
Install
This package is managed via a pnpm workspace.
This only needs to be repeated if dependencies change or there is a change to the phoenix-client.
Building
To build the project:
Development Mode
To run in development mode:
Debugging
You can build and run the MCP inspector using the following:
Environment Variables
When developing, the server requires the following environment variables:
PHOENIX_API_KEY: Your Phoenix API keyPHOENIX_BASE_URL: The base URL for Phoenix
Make sure to set these in a .env file. See .env.example.
Community
Join our community to connect with thousands of AI builders:
๐ Join our Slack community.
๐ Read the Phoenix documentation.
๐ก Ask questions and provide feedback in the #phoenix-support channel.
๐ Leave a star on our GitHub.
๐ Report bugs with GitHub Issues.
๐ Follow us on ๐.
๐บ๏ธ Check out our roadmap to see where we're heading next.
License
Apache 2.0