Is this an official Segment MCP server?

No. It is Memtro's MCP server with Memtro's Segment connector behind it: the connector reads Segment through its API with the credentials you connect on Dashboard → Connections, and Segment publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Segment?

Not yet. Today every Segment tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Analytics

Segment MCP server

Segment in any MCP client, through Memtro: Segment does not publish this server. Memtro's Segment connector reads Segment through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only view of a Twilio Segment workspace: sources, destinations, warehouses and tracking plans, plus (with Unify) a customer profile's traits, identifiers and recent events.

Reads

segment_workspaceThe Segment workspace and its sources (where events come from): id, slug, name, source type, enabled, labels.
segment_destinationsDestinations (where Segment forwards data): for one source (source_id from segment_workspace) or across the workspace.
segment_warehousesData warehouses Segment syncs into (Snowflake, BigQuery, Redshift, Postgres…): id, name, type, enabled.
segment_profileLook up one customer profile in Segment Unify by user_id, email or anonymous_id: its traits (name, plan, company……
segment_profile_eventsRecent events (track/page/screen/identify) for one Unify profile, newest first…
segment_tracking_plansTracking plans (Protocols): the catalogue of expected events.

Connect it

First connect Segment on Dashboard → Connections, then add Memtro to your client once. The Segment tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Segment connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› What did jane@acme.com do in the product this week?
› Which destinations receive data from the iOS source?
› Do we have a tracking plan rule for Order Completed and which properties are required?
› Is the Snowflake warehouse sync enabled?

Questions

Is this an official Segment MCP server?: No. It is Memtro's MCP server with Memtro's Segment connector behind it: the connector reads Segment through its API with the credentials you connect on Dashboard → Connections, and Segment publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Segment?: Not yet. Today every Segment tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.