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

Source: https://elaichi.ai/connectors/segment/

## Facts

| | |
| --- | --- |
| Application | Segment |
| Category | Marketing Automation |
| AI tools | 201 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Segment is connected

- 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

## Connect Segment in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Segment.
2. Optionally set Share with, then press Connect.
3. Paste a Segment API key. One person generates a token in Segment and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Segment tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Segment MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
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

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

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

## Segment MCP connector for Microsoft Copilot

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

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

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

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

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

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Segment tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Segment through Elaichi

### Send an audience to a new destination

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

### Put audience syncs on a schedule

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

### Kick off a batch of activations

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

### See who has access to Segment

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

### Remove leavers from the workspace

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

### Keep groups and permissions tidy

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

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

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

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

## All 201 Segment tools

Every tool below is callable through https://api.elaichi.ai/mcp once Segment is connected, subject to the toolbox it is in and the restrictions on the caller.

- **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.
- **Segment users bulk delete group** (Delete). Remove users from a Segment user group by email address. Returns: status. Required: user_group_id, emails.
- **Segment users bulk update** (Update). Replace the members of a Segment user group with a new list of email addresses. Returns the updated group with id, name, memberCount, and permissions. Required: user_group_id, emails.
- **List all Segment roles** (List). List Segment roles available to apply to permissions for users and groups. Returns: id, name, description.
- **Update a Segment role by ID** (Update). Replace the permission roles assigned to a Segment user. Returns the updated permissions under data, each including roleId, roleName, and resources. Required: userId, permissions.
- **List all Segment groups** (List). List Segment user groups. Returns: memberCount, permissions, id, name.
- **Get single Segment group by ID** (Get). Get a Segment user group by id. Returns: memberCount, permissions, id, name. Required: id.
- **Segment groups attach permission** (Action). Add access permissions to a Segment user group. Returns the granted permissions with roleId, roleName, and resources. Required: user_group_id, userGroupId, permissions.
- **Segment groups bulk update** (Update). Replace all access permissions for a Segment user group. Returns the new permissions with roleId, roleName, and resources. Required: user_group_id, userGroupId, permissions.
- **Create a Segment group** (Create). Create a user group in Segment. Returns the created group with id, name, and memberCount. Required: name.
- **Delete a Segment group by ID** (Delete). Delete a user group from a Segment workspace by id. Returns: status. Required: id.
- **Update a Segment group by ID** (Update). Update a user group's name in Segment by id. Returns the updated group with id, name, and memberCount. Required: id, name.
- **List all Segment workspace** (List). Get the Workspace in Segment associated with your API token. Returns: id, slug, name.
- **Create a Segment activations batch** (Create). Batch query Segment activations for a space, listing activations across many audiences in one bulk call instead of one request per audience. Returns: id, enabled, workspaceId, spaceId, audienceId, connectionId, and 3 more fields. Required: space_id, spaceId. Requires space_id and audienceIds. The workspace must have the Audience feature enabled.
- **Create a Segment audience destination connection** (Create). Add a Destination to an Audience in Segment, creating a destination connection. Returns: id. The Destination must already be added to Engage via the Engage Settings page, and an Activation must be created to start syncing data. Required: space_id, audience_id, spaceId, audienceId, destination.
- **Delete a Segment audience destination connection by ID** (Delete). Remove a Destination from an Audience in Segment by connection id. Returns: status. The request fails with a 409 Conflict if activations exist for the Destination. Required: id, space_id, audience_id, spaceId, audienceId, destinationId.
- **List all Segment audience destination connections** (List). List all Destinations connected to an Audience in Segment. Returns: id, name, sourceId, enabled, createdAt, updatedAt, settings, destinationId, metadata, idSyncConfiguration, connectionSettings. Required: space_id, audience_id, space_id, audience_id.
- **Update a Segment audience destination connection by ID** (Update). Update the Destination connection for an Audience in Segment. Returns the connection with its destination id and idSyncConfiguration (externalId, strategy). The workspace must have the Audience feature enabled. Required: id, space_id, audience_id, spaceId, audienceId, destinationId.
- **Create a Segment audience schedule** (Create). Create a run schedule for a Linked Audience in Segment. Returns: id, strategy, config, nextExecution. Requires space_id, audience_id, strategy, and config. Schedules are only supported for Linked Audiences (audienceType = LINKED). Required: space_id, audience_id, spaceId, strategy, config.
- **Delete a Segment audience schedule by ID** (Delete). Delete an audience schedule from a Linked Audience in Segment. Returns: status. Requires space_id, audience_id, and id. Required: id, space_id, audience_id, spaceId, scheduleId.
- **Get single Segment audience schedule by ID** (Get). Get a single audience schedule for an audience in Segment by id. Returns: id, strategy, config, nextExecution. Requires space_id, audience_id, and id. Required: id, space_id, audience_id, spaceId, scheduleId.
- **List all Segment audience schedules** (List). List all schedules configured for an audience in Segment. Returns: id, strategy, config, nextExecution. Requires space_id and audience_id. Required: space_id, audience_id, spaceId.
- **Update a Segment audience schedule by ID** (Update). Update the run schedule for a Linked Audience in Segment. Returns: id, strategy, config, nextExecution. Requires space_id, audience_id, id, strategy, and config. Required: id, space_id, audience_id, spaceId, scheduleId, strategy, config.
- **Create a Segment audiences preview** (Create). Create an Audience Preview in a Segment space to evaluate an audience definition. Returns: id. The space's workspace must have the Audience feature enabled. Required: space_id, spaceId, definition, audienceType.
- **Get single Segment audiences preview by ID** (Get). Get an Audience Preview by id in a Segment space to read its computed results. Returns: id, audienceType, definition, options, status, results, size, failureReason. Required: id, space_id, spaceId.
- **Create a Segment destination connection activation** (Create). Create an Activation to sync a Segment audience to a destination connection. Returns: id, activationType, personalization, destinationMapping, and 8 more. The workspace must have the Audience feature enabled. Required: space_id, audience_id, connection_id, space_id, audience_id, connection_id, activationType, activationName, performResync.
- **Create a Segment group user** (Create). Add users or invites to a Segment user group by email. Returns the updated group including id, name, and memberCount. Required: user_group_id, userGroupId, emails.
- **List all Segment group users** (List). List the users belonging to a Segment user group. Returns: id, name, email. Required: user_group_id, userGroupId.
- **Create a Segment regulations cloudsource** (Create). Create a Cloud Source Regulation in Segment to suppress or delete end-user data scoped to a cloud source. Returns: regulateId. Regulations are processed asynchronously. Required: cloudsource_id, sourceId, regulationType, subjectType, subjectIds, collection.
- **Segment reverse etl model syncs cancel** (Cancel). Cancel a running Reverse ETL sync for a model in Segment. Returns: modelId, syncId, errorCode, errorMessage, status. Cancellation may take a few seconds to complete and the call errors if the sync already completed or was cancelled. Required: model_id, sync_id, modelId, syncId.
- **Get single Segment reverse etl model sync by ID** (Get). Get the detailed sync status for a Reverse ETL sync in Segment, including extract and load phase results. Returns: syncId, modelId, sourceId, syncStatus, duration, startedAt, finishedAt, extractPhase, loadPhase, error, errorCode. Required: id, model_id, modelId, syncId.
- **Segment sources attach label** (Action). Add existing labels to a Segment Source. Returns the source's labels with their key, value, and description. Requires source_id and labels (an array of key/value pairs). Required: source_id, sourceId, labels.
- **Segment sources bulk update** (Update). Replace all labels in a Segment Source with the provided set. Returns the source's labels with their key, value, and description. Requires source_id and labels (an array of key/value pairs). Required: source_id, sourceId, labels.
- **Create a Segment source** (Create). Create a new Source in Segment for a website or app you want to track. Returns the created source including its id, slug, name, writeKeys, enabled, metadata, settings, and labels. Required: slug, enabled, metadataId.
- **Delete a Segment source by ID** (Delete). Delete a Segment Source by id. Returns: status. Required: id.
- **Get single Segment source by ID** (Get). Get a Segment Source by id. Returns the source including its id, slug, name, workspaceId, enabled, writeKeys, metadata, settings, and labels. Required: id.
- **List all Segment sources** (List). List the Segment sources configured in your workspace. Returns for each source: id, slug, name, enabled, writeKeys, and metadata.
- **Update a Segment source by ID** (Update). Update an existing Segment source by id — rename it, change its slug or settings, or enable or disable it. Returns: id, slug, name, metadata, workspaceId, enabled, writeKeys, settings, labels. Required: id.
- **Create a Segment space audience** (Create). Create an audience in a Segment space. Returns the created audience including id, name, key, enabled, definition, status, and audienceType. The workspace must have the Audience feature enabled. Required: space_id, spaceId, name, definition, audienceType.
- **Delete a Segment space audience by ID** (Delete). Delete an audience from a Segment space by id. Returns: status. The workspace must have the Audience feature enabled. Required: id, space_id, spaceId.
- **Get single Segment space audience by ID** (Get). Get an audience in a Segment space by id. Returns the audience including id, name, key, enabled, definition, status, size, and computeCadence. The workspace must have the Audience feature enabled. Required: id, space_id, spaceId.
- **List all Segment space audiences** (List). List audiences in a Segment space. Returns audiences with id, name, key, enabled, definition, status, size, and computeCadence. The workspace must have the Audience feature enabled. Required: space_id, spaceId.
- **Update a Segment space audience by ID** (Update). Update an audience in a Segment space by id. Returns the updated audience including id, name, key, enabled, definition, status, and options. The audience is locked from further edits until the changes are incorporated, and the workspace must have the Audience feature enabled. Required: id, space_id, spaceId.
- **Create a Segment space computed trait** (Create). Create a Computed Trait in a Segment space. Returns the created trait with id, name, key, definition, status, enabled, and createdAt. Requires space_id, name, and definition. Alpha API; API-created definitions are not editable in the Segment app. Required: space_id, spaceId, name, definition.
- **Delete a Segment space computed trait by ID** (Delete). Delete a Computed Trait from a Segment space by id. Returns: status. Requires space_id and id. Alpha API. Required: id, space_id, spaceId.
- **Get single Segment space computed trait by ID** (Get). Get a Computed Trait by id in a Segment space. Returns: id, spaceId, name, description, key, enabled, definition, status, createdBy, updatedBy, createdAt, updatedAt, options. Requires space_id and id. Alpha API. Required: id, space_id, spaceId.
- ...and 151 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
