segment-mcp

Name: segment-mcp
Author: katekruger

by katekrugerversion 0.1.2i★ –iRuns on your computer

Registry nameio.github.katekruger/segment-mcp

Install

Overview

Description from the maker (original English)

Read-first MCP server for Twilio Segment: routing, stale sources, delivery health, governance.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Clinics & health
You need to fill in: SEGMENT_API_TOKEN, SEGMENT_REGION

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: SEGMENT_API_TOKEN, SEGMENT_REGION, SEGMENT_MCP_MODE, SEGMENT_PROFILE_TOKEN, SEGMENT_PROFILE_SPACE_ID

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "segment": {
      "command": "uvx",
      "args": [
        "segment-mcp"
      ],
      "env": {
        "SEGMENT_API_TOKEN": "your-value",
        "SEGMENT_REGION": "your-value",
        "SEGMENT_MCP_MODE": "your-value",
        "SEGMENT_PROFILE_TOKEN": "your-value",
        "SEGMENT_PROFILE_SPACE_ID": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add segment --env SEGMENT_API_TOKEN=your-value --env SEGMENT_REGION=your-value --env SEGMENT_MCP_MODE=your-value --env SEGMENT_PROFILE_TOKEN=your-value --env SEGMENT_PROFILE_SPACE_ID=your-value -- uvx segment-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "segment": {
      "command": "uvx",
      "args": [
        "segment-mcp"
      ],
      "env": {
        "SEGMENT_API_TOKEN": "your-value",
        "SEGMENT_REGION": "your-value",
        "SEGMENT_MCP_MODE": "your-value",
        "SEGMENT_PROFILE_TOKEN": "your-value",
        "SEGMENT_PROFILE_SPACE_ID": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "segment": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "segment-mcp"
      ],
      "env": {
        "SEGMENT_API_TOKEN": "your-value",
        "SEGMENT_REGION": "your-value",
        "SEGMENT_MCP_MODE": "your-value",
        "SEGMENT_PROFILE_TOKEN": "your-value",
        "SEGMENT_PROFILE_SPACE_ID": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

SEGMENT_API_TOKEN secret required env
Segment Public API token. Only a Workspace Owner can mint one — Segment App -> Workspace Settings -> Access Management -> Tokens -> Create Token -> Public API.
SEGMENT_REGION required env
Workspace region: 'us' or 'eu'. No default — must be set explicitly, or the server refuses to start.
SEGMENT_MCP_MODE env
read (default) | write | admin. Every tool in v0.1 is read-only regardless of this setting.
SEGMENT_PROFILE_TOKEN env
Separate credential for the Profile API (not yet wired to a tool in this version). Leave unset.
SEGMENT_PROFILE_SPACE_ID env
Unify Space ID for the Profile API (not yet wired to a tool in this version). Leave unset.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account katekruger, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Clinics & healthi

More stars than 0% of the other 870 servers in this category
Published to the registry more recently than 36% of the other 870 servers in this category
Basic checks equal to or better than 100% of the other 870 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is segment-mcp safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: SEGMENT_API_TOKEN, SEGMENT_REGION

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Mirobody, FHIR MCP Server, Google Health MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Mirobody

by thetahealth

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

Runs on your computer★ 1,408Apache-2.0Updated 6 days ago

Install

FHIR MCP Server

by wso2

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

Runs on your computer★ 137Apache-2.0Updated 9 days ago

Install

Google Health MCP

by davidmosiah

Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents

Runs on your computer★ 79MITUpdated 4 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

segment-mcp

A read-first MCP server for Twilio Segment. Answers which destinations get which events, which sources are dead, and which are governed by nothing — the questions nobody can answer without clicking through forty screens.

Read-only by default

SEGMENT_MCP_MODE defaults to read, and every tool this server ships today is a read. Shipping with zero write tools is a feature, not a limitation — see BUILD-PLAN.md §2. write and admin modes exist in the tier model (src/segment_mcp/modes.py) for when gated writes land; right now there is nothing for them to unlock.

What this refuses to do — permanently, not "for now"

POST /regulations and POST /regulations/sources/{id} — workspace-scoped, irreversible deletion or suppression of user data across every source — are unreachable in every mode, with no configuration path to enable them. Three independent things enforce this: the mode-authorization layer refuses it before even checking the current mode, the API client refuses to send the request before it reaches the network, and no tool this server registers references it in any form.

This isn't a gate waiting for the right permission level. It's a line, because these endpoints accept an array of subjects and one malformed or hallucinated call can permanently delete thousands of profiles with no undo. Full reasoning: [docs/what-this-refuses-to-do.md](docs/what-this-refuses-to-do.md).

Quick start

Requires a Segment workspace on Team or Business tier and a Public API token (see Prerequisites below).

gh repo clone katekruger/segment-mcp

cd segment-mcp uv sync cp .env.example .env # fill in SEGMENT_API_TOKEN and SEGMENT_REGION uv run segment-mcp

Point an MCP client (Claude Desktop, Claude Code, etc.) at it over stdio. The server refuses to start — loudly, with a clear message — if the token, region, or workspace tier isn't right; see Startup checks.

The five tools

Each composes several Public API calls into one structured answer, not a raw endpoint dump:

Tool	Question it answers
`audit_event_routing`	Which destinations get which events?
`trace_event`	Given an event name: where does it go, and is it governed by anything?
`find_stale_sources`	Which sources have no recent data — dead instrumentation vs. simply new?
`check_delivery_health`	Is this destination silently failing?
`find_ungoverned_sources`	Which sources are governed by nothing, or allowing unplanned events through?

Prerequisites

Team or Business tier. The Public API is not available on Free or Add-on plans. There is no workaround, and the server's startup checks fail with a clear message rather than a raw 403 if your workspace doesn't qualify.
A Public API token. Only a Workspace Owner can mint one: Segment App → Workspace Settings → Access Management → Tokens → Create Token → Public API (not Config API).

Region configuration

SEGMENT_REGION=us   # or eu

There is no default — you must set this explicitly. An EU workspace whose API calls are pointed at the US endpoint doesn't error; it just silently returns nothing, which is a far worse failure mode than a crash. This server's startup checks call the API once with your configured region and fail loudly if the token doesn't actually belong to it, naming the region that does.

Startup checks

All fatal — the server refuses to start rather than fail confusingly on the first tool call:

SEGMENT_REGION is set and one of us/eu.
SEGMENT_API_TOKEN is present and actually authenticates against that region.
The workspace's tier supports the Public API — a Free-tier workspace gets a clear "requires Team or Business tier" message, not a raw 403.

Modes

SEGMENT_MCP_MODE = read (default) | write | admin

`read` — every tool above. No mutation reachable, at any mode.
`write` — would add Tier 3 replace-semantics changes (none shipped yet), each echoed back for confirmation before executing.
`admin` — would add Tier 2 deletes (none shipped yet), gated behind a *typed* confirmation naming the exact resource — not just confirm=true.

See src/segment_mcp/modes.py for the full tier model and docs/what-this-refuses-to-do.md for what stays out of scope regardless of mode.

Profile API — a separate, higher trust tier

The Profile API returns PII on named individuals — traits, external IDs, event history, and identity links for a specific person. This is the most privacy-sensitive read anywhere in this server's surface, so it is walled off from everything else:

A separate credential, SEGMENT_PROFILE_TOKEN — never the main SEGMENT_API_TOKEN. Also requires SEGMENT_PROFILE_SPACE_ID (your Unify Space ID, not your workspace ID).
Explicit opt-in. If SEGMENT_PROFILE_TOKEN is unset, no profile tool is registered — the capability doesn't exist for that server instance.
Every lookup is logged — collection, id_type, and the caller — before the request is even sent, via client/profile_api.py's segment_mcp.profile_api logger. The log records *that* a lookup happened and *which* profile, as a truncated SHA-256 digest of the lookup key, never the raw identifier — this client never logs the raw identifier itself, and it silences httpx's own request-URL log process-wide at construction so the identifier doesn't leak that way either, since the Profile API puts it in the URL path. The digest cannot be reversed back to the identifier, but repeated lookups of the same profile are still correlatable across log lines for auditing.
Lookups are case-sensitive. The wrong case returns an empty result, not an error — this client lowercases every lookup value at its boundary and logs a warning when it had to.

No profile-lookup MCP tool is wired into server.py yet — this is the client and trust-boundary machinery a future tool will be built on, per BUILD-PLAN.md's v0.2 scope.

Development

uv sync

uv run pre-commit install uv run ruff check . && uv run ruff format --check . && uv run pyright && uv run pytest

See CONTRIBUTING.md and AGENTS.md.

License

MIT — see LICENSE.

segment-mcp

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Clinics & healthi

Common questions

Alternatives

Mirobody

FHIR MCP Server

Google Health MCP

README from the maker

segment-mcp

Read-only by default

What this refuses to do — permanently, not "for now"

Quick start

The five tools

Prerequisites

Region configuration

Startup checks

Modes

Profile API — a separate, higher trust tier

Development

See also

License