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. Each tool also inherits the stage of the REST operation behind it, which the tool catalog lists per tool. 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, read the current version of a prompt, or create a dataset, 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 either an Arize API key or an Arize sign-in through OAuth. Connect your client walks through setup for Claude Code, Cursor, Claude Desktop, and Codex.

ā€‹
What your agent can do

Your agent can read, create, update, and delete Arize AX resources, and run actions such as annotating data or triggering tasks. What is available depends on your permissions in Arize. The tool catalog lists every tool, its arguments, and the stage of its REST operation.

ā€‹
Safety and permissions

Write and delete tools act on real data in your account. Keep these points in mind before you connect an agent:
  • Tool annotations such as destructiveHint are hints for your client. They do not block anything on the server. See conventions.
  • The server has no confirmation step and no dry run. A tool call runs as soon as your client sends it.
  • The token carries your full permissions in Arize. The server adds no limits of its own, so the agent can do whatever your role allows.
To limit the risk, connect with an API key tied to a role that has only the access the agent needs. In your client, approve destructive tools one call at a time instead of allowing them automatically.

ā€‹
How access works

You authenticate with an Arize API key, or with an OAuth sign-in where your client supports it. Either way, the credential is forwarded to the REST API on every call. See authentication for both options and endpoints for the regional URLs.
Not sure whether to use the MCP server, Skills, or the CLI? See the FAQ.

ā€‹
Next steps

Connect your client

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

Endpoints

Regional URLs for the MCP server.

Authentication

Sign in with an API key or OAuth.

Tool catalog

Every tool, grouped by resource, with its stage.

FAQ

Common questions and fixes for connection errors.

REST API reference

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

Skills

Give your agent repeatable Arize AX workflows that run through the CLI.