How to integrate Arize AX MCP with Claude Agent SDK

This guide walks you through connecting Arize AX to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Arize AX agent that can summarize failed spans from latest traces, compare experiment results across prompt versions, create dataset from production traces through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Arize AX account through Composio's Arize AX MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for free Get a demo

Arize AX

Api Key

Arize AX is an AI engineering platform for tracing, evaluating, and improving AI applications. Use it to debug LLM behavior, compare experiments, and improve production AI quality.

24 Tools

Managed auth

Connect Arize AX without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Try for free

Introduction

This guide will help you understand how to give your Claude Agent SDK agent real control over a Arize AX account through Composio's Arize AX MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Arize AX with

OpenAI Agents SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

Get and set up your Claude/Anthropic and Composio API keys
Install the necessary dependencies
Initialize Composio and create a Tool Router session for Arize AX
Configure an AI agent that can use Arize AX as a tool
Run a live chat session where you can ask the agent to perform Arize AX operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

Native MCP Support: Built-in support for Model Context Protocol servers
Permission Modes: Control tool execution permissions
Streaming Responses: Real-time response streaming for interactive applications
Context Manager: Clean async context management for sessions

What is the Arize AX MCP server, and what's possible with it?

The Arize AX MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Arize AX account. It provides structured and secure access to your projects, datasets, prompts, experiments, traces, and spans, so your agent can inspect AI activity, manage evaluation data, maintain prompts, run experiments, and review results on your behalf.

Project and space discovery: Have your agent find accessible spaces and projects, then retrieve details about the AI applications you monitor.
Dataset management: Let the agent create and rename datasets, add or update examples, and review examples from current or named dataset versions.
Prompt versioning: Direct your agent to create prompts, publish new immutable versions, update prompt descriptions, and review current or previous versions.
Experiment tracking: Instruct your agent to create experiments, append runs, and inspect experiment outputs for evaluation and comparison.
Trace and span analysis: Have your agent review bounded sets of traces and spans within chosen time ranges and filters to investigate application behavior.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS

Prerequisites

Before starting, make sure you have:

Composio API Key and Claude/Anthropic API Key
Primary know-how of Claude Agents SDK
A Arize AX account
Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key

Go to the Anthropic Console and create an API key. You'll need credits to use the models.
Keep the API key safe.

Composio API Key

Log in to the Composio dashboard.
Navigate to your API settings and generate a new API key.
Store this key securely as you'll need it for authentication.

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

@composio/core provides Composio integration for Anthropic
@anthropic-ai/claude-agent-sdk is the core agent framework
dotenv/config loads environment variables

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

COMPOSIO_API_KEY authenticates with Composio
USER_ID identifies the user for session management
ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();

What's happening:

We're importing all necessary libraries including the Claude Agent SDK and Composio
The dotenv.config() function loads environment variables from your .env file
This setup prepares the foundation for connecting Claude with Arize AX functionality

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Arize AX
  const session = await composio.create(USER_ID, {
    toolkits: ['arize_ax'],
  });
  const mcpUrl = session?.mcp.url;

What's happening:

The function checks for the required COMPOSIO_API_KEY environment variable
We're creating a Composio instance using our API key
The create method creates a Tool Router session for Arize AX
The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Arize AX tools via Composio.',
  maxTurns: 10,
};

What's happening:

We're configuring the Claude Agent options with the MCP server URL
permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
The system prompt instructs the agent that it has access to Arize AX
maxTurns: 10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

What's happening:

The readline interface is created to handle user input and output
The query function is used to send the user's input to the agent
The chat loop continues until the user types 'exit' or 'quit'

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

What's happening:

The chat function is the entry point for the application
The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Arize AX and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['arize_ax']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Arize AX tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Arize AX through Composio's Tool Router.

Key features:

Native MCP support through Claude's agent framework
Streaming responses for real-time interaction
Permission bypass for smooth automated workflows

You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

TOOLS

Supported Tools

Every Arize AX action and event your agent gets out of the box.

Add Dataset Examples

Append arbitrary-field examples to an Arize dataset or a specified dataset version.

Add Experiment Runs

Append one or more runs to an existing Arize experiment.

Create Dataset

Create an Arize dataset in a space with an explicit initial array of examples.

Create Experiment

Create an Arize experiment with initial runs, associated with exactly one dataset or space.

Create Prompt

Create an Arize prompt and its initial version in a space.

Create Prompt Version

Create a new immutable version of an existing Arize prompt.

Get Dataset

Get one Arize dataset and its versions by dataset ID.

Get Experiment

