Skip to main content
The MCP server is in Alpha. It is meant for developers exploring new capabilities, and breaking changes are expected. Tool names, arguments, and response shapes can change without a deprecation window. See API version stages for what each stage means.
The Arize AX MCP server is a hosted Model Context Protocol server that puts your Arize AX resources inside your agent’s context. Connect it once and Claude Code, Cursor, Claude Desktop, Codex, or any other MCP client can look up a project, pull the spans from a failing trace, check what an evaluator scored, or read the current version of a prompt, without you copying IDs between a browser tab and a chat window. It is a thin layer over the REST API v2.

​
Connect your client

The server is hosted, so there is nothing to install. You need an endpoint URL and an Arize API key. Connect your client walks through setup for Claude Code, Cursor, Claude Desktop, and Codex.

​
What your agent can read

The server exposes 45 read-only tools, plus a server_info tool for checking which version you reached. The tools catalog has every tool name and its arguments.

​
Read-only by design

Nothing the server exposes can change your data. There are no create, update, or delete tools, so an agent that goes off script cannot drop a dataset or overwrite a prompt. Two categories are left out on purpose:
  1. Writes and deletes, which need a docstring stating their blast radius before an agent should be trusted to call them.
  2. The account administration surface, including API keys, users, roles, and role bindings. Reading those is an information exposure risk even though it changes nothing.
To create or modify resources from an agent, use Arize Skills instead. Skills drive the Arize AX CLI, which covers the full read and write surface.

​
How access works

You authenticate with an Arize API key, passed as a bearer token that gets forwarded to the REST API on every call. See endpoints for the regional URLs and authentication for how to get a key.

​
MCP server, skills, or the CLI?

There are three ways to put Arize AX in front of an agent, and each solves a different problem:
  • MCP server when you want the agent to answer questions about data already in AX. It can debug a trace, check experiment results, or find the project that contains a span. There is no installation step, and the tools remain available across sessions.
  • Skills when you want the agent to do the work: add tracing to an app, build a dataset, run an experiment, create an evaluator, optimize a prompt. Skills can write.
  • The Arize AX CLI when you are scripting or wiring Arize into CI/CD and no agent is involved.
Using the MCP server and skills together is a reasonable setup. The agent reads through MCP tools and acts through the CLI.

​
Next steps

Connect your client

Per-client setup for Claude Code, Cursor, Claude Desktop, and Codex.

Endpoints

Regional URLs for the MCP server.

Authentication

Get an API key and see how bearer token auth works.

Tool catalog

Every tool, grouped by resource.

REST API reference

The API behind the tools, including authorization, errors, and rate limits.

Skills

Give your agent the write side of Arize AX through the CLI.