Skip to content

Segment MCP connector

Connect Segment to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can list workspace users, roles and groups, manage audience destination connections and schedules, every call signed in as you and logged.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

List everyone with admin access in our Segment workspace

Working in Segment with Elaichi

  • List all Segment users
  • Get single Segment user by ID
  • List all Segment roles
Ask anything…
Governance / Audit log Last 24 hours
Segment List all Segment roles Emily Carter · Claude · 9:41 AM Done
Segment Get single Segment user by ID Emily Carter · Claude · 9:41 AM Done
Segment List all Segment users Emily Carter · Claude · 9:41 AM Done
Segment Segment users attach permission Megan Brooks · ChatGPT · 9:38 AM Done
Segment Segment users bulk update Ryan Hayes · Cursor · 9:35 AM Done

How to connect Segment to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Segment MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Segment MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Segment MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Segment MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Segment MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Segment to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with Segment through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Segment is logged.

  • Marketing

    Send an audience to a new destination

    Ask for the retention audience to be connected to the ad platform you just set up, and check which destinations it already feeds before you do.

  • Marketing Ops

    Put audience syncs on a schedule

    Set a daily schedule for a campaign audience, then remove it once the campaign ends so nothing keeps syncing by accident.

  • Growth

    Kick off a batch of activations

    Create a batch of activations for a launch in one ask instead of clicking through each audience by hand.

  • IT

    See who has access to Segment

    Pull the full list of workspace users with their roles and groups, so a quarterly access review takes minutes rather than an afternoon.

  • Security

    Remove leavers from the workspace

    Delete a departed employee's Segment user, or clear out a whole batch at once after a reorganization, and the audit log shows who did it.

  • Data

    Keep groups and permissions tidy

    Create a group for a new analytics squad, attach the right permissions, and update membership as people move between teams.

Try asking

  • “List everyone with admin access in our Segment workspace”
  • “Which destinations does the retention audience sync to right now”
  • “Who sits in the Marketing group and what roles do they hold”

See all 201 Segment tools →

What connecting Segment gets you

6 screens from Elaichi, each doing one job for your Segment account.

Elaichi Agent

Ask Elaichi to work across your apps.

List everyone with admin access in our Segment workspace

Which destinations does the retention audience sync to right now

Who sits in the Marketing group and what roles do they hold

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask Segment who has access, in plain words.

Type a question and get answers from live Segment users, groups and audiences.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One Segment endpoint for every AI client.

Claude, ChatGPT and Cursor reach Segment through one governed endpoint, no SDK, no shared key.

ElaichiTools
Tool Action Description
List all Segment users List List Segment users with access to the Workspace. Returns: id, name, email, permissions.
Get single Segment user by ID Get Get a single Segment Workspace user by id. Returns: id, name, email, permissions. Required: id.
Delete a Segment user by ID Delete Delete a user from a Segment workspace by id. Returns: status. Required: id.
Segment users attach permission Action Add a list of access permissions to a Segment user. Returns: roleId, roleName, resources. Required: user_id, userId, permissions.
Segment users bulk delete Delete Delete one or more Segment users in bulk by their ids. Returns: status. Required: userIds.

Tool catalog

201 Segment tools, no custom code.

Users, roles, groups, audiences and destination connections, cataloged and ready without an engineer.

ElaichiToolboxes
Name Source template Tools Created

Marketing toolbox

Segment · audiences and destinations

Segment starter 18 Mar 4, 2026

Marketing Ops toolbox

Segment · audience schedules and activations

— 9 Mar 2, 2026

Growth toolbox

Segment · activation batches

— 24 Feb 27, 2026

IT toolbox

Segment · users and roles

Segment starter 6 Feb 19, 2026

Security toolbox

Segment · permissions and access reviews

— 31 Jan 30, 2026

Data toolbox

Segment · workspaces and groups

— 12 Jan 22, 2026

Toolboxes

Each team gets its own Segment toolbox.

Marketing works audiences, IT works users and roles, each team sees only its toolbox.

ElaichiConnections
Connection Scope Status Access
SE

Segment (Marketing)

Connected by Emily Carter

Personal • Active 1 team · 6 members
SE

Segment (Growth)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
SE

Segment (Lifecycle)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
SE

Segment (Data platform)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
SE

Segment (IT admin)

Connected by Ryan Hayes

Personal • Active Not shared
SE

Segment (EMEA marketing)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share a Segment connection, not the API key.

One person connects Segment, teammates work through it and never see the key.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Segment Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Segment Users Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Segment Users List Toolbox

Audit log

Every Segment change names the person behind it.

When, who, what happened and which user or audience, kept in one append-only log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Segment digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch users

    Segment

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Segment

    Queued

Workflows

A schedule runs Segment work end to end.

Audience schedules are fetched, grouped and drafted into a digest a person approves before posting.

Segment health

Refreshed 4 minutes ago · every 15 minutes · from the users collection

Live

Users

1,284 ↓ 12%

Groups

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Users created

Last 14 days

By team

Share of activity

Marketing 34%

Growth 27%

Lifecycle 21%

Data platform 18%

Collections and dashboards

Segment health numbers, computed, never asked for.

Four metrics and a 14 day chart from Segment records, no model, refreshed on schedule.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Segment

All three can connect Segment to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Segment, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Segment tools Allow or restrict single Segment tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Segment call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Segment tools for your AI agents

201 tools are ready to call through Elaichi's MCP endpoint the moment you connect Segment, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

How do I connect Segment to Claude?

Two steps. In Elaichi, add the Segment connector and paste in a Segment API key, there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks and Segment is available in the chat.

Does Segment work with ChatGPT and Cursor as well as Claude?

Yes. Once Segment is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Segment once and every client picks it up.

What can an AI agent actually do with my Segment data?

With Segment connected, an agent can list the users in your workspace with their roles and groups, create or update groups and attach permissions, and remove users who have left. On the marketing side it can connect an audience to a destination, set or remove an audience schedule, and create a batch of activations. Short, concrete asks such as "list every admin in Segment" work better than long paragraphs.

Does connecting Segment give the AI access to my whole workspace?

No. Every call to Segment runs inside the access of the person who signed in to Elaichi, so an agent can only touch the workspaces, users and audiences that person could reach themselves. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Segment already allows.

Can my team share one Segment connection?

Yes. One person adds the Segment API key in Elaichi and shares the connection with a team, and nobody else ever sees or handles the key. Each teammate still signs in to Elaichi as themselves, so every Segment action in the audit log carries their own name.

Can I stop an agent from deleting or changing things in Segment?

Yes. Restrictions in Elaichi apply per action, for example deleting a Segment user or removing an audience schedule, and are set on a role or on one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

What happens to a Segment connection when someone leaves?

Offboarding a person in Elaichi ends their access to Segment at once, in every client they used. If they were working through a shared Segment connection, that connection keeps working for everyone else on the team. Disconnecting Segment once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

Does the Segment MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Segment is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Segment?

Yes. Both let Claude, ChatGPT or Cursor use Segment. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Segment call.

How is Elaichi different from Composio for Segment?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Segment: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Segment in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot