How to connect Segment to Claude Cowork

Trusted by teams atAWSGleanZoomAirtable

30 min · no commitment · see it on your stack

Segment logo
Claude Cowork logo
divider

Introduction

Cowork is Anthropic's AI agent for knowledge work. Think of it as Claude Code for everything else. It works autonomously with your computer, local files, and applications to accomplish complex tasks.

This guide walks you through the easiest and most secure way to connect your Segment account to Cowork via Composio Connect, enabling it to fetch daily API usage for each source, add metadata labels to a specific source, identify a user and update their traits, and more such actions on your behalf without compromising your account security.

Also integrate Segment with

Connecting Segment to Claude Cowork

1. Open Customize

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

2. Add the Composio MCP server

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

3. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Cowork

4. Connect your Segment account

Back in Cowork, ask the agent to connect to Segment or give it any Segment-related task.

For example, ask Cowork to:

  • "Fetch daily API usage for each source"
  • "Add metadata labels to a specific source"
  • "Identify a user and update their traits"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Cowork, and your Segment account is ready to use.

What is Claude Cowork?

Claude Cowork is Anthropic's agent for general knowledge work. It can use your computer, files, and connected applications to complete longer-running tasks across your work tools.

With Composio Connect, Cowork can securely access apps like Segment through MCP without you sharing account credentials directly with the agent.

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

How to build Segment MCP Agent with another framework

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 Claude Cowork?

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