SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Segment MCP with Claude Agent SDK

Connect Claude Agent SDK to Segment MCP. Fetch daily api usage for each source, add metadata labels to a specific source, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Segment logoSegment
Api Key

Segment is a customer data platform that helps businesses collect, clean, and control their customer data. It empowers teams to unify analytics and personalize user experiences with reliable, centralized data.

17 Tools

Introduction

This guide walks you through connecting Segment to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Segment agent that can track events and page views, identify and group users, import historical data, manage sources, and check delivery metrics through natural language commands.

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

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

Also integrate Segment with

Claude CodeClaude CoworkOpenAI Agents SDKCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

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 Segment
  • Configure an AI agent that can use Segment as a tool
  • Run a live chat session where you can ask the agent to perform Segment 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 Segment MCP server, and what's possible with it?

The Segment MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Segment account. It provides structured and secure access to your customer data platform, so your agent can perform actions like identifying users, tracking analytics events, managing sources and destinations, and monitoring API usage on your behalf.

  • User identification and trait management: Your agent can identify users, set or update their traits, and manage user profiles using Segment's Identify and Group tools.
  • Analytics event tracking and batching: Effortlessly track individual or batched analytics events, enabling automated insights and seamless event monitoring across platforms.
  • Source and destination administration: Let your agent add labels to sources, delete sources, retrieve detailed destination configurations, and list warehouses connected to a source.
  • Alias and merge user identities: Merge anonymous and known identities by aliasing user IDs for more accurate customer journeys and unified profiles.
  • Usage monitoring and delivery metrics: Fetch daily API call usage per source and view delivery metrics summaries for destinations to keep tabs on system health and integration performance.

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:

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

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Segment account
  • Some knowledge of Python
2

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.
3

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
4

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
5

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 Segment functionality
6

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 Segment
  const session = await composio.create(USER_ID, {
    toolkits: ['segment'],
  });
  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 Segment
  • The returned url is the MCP server URL that your agent will use
7

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 Segment 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 Segment
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

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'
9

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 Segment 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: ['segment']
  });
  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 Segment 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 Segment 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 Segment action and event your agent gets out of the box.

Add Labels to Source

Tool to add existing labels to a Source.

Segment Alias

Tool to alias a previous user ID to a new user ID.

Batch Segment Analytics Events

Tool to send multiple analytics calls in a single batch request.

Delete Source

Tool to delete a Segment Source.

Get Daily Per Source API Calls Usage

Fetch daily API call counts by Segment Source for a given reporting period.

Get Destination

Retrieve a Segment Destination's configuration by its unique ID using the configured region.

Segment Group

Tool to associate an identified user with a group via Segment HTTP Tracking API.

Segment Identify

Tool to identify a user and set/update traits via Segment HTTP Tracking API.

Import Historical Data

Import historical events in bulk into Segment with their original timestamps, for backfilling past activity.

List Connected Warehouses From Source

List warehouses connected to a Segment Source by source ID.

List Delivery Metrics Summary from Destination

Get an event delivery metrics summary for a Destination and Source.

List Schema Settings in Source

Retrieve schema configuration settings for a Segment Source by its ID, including settings for track, identify, and group calls.

Segment Page View

Tool to record a page view via Segment HTTP Tracking API.

Remove Source Write Key

Remove a specified write key from a Segment Source, for example during security maintenance or key rotation.

Segment Screen Event

Tool to record a mobile app screen view.

Segment Track Event

Tool to record a custom user event via Segment HTTP Tracking API.

Update Source

Update an existing Segment Source by ID, changing its name, slug, enabled status, or type-specific settings.

FRAMEWORKS

How to build Segment MCP Agent with another framework

Claude Code logo

Claude Code

Use Segment MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Segment MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Segment MCP with OpenAI Agents SDK

Codex logo

Codex

Use Segment MCP with Codex

OpenClaw logo

OpenClaw

Use Segment MCP with OpenClaw

Hermes logo

Hermes

Use Segment MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Segment MCP with Atomic Agent

Google ADK logo

Google ADK

Use Segment MCP with Google ADK

LangChain logo

LangChain

Use Segment MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Segment MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Segment MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Segment MCP with LlamaIndex

CrewAI logo

CrewAI

Use Segment MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Segment MCP with Pydantic AI

AutoGen logo

AutoGen

Use Segment MCP with AutoGen

FAQ

Frequently asked questions

Start with Segment.It takes 30 seconds.

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

Start building