An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Segment to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Manage your customer data pipelines through natural conversation.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 7 capabilities

We ship only the actions that matter.

Capability set01 / 02

01-04

4 capabilities in this set.

Part of 7 available through Segment.

  1. 01

    List tracking plans

    This capability pulls a full list of all tracking plans currently active in your Segment workspace.

  2. 02

    Get source

    Use this to retrieve specific configuration and metadata for a single data source.

  3. 03

    Get tracking plan

    This capability fetches the detailed schema and event requirements for a specific tracking plan.

  4. 04

    Get workspace

    This capability returns the core configuration and details for your current Segment workspace.

Capability set02 / 02

05-07

3 capabilities in this set.

Part of 7 available through Segment.

  1. 05

    List destinations

    This capability shows every destination currently receiving data from a specific source.

  2. 06

    List sources

    Use this to see a complete list of all data sources within your workspace.

  3. 07

    List warehouses

    This capability identifies all data warehouses connected to your Segment workspace.

Real work

What teams actually run

01

Schema Validation

Compare a live event payload against a tracking plan to ensure data integrity.

02

Routing Audits

Verify that data from a specific mobile app source is reaching the correct analytics capabilities.

03

Warehouse Compliance

Confirm which data warehouses are currently receiving data from the workspace.

04

Developer Workflow

Get exact event properties via chat to implement tracking in code.

Automate a task

Put Segment to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Segment works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Segment to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

872ms average. Fast in production.

Segment is checked daily against the live service.

Daily averagePeak 1106ms
Oct 3Today
Fastest day
713ms
Slowest day
1106ms
14-day trend
Slowing+19%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 7 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Segment, so you can see the experience inside your AI.

It does not authenticate your account with Segment. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Segment Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_oCSWGNyPpMslZfXLGFWI7A5SYVuHGSeAvjoUSWuf/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Segment capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "segment-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_oCSWGNyPpMslZfXLGFWI7A5SYVuHGSeAvjoUSWuf/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Segment in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Segment owners hand off.

Technical teams managing customer data pipelines and event tracking schemas.

  • 01

    Data Engineers

    Retrieve event schemas to write accurate tracking code in frontend repositories.

  • 02

    RevOps & Growth

    Map source to destination connections to ensure all capabilities receive data.

  • 03

    Analytics Teams

    Check raw source IDs to configure BI dashboard parameters.

FAQ

Questions Segment owners ask.

  • 01

    How do I connect Segment to my AI client?

    You subscribe to the MCP on Vinkius and provide your Segment Public API Token. Once connected, you can use it immediately in any MCP-compatible client.

  • 02

    What credentials does this MCP need?

    This MCP requires a Public API Token from your Segment admin panel to interact with your workspace.

  • 03

    Can I use this to check my tracking plans?

    Yes. You can use the agent to pull specific tracking plan details and verify event structures.

  • 04

    Does this work with my existing data warehouses?

    Yes. The MCP can list all authorized data warehouses connected to your Segment workspace.

  • 05

    Which AI clients are compatible?

    This MCP works with any compatible client, including Claude, Cursor, Windsurf, and VS Code.

  • 06

    Can the AI create new sources or configure tracking events?

    No. By design, this MCP server uses read-only capability endpoints (list, get). It's engineered strictly to audit, report, and ingest context about your existing architecture to ensure absolute safety and prevent accidental destructiveness.

  • 07

    Can it tell me which downstream destinations are linked to a specific source?

    Absolutely. You can prompt the AI: 'List all destinations tied to the Web App Source [ID]'. Using the list_destinations capability, the agent parses the explicit router table to confirm exact capabilities receiving your events.

  • 08

    Why use an AI agent to read tracking plans?

    Because it radically accelerates coding. If you are developing a new feature in Cursor and need to dispatch tracking info, simply invoke the get_tracking_plan capability. The AI reads the exact structural interface from Segment and writes perfectly matching telemetry code, avoiding human typos.

Explore

More in Growth Engine

Suggestions

Connect Segment to Claude, Cursor, ChatGPT & more