# How to integrate Segment MCP with Claude Code ```json { "title": "How to integrate Segment MCP with Claude Code", "toolkit": "Segment", "toolkit_slug": "segment", "framework": "Claude Code", "framework_slug": "claude-code", "url": "https://composio.dev/toolkits/segment/framework/claude-code", "markdown_url": "https://composio.dev/toolkits/segment/framework/claude-code.md", "updated_at": "2026-05-12T10:25:03.502Z" } ``` ## Introduction Manage your Segment directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: - Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach - Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control ## Also integrate Segment with - [OpenAI Agents SDK](https://composio.dev/toolkits/segment/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/segment/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/segment/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/segment/framework/codex) - [OpenClaw](https://composio.dev/toolkits/segment/framework/openclaw) - [Hermes](https://composio.dev/toolkits/segment/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/segment/framework/cli) - [Google ADK](https://composio.dev/toolkits/segment/framework/google-adk) - [LangChain](https://composio.dev/toolkits/segment/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/segment/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/segment/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/segment/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/segment/framework/crew-ai) ## TL;DR - Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles. - Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling. - Handling Large tool responses out of LLM context to minimize context rot. - Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need. ## Connect Segment to Claude Code ### Connecting Segment to Claude Code using Composio 1. Add the Composio MCP to Claude ```bash claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp ``` ## What is Claude Code? Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working. Key features include: - Terminal-Native Experience: Work with Claude directly in your command line without switching contexts - MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities - Project Context: Claude understands your project structure and can read, write, and modify files - Interactive Development: Ask questions, debug code, and get help in real-time while coding - Multi-Platform: Works on macOS, Linux, WSL, and Windows ## 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. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `SEGMENT_ADD_LABELS_TO_SOURCE` | Add Labels to Source | Tool to add existing labels to a Source. Use when you have the source ID and want to tag it with metadata labels. | | `SEGMENT_ALIAS` | Segment Alias | Tool to alias a previous user ID to a new user ID. Use when merging anonymous and known identities. | | `SEGMENT_BATCH` | Batch Segment Analytics Events | Tool to send multiple analytics calls in a single batch request. Use when you want to reduce HTTP overhead by batching Identify/Track/Page/Screen/Group calls into one request. | | `SEGMENT_DELETE_SOURCE` | Delete Source | Tool to delete a Segment Source. Use when you need to permanently remove a Source by its ID after confirmation. | | `SEGMENT_GET_DAILY_PER_SOURCE_API_CALLS_USAGE` | Get Daily Per Source API Calls Usage | Tool to fetch daily API call counts per source for a given period. Use when you need daily breakdown of API usage by source after determining the reporting period. | | `SEGMENT_GET_DESTINATION` | Get Destination | Tool to retrieve a Destination by ID. Use when you need to fetch the full configuration of a Segment Destination instance by its unique identifier. Falls back US→EU public API and legacy app endpoint; returns minimal envelope on legacy HTML or parse errors. | | `SEGMENT_GROUP` | Segment Group | Tool to associate an identified user with a group via Segment HTTP Tracking API. Use when grouping users with traits. | | `SEGMENT_IDENTIFY` | Segment Identify | Tool to identify a user and set/update traits via Segment HTTP Tracking API. | | `SEGMENT_IMPORT_HISTORICAL_DATA` | Import Historical Data | Tool to import historical data in bulk with support for historical timestamps. Use when you need to backfill or import past events with their original timestamps into Segment. | | `SEGMENT_LIST_CONNECTED_WAREHOUSES_FROM_SOURCE` | List Connected Warehouses From Source | Tool to list warehouses connected to a Source. Use when you need to retrieve warehouses for a given source ID. | | `SEGMENT_LIST_DELIVERY_METRICS_SUMMARY_FROM_DESTINATION` | List Delivery Metrics Summary from Destination | Get an event delivery metrics summary from a Destination. Primary attempt uses Segment Public API; fallback to legacy app host if needed. On HTML fallback responses, returns a minimal valid envelope to maintain contract. | | `SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCE` | List Schema Settings in Source | Retrieve schema configuration settings for a Source. | | `SEGMENT_PAGE` | Segment Page View | Tool to record a page view via Segment HTTP Tracking API. Use when sending page views with optional page name and properties. | | `SEGMENT_REMOVE_SOURCE_WRITE_KEY` | Remove Source Write Key | Tool to remove a write key from a Source. Use when you need to revoke an existing write key for security or rotation. | | `SEGMENT_SCREEN` | Segment Screen Event | Tool to record a mobile app screen view. Use when tracking screen views in a mobile app via Segment HTTP Tracking API. | | `SEGMENT_TRACK` | Segment Track Event | Tool to record a custom user event via Segment HTTP Tracking API. Use when sending events to Segment with valid identity. | | `SEGMENT_UPDATE_SOURCE` | Update Source | Tool to update a Source's metadata and settings. Use when you need to modify an existing Source after confirming its ID. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Segment MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Segment account. It provides structured and secure access so Claude can perform Segment operations on your behalf. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Claude Pro, Max, or API billing enabled Anthropic account - Composio API Key - A Segment account - Basic knowledge of Python or TypeScript ### 1. Install Claude Code To install Claude Code, use one of the following methods based on your operating system: ```bash # macOS, Linux, WSL curl -fsSL https://claude.ai/install.sh | bash # Windows PowerShell irm https://claude.ai/install.ps1 | iex # Windows CMD curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd ``` ### 2. Set up Claude Code Open a terminal, go to your project folder, and start Claude Code: - Claude Code will open in your terminal - Follow the prompts to sign in with your Anthropic account - Complete the authentication flow - Once authenticated, you can start using Claude Code ```bash cd your-project-folder claude ``` ### 3. Set up environment variables Create a .env file in your project root with the following variables: - COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code)) - USER_ID identifies the user for session management (use any unique identifier) ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here ``` ### 4. Install Composio library No description provided. ```python pip install composio-core python-dotenv ``` ```typescript npm install @composio/core dotenv ``` ### 5. Generate Composio MCP URL No description provided. ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["segment"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http segment-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; 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 composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['segment'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http segment-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ### 6. Run the script and copy the MCP URL No description provided. ```python python generate_mcp_url.py ``` ```typescript node --loader ts-node/esm generate_mcp_url.ts # or if using tsx tsx generate_mcp_url.ts ``` ### 7. Add Segment MCP to Claude Code In your terminal, add the MCP server using the command from the previous step. The command format is: - claude mcp add registers a new MCP server with Claude Code - --transport http specifies that this is an HTTP-based MCP server - The server name (segment-composio) is how you'll reference it - The URL points to your Composio Tool Router session - --headers includes your Composio API key for authentication After running the command, close the current Claude Code session and start a new one for the changes to take effect. ```bash claude mcp add --transport http segment-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY" # Then restart Claude Code exit claude ``` ### 8. Verify the installation Check that your Segment MCP server is properly configured. - This command lists all MCP servers registered with Claude Code - You should see your segment-composio entry in the list - This confirms that Claude Code can now access Segment tools If everything is wired up, you should see your segment-composio entry listed: ```bash claude mcp list ``` ### 9. Authenticate Segment The first time you try to use Segment tools, you'll be prompted to authenticate. - Claude Code will detect that you need to authenticate with Segment - It will show you an authentication link - Open the link in your browser (or copy/paste it) - Complete the Segment authorization flow - Return to the terminal and start using Segment through Claude Code Once authenticated, you can ask Claude Code to perform Segment operations in natural language. For example: - "Fetch daily API usage for each source" - "Add metadata labels to a specific source" - "Identify a user and update their traits" ## Complete Code ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["segment"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http segment-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; 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 composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['segment'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http segment-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ## Conclusion You've successfully integrated Segment with Claude Code using Composio's MCP server. Now you can interact with Segment directly from your terminal using natural language commands. Key features of this setup: - Terminal-native experience without switching contexts - Natural language commands for Segment operations - Secure authentication through Composio's managed MCP - Tool Router for dynamic tool discovery and execution Next steps: - Try asking Claude Code to perform various Segment operations - Add more toolkits to your Tool Router session for multi-app workflows - Integrate this setup into your development workflow for increased productivity You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities. ## How to build Segment MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/segment/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/segment/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/segment/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/segment/framework/codex) - [OpenClaw](https://composio.dev/toolkits/segment/framework/openclaw) - [Hermes](https://composio.dev/toolkits/segment/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/segment/framework/cli) - [Google ADK](https://composio.dev/toolkits/segment/framework/google-adk) - [LangChain](https://composio.dev/toolkits/segment/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/segment/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/segment/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/segment/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/segment/framework/crew-ai) ## Related Toolkits - [Firecrawl](https://composio.dev/toolkits/firecrawl) - Firecrawl automates large-scale web crawling and data extraction. It helps organizations efficiently gather, index, and analyze content from online sources. - [Tavily](https://composio.dev/toolkits/tavily) - Tavily offers powerful search and data retrieval from documents, databases, and the web. It helps teams locate and filter information instantly, saving hours on research. - [Exa](https://composio.dev/toolkits/exa) - Exa is a data extraction and search platform for gathering and analyzing information from websites, APIs, or databases. It helps teams quickly surface insights and automate data-driven workflows. - [Serpapi](https://composio.dev/toolkits/serpapi) - SerpApi is a real-time API for structured search engine results. It lets you automate SERP data collection, parsing, and analysis for SEO and research. - [Peopledatalabs](https://composio.dev/toolkits/peopledatalabs) - Peopledatalabs delivers B2B data enrichment and identity resolution APIs. Supercharge your apps with accurate, up-to-date business and contact data. - [Snowflake](https://composio.dev/toolkits/snowflake) - Snowflake is a cloud data warehouse built for elastic scaling, secure data sharing, and fast SQL analytics across major clouds. - [Posthog](https://composio.dev/toolkits/posthog) - PostHog is an open-source analytics platform for tracking user interactions and product metrics. It helps teams refine features, analyze funnels, and reduce churn with actionable insights. - [Amplitude](https://composio.dev/toolkits/amplitude) - Amplitude is a digital analytics platform for product and behavioral data insights. It helps teams analyze user journeys and make data-driven decisions quickly. - [Bright Data MCP](https://composio.dev/toolkits/brightdata_mcp) - Bright Data MCP is an AI-powered web scraping and data collection platform. Instantly access public web data in real time with advanced scraping tools. - [Browseai](https://composio.dev/toolkits/browseai) - Browseai is a web automation and data extraction platform that turns any website into an API. It's perfect for monitoring websites and retrieving structured data without manual scraping. - [ClickHouse](https://composio.dev/toolkits/clickhouse) - ClickHouse is an open-source, column-oriented database for real-time analytics and big data processing using SQL. Its lightning-fast query performance makes it ideal for handling large datasets and delivering instant insights. - [Coinmarketcal](https://composio.dev/toolkits/coinmarketcal) - CoinMarketCal is a community-powered crypto calendar for upcoming events, announcements, and releases. It helps traders track market-moving developments and stay ahead in the crypto space. - [Control d](https://composio.dev/toolkits/control_d) - Control d is a customizable DNS filtering and traffic redirection platform. It helps you manage internet access, enforce policies, and monitor usage across devices and networks. - [Databox](https://composio.dev/toolkits/databox) - Databox is a business analytics platform that connects your data from any tool and device. It helps you track KPIs, build dashboards, and discover actionable insights. - [Databricks](https://composio.dev/toolkits/databricks) - Databricks is a unified analytics platform for big data and AI on the lakehouse architecture. It empowers data teams to collaborate, analyze, and build scalable solutions efficiently. - [Datagma](https://composio.dev/toolkits/datagma) - Datagma delivers data intelligence and analytics for business growth and market discovery. Get actionable market insights and track competitors to inform your strategy. - [Delighted](https://composio.dev/toolkits/delighted) - Delighted is a customer feedback platform based on the Net Promoter System®. It helps you quickly gather, track, and act on customer sentiment. - [Dovetail](https://composio.dev/toolkits/dovetail) - Dovetail is a research analysis platform for transcript review and insight generation. It helps teams code interviews, analyze feedback, and create actionable research summaries. - [Dub](https://composio.dev/toolkits/dub) - Dub is a short link management platform with analytics and API access. Use it to easily create, manage, and track branded short links for your business. - [Elasticsearch](https://composio.dev/toolkits/elasticsearch) - Elasticsearch is a distributed, RESTful search and analytics engine for all types of data. It delivers fast, scalable search and powerful analytics across massive datasets. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Segment MCP? With a standalone Segment MCP server, the agents and LLMs can only access a fixed set of Segment tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Segment and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Claude Code? Yes, you can. Claude Code 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 Segment tools. ### Can I manage the permissions and scopes for Segment while using Tool Router? Yes, absolutely. You can configure which Segment 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. ### How safe is my data with Composio Tool Router? 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 Segment data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)