Get one Arize experiment by its ID, without its experiment runs.

Get Project

Get one accessible Arize project by its ID.

Get Prompt

Get an Arize prompt with its current, explicitly selected, or labeled version.

Get Space

Get one accessible Arize space by its ID.

List Dataset Examples

List one page of examples from an Arize dataset or a specific dataset version, preserving user-defined example fields.

List Datasets

List one page of Arize datasets, optionally filtered by space or dataset name.

List Experiment Runs

List one page of runs and outputs for an Arize experiment, preserving additional run fields.

List Experiments

List one page of Arize experiments, optionally filtered by dataset, space, or name.

List Projects

List one page of accessible Arize projects, optionally filtered by space or project name.

List Prompts

List one page of Arize prompts, optionally filtered by space or prompt name.

List Prompt Versions

List one page of versions for an Arize prompt, newest first.

List Spaces

List one page of Arize spaces accessible to the connected API key, optionally filtered by organization or name.

List Spans

Read one bounded page of spans for an Arize project using optional time and filter constraints.

List Traces

Read one bounded page of traces and nested spans for an Arize project using optional time and filter constraints; nested spans may be truncated per trace.

Update Dataset

Rename an existing Arize dataset.

Update Dataset Examples

Update existing Arize dataset examples by ID, optionally creating a named dataset version.

Update Prompt

Update or clear an Arize prompt's description.

FRAMEWORKS

How to build Arize AX MCP Agent with another framework

OpenAI Agents SDK

Use Arize AX MCP with OpenAI Agents SDK

Claude Code

Use Arize AX MCP with Claude Code

Claude Cowork

Use Arize AX MCP with Claude Cowork

Codex

Use Arize AX MCP with Codex

OpenClaw

Use Arize AX MCP with OpenClaw

Hermes

Use Arize AX MCP with Hermes

CLI

Use Arize AX MCP with CLI

Google ADK

Use Arize AX MCP with Google ADK

LangChain

Use Arize AX MCP with LangChain

Vercel AI SDK

Use Arize AX MCP with Vercel AI SDK

Mastra AI

Use Arize AX MCP with Mastra AI

LlamaIndex

Use Arize AX MCP with LlamaIndex

CrewAI

Use Arize AX MCP with CrewAI

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

AltTextLab

Api Key

AltTextLab is an AI service that generates accessible, SEO-aware alt text for images. It helps teams make image content easier to understand, index, and publish.

Apiframe

Api Key

Apiframe is an API platform for generating and managing AI images, videos, music, uploads, assets, jobs, and custom LoRAs. It gives developers one clean API for creative AI workflows without juggling multiple model providers.

AssemblyAI

Api Key

AssemblyAI is a speech-to-text and audio intelligence API for uploaded or hosted media. Use it to turn audio and video into accurate transcripts, summaries, and insights.

Avoma

Api Key

Avoma is an AI meeting assistant for recording, transcribing, analyzing, and managing meetings, calls, notes, scorecards, and conversation intelligence. It helps teams turn conversations into searchable notes, follow-ups, coaching insights, and revenue intelligence.

FAQ

Frequently asked questions

With a standalone Arize AX MCP server, the agents and LLMs can only access a fixed set of Arize AX tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Arize AX and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Arize AX tools.

Yes, absolutely. You can configure which Arize AX scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Arize AX data and credentials are handled as safely as possible.

Start with Arize AX.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Arize AX tool your agent needs.Free to start.

Start building

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati

Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya

Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave

CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu

Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola

Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche

Co-Founder, Ingram Technologies

How to integrate Arize AX MCP with Claude Agent SDK

Connect Arize AX without auth hassles

Introduction

Also integrate Arize AX with

TL;DR

What is Claude Agent SDK?

What is the Arize AX MCP server, and what's possible with it?

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for Claude/Anthropic and Composio

Install dependencies

Set up environment variables

Import dependencies

Create a Composio instance and Tool Router session

Configure Claude Agent with MCP

Create client and start chat loop

Run the application

Complete Code

Conclusion

Supported Tools

How to build Arize AX MCP Agent with another framework

OpenAI Agents SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

LlamaIndex

CrewAI

Explore Other Toolkits

AltTextLab

Apiframe

AssemblyAI

Avoma

Frequently asked questions

What are the differences in Tool Router MCP and Arize AX MCP?+

Can I use Tool Router MCP with Claude Agent SDK?+

Can I manage the permissions and scopes for Arize AX while using Tool Router?+

How safe is my data with Composio Tool Router?+

Start with Arize AX.It takes 30 seconds.

Teams ship real agents on Composio