How to integrate Segment MCP with LangChain

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Segment logo
LangChain logo
divider

Introduction

This guide walks you through connecting Segment to LangChain using the Composio tool router. By the end, you'll have a working Segment agent that can fetch daily api usage for each source, add metadata labels to a specific source, identify a user and update their traits through natural language commands.

This guide will help you understand how to give your LangChain 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

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Segment project to Composio
  • Create a Tool Router MCP session for Segment
  • Initialize an MCP client and retrieve Segment tools
  • Build a LangChain agent that can interact with Segment
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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 & Triggers

Tools
Add Labels to SourceTool to add existing labels to a Source.
Segment AliasTool to alias a previous user ID to a new user ID.
Batch Segment Analytics EventsTool to send multiple analytics calls in a single batch request.
Delete SourceTool to delete a Segment Source.
Get Daily Per Source API Calls UsageTool to fetch daily API call counts per source for a given period.
Get DestinationTool to retrieve a Destination by ID.
Segment GroupTool to associate an identified user with a group via Segment HTTP Tracking API.
Segment IdentifyTool to identify a user and set/update traits via Segment HTTP Tracking API.
Import Historical DataTool to import historical data in bulk with support for historical timestamps.
List Connected Warehouses From SourceTool to list warehouses connected to a Source.
List Delivery Metrics Summary from DestinationGet an event delivery metrics summary from a Destination.
List Schema Settings in SourceRetrieve schema configuration settings for a Source.
Segment Page ViewTool to record a page view via Segment HTTP Tracking API.
Remove Source Write KeyTool to remove a write key from a Source.
Segment Screen EventTool to record a mobile app screen view.
Segment Track EventTool to record a custom user event via Segment HTTP Tracking API.
Update SourceTool to update a Source's metadata and settings.

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

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • 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

pip install composio-langchain langchain-mcp-adapters langchain python-dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • composio-langchain provides Composio integration for LangChain
  • langchain-mcp-adapters enables MCP client connections
  • langchain is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models

Import dependencies

from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Segment functionality through MCP

Initialize Composio client

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))

    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Segment tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

# Create Tool Router session for Segment
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['segment']
)

url = session.mcp.url
What's happening:
  • We're creating a Tool Router session that gives your agent access to Segment tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Segment tools as needed

Configure the agent with the MCP URL

client = MultiServerMCPClient({
    "segment-agent": {
        "transport": "streamable_http",
        "url": session.mcp.url,
        "headers": {
            "x-api-key": os.getenv("COMPOSIO_API_KEY")
        }
    }
})

tools = await client.get_tools()

agent = create_agent("gpt-5", tools)
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Segment MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • get_tools() retrieves all available Segment tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model

Set up interactive chat interface

conversation_history = []

print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Segment related question or task to the agent.\n")

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ['exit', 'quit', 'bye']:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_history.append({"role": "user", "content": user_input})
    print("\nAgent is thinking...\n")

    response = await agent.ainvoke({"messages": conversation_history})
    conversation_history = response['messages']
    final_response = response['messages'][-1].content
    print(f"Agent: {final_response}\n")
What's happening:
  • We initialize an empty conversation_history list to maintain context across interactions
  • A while loop continuously accepts user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the ainvoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully

Run the application

if __name__ == "__main__":
    asyncio.run(main())
What's happening:
  • We call the main() function using asyncio.run() to start the application

Complete Code

Here's the complete code to get you started with Segment and LangChain:

from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    
    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
    
    session = composio.create(
        user_id=os.getenv("COMPOSIO_USER_ID"),
        toolkits=['segment']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "segment-agent": {
            "transport": "streamable_http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    })
    
    tools = await client.get_tools()
  
    agent = create_agent("gpt-5", tools)
    
    conversation_history = []
    
    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Ask any Segment related question or task to the agent.\n")
    
    while True:
        user_input = input("You: ").strip()
        
        if user_input.lower() in ['exit', 'quit', 'bye']:
            print("\nGoodbye!")
            break
        
        if not user_input:
            continue
        
        conversation_history.append({"role": "user", "content": user_input})
        print("\nAgent is thinking...\n")
        
        response = await agent.ainvoke({"messages": conversation_history})
        conversation_history = response['messages']
        final_response = response['messages'][-1].content
        print(f"Agent: {final_response}\n")

if __name__ == "__main__":
    asyncio.run(main())

Conclusion

You've successfully built a LangChain agent that can interact with Segment through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

How to build Segment MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Segment MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Segment MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Segment MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Segment MCP with Claude Cowork

Codex logo

Codex

Use Segment MCP with Codex

OpenClaw logo

OpenClaw

Use Segment MCP with OpenClaw

Hermes logo

Hermes

Use Segment MCP with Hermes

CLI logo

CLI

Use Segment MCP with CLI

Google ADK logo

Google ADK

Use Segment MCP with Google ADK

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

FAQ

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 LangChain?

Yes, you can. LangChain 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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