Arize AX

All Arize integration capabilities

About

This is an MCP connector that gives the Sazabi agent tools from Arize's hosted Arize AX MCP server. Arize AX is an observability and evaluation platform for LLM and agent applications. Arize runs the server in three regions: Global (https://api.arize.com/mcp), Europe (https://api.eu-west-1a.arize.com/mcp), and Canada (https://api.ca-central-1a.arize.com/mcp). Sazabi stores your Arize API key securely, checks it with Arize in the region you choose, and sends it as the Authorization: Bearer token. The agent sees exactly the spaces and projects the key can see, and every tool is read-only.

What the agent can do:

• Find failing traces in an Arize project and inspect their spans (list_traces, list_spans)
• Read the prompt version serving under a label such as production, and its history (get_prompt_label, list_prompt_versions)
• Check experiment runs, evaluator versions, and dataset examples
• Read monitors, tasks, annotation queues, spaces, and projects

This connector is for Arize AX. Arize Phoenix, the open-source self-hosted product, runs a separate MCP server that this connector does not cover.

Prerequisites

• An Arize AX account, and the region it runs in: the host you sign in to (app.arize.com is Global, app.eu-west-1a.arize.com is Europe, app.ca-central-1a.arize.com is Canada)
• An Arize API key from Settings > API Keys in Arize AX. A user key acts with your own permissions; a service key keeps working if you leave the account and suits a shared agent.

Set up in the dashboard

Configure connectors in the dashboard under Settings > MCP connectors.

Set up with the CLI

Arize AX authenticates with an Arize API key. With the Sazabi CLI installed and authenticated (see sazabi mcp-connectors reference), connect it in one command, passing the credential as a header:

sazabi mcp-connectors connect arize --header "Authorization=Bearer <api-key>"

That connects to the Global region. For Europe or Canada, add the region's server URL:

sazabi mcp-connectors connect arize \
  --header "Authorization=Bearer <api-key>" \
  --server-url https://api.eu-west-1a.arize.com/mcp

Canada uses https://api.ca-central-1a.arize.com/mcp. The CLI checks the key, connects to the MCP server, and prints the connection with the tools it discovered. Use NAME=@<file> to read a value from a file, or --header-file <file.json> for a JSON object of header names and values. To rotate the stored key later, use sazabi mcp-connectors update-credentials <connection-id>; find the connection ID with sazabi mcp-connectors list.

Verify

Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered (for example list_projects, list_traces, get_prompt_label). Then, in a thread, ask the agent to list your Arize projects and confirm it returns them by name.

Troubleshooting

Arize rejected this API key: The key is wrong, revoked, or was created in another region. Check that you chose the region you sign in to, then create a new key in Arize AX if needed.

A tool returns not found for something you can see in Arize: Arize answers "not found" when the key cannot read a space or project. Use a key whose account or service key can read it.

Requests fail with a rate limit: Arize limits each key to 100 requests per minute. Ask the agent to narrow the time window or filters so it needs fewer pages.

Connection shows needs attention: The key may have been revoked; create a new one in Arize AX and update the connector's credentials from Settings > MCP connectors.

Further reading