Skip to main content

​
Authentication

You authenticate with an Arize API key or service key, passed as a bearer token. The server holds no permission logic of its own: it forwards your key to the REST API on every call, so an agent sees exactly the spaces and projects you can see, and a 404 on a resource you lack read access to means the same thing it means over HTTP. Revoking the key cuts the agent off immediately.

​
Get an API key

  1. Go to Settings → API Keys in Arize AX.
  2. Click + New API Key, name it after the client you are connecting, then click Create Key.
  3. Copy the key. Arize shows it once.
Both user keys and service keys work. A user key inherits your own permissions, which is usually what you want for a personal editor. Use a service key when the connection outlives your account, such as a shared agent or a team workstation. Export it so your client config does not carry the secret:
Keys grant an agent read access to every space you can see. Treat one like a password: keep it out of committed files, and revoke it in Settings → API Keys if it leaks.

​
Next steps

Endpoints

Regional URLs for the MCP server.

Connect your client

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

Tool catalog

Every tool, grouped by resource.