Get started

Segment for AI agents

Twilio Segment is a customer data platform that collects, cleans, and routes customer event data from sources to destinations like warehouses and analytics tools. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect SegmentSee the 17 actions ↓
AnalyticsAPI keyMCP + RESTsegment.com
AUDIT LOG · SEGMENTPOLICY: acme-support
09:41:07 · claude · u_8f2read
segment.list_schema_settings_in_source
List Schema Settings in Source✓ allowed · 212ms
09:41:08 · claude · u_8f2read
segment.track
Segment Track Event✓ allowed · 164ms
09:41:09 · claude · u_8f2write
segment.update_source
Update Source✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
segment.delete_source
Delete Source✕ blocked · policy: deny
EVERY SEGMENT CALL, ON THE RECORD
01 · USE CASES

What agents do in Segment.

01

Send an identify or track event

Records a customer identify or track event into Segment so downstream tools stay in sync.

02

Check delivery metrics for a destination

Reads recent delivery metrics for a destination to confirm events are reaching it.

03

Delete a source only after confirmation

Removes a data source from the workspace only once someone confirms it is no longer in use.

02 · ACTIONS

17 Segment actions, graded by risk.

Every Segment action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

7

Look things up. Allowed by default.

  • segment.get_destination
    Get Destination
  • segment.list_schema_settings_in_source
    List Schema Settings in Source
  • segment.get_daily_per_source_api_calls_usage
    Get Daily Per Source API Calls Usage
  • segment.list_connected_warehouses_from_source
    List Connected Warehouses From Source
  • segment.list_delivery_metrics_summary_from_destination
    List Delivery Metrics Summary from Destination
  • segment.track
    Segment Track Event
  • segment.identify
    Segment Identify

write

8

Create and change things. Allow, or ask the user first.

  • segment.update_source
    Update Source
  • segment.add_labels_to_source
    Add Labels to Source
  • segment.page
    Segment Page View
  • segment.alias
    Segment Alias
  • segment.batch
    Batch Segment Analytics Events
  • segment.group
    Segment Group
  • segment.screen
    Segment Screen Event
  • segment.import_historical_data
    Import Historical Data

destructive

2

Delete, cancel or archive. Ask first, or deny outright.

  • segment.delete_source
    Delete Source
  • segment.remove_source_write_key
    Remove Source Write Key
03 · HOW IT WORKS

Segment in three steps.

  1. 01Your users connect SegmentThey add their Segment api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “update Source” can wait for the user, and “delete Source” can be denied outright.
  3. 03Any agent can actYour agent calls Segment through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('segment', {
  read: 'allow',
  write: 'ask',        // update_source
  destructive: 'deny',  // delete_source
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Segment connects.

Users add their Segment api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Segment connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Segment from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More analytics apps.

Gong58 actionsSerpApi59 actionsPeople Data Labs27 actionsPostHog507 actions21risk8 actionsAkta19 actionsAlpha Vantage56 actionsAmplitude54 actions
ALL ANALYTICS APPS →
07 · FAQ

Segment and Arc0, answered.

Q01

Can I use Segment with Claude, ChatGPT or Cursor?

Yes. Connect Segment to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Segment actions you allow.

Q02

How do users connect Segment?

Users add their Segment api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Segment actions can my agent take?

17 in total: 7 read, 8 write and 2 destructive, such as “update Source”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Segment?

Yes. Actions like “delete Source” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Segment too?

Yes. The same Segment connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Segment into your agent.

Your users connect Segment once, under your brand. Your agent gets 17 actions behind your policies, with every call on the record.

Connect SegmentBrowse all apps →

Free to build · MCP + REST · Audit log on every plan