Getting started

SegmentStream MCP uses the Streamable HTTP transport at https://mcp.segmentstream.com/mcp. You authenticate with an API token passed in the Authorization header.

Prerequisites

Before you begin, you need:

A SegmentStream account with access to at least one project
An API token — contact your SegmentStream manager or generate one from the SegmentStream admin panel
An MCP-compatible AI tool — Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, or any client that supports MCP

Setup by tool

Run this command in your terminal:

claude mcp add segmentstream \
  --transport http \
  --header "Authorization: Bearer YOUR_API_TOKEN" \
  https://mcp.segmentstream.com/mcp

Replace YOUR_API_TOKEN with your SegmentStream API token.You can scope the server to your project, your user profile, or local only:

Flag	Scope	Config file
`-s project`	Shared with your team via `.mcp.json`	`.mcp.json` in project root
`-s user`	Personal, across all projects	`~/.claude/settings.json`
(default)	Local to this project	`.mcp.json` in project root

If you use project scope, your API token will be stored in the config file. Consider using an environment variable reference like ${SEGMENTSTREAM_API_TOKEN} instead.

Open Settings → MCP and add a new server, or edit .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "segmentstream": {
      "type": "http",
      "url": "https://mcp.segmentstream.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Replace YOUR_API_TOKEN with your SegmentStream API token. Restart Cursor to activate the connection.

Create or edit .vscode/mcp.json in your project root:

{
  "servers": {
    "segmentstream": {
      "type": "http",
      "url": "https://mcp.segmentstream.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:segmentstream-token}"
      }
    }
  },
  "inputs": [
    {
      "id": "segmentstream-token",
      "type": "promptString",
      "description": "SegmentStream API token",
      "password": true
    }
  ]
}

VS Code will prompt you for the token on first use so it is not stored in the config file.

Open Settings → Connectors (requires a Claude Pro, Max, Team, or Enterprise plan) and add a new MCP server with this URL:

https://mcp.segmentstream.com/mcp

You will need to configure the Authorization header with your API token. Alternatively, use the STDIO transport with the mcp-remote bridge:

{
  "mcpServers": {
    "segmentstream": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.segmentstream.com/mcp",
        "--header",
        "Authorization: Bearer YOUR_API_TOKEN"
      ]
    }
  }
}

Open Settings, search for “MCP”, and edit the config file to add:

{
  "mcpServers": {
    "segmentstream": {
      "type": "http",
      "url": "https://mcp.segmentstream.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Replace YOUR_API_TOKEN with your SegmentStream API token.

Any MCP client that supports the Streamable HTTP transport can connect to SegmentStream MCP. Use these settings:

Setting	Value
Transport	Streamable HTTP
URL	`https://mcp.segmentstream.com/mcp`
Authorization header	`Bearer YOUR_API_TOKEN`

If your client only supports SSE, use the same URL — the server supports both Streamable HTTP and SSE transports.If your client only supports STDIO, use the mcp-remote bridge:

npx mcp-remote https://mcp.segmentstream.com/mcp \
  --header "Authorization: Bearer YOUR_API_TOKEN"

Verify the connection

After setup, test that the connection works by asking your AI assistant:

List my SegmentStream projects

The assistant should call the list_active_projects tool and return a list of projects you have access to. If you see your projects, the connection is working.

Using environment variables

To avoid storing your API token in config files, use an environment variable:

Set the environment variable

Add this to your shell profile (.bashrc, .zshrc, or similar):

export SEGMENTSTREAM_API_TOKEN="your-token-here"

Reference it in the config

Use ${SEGMENTSTREAM_API_TOKEN} in your MCP configuration:

{
  "mcpServers": {
    "segmentstream": {
      "type": "http",
      "url": "https://mcp.segmentstream.com/mcp",
      "headers": {
        "Authorization": "Bearer ${SEGMENTSTREAM_API_TOKEN}"
      }
    }
  }
}

Environment variable substitution syntax varies by client. The ${VAR} syntax works in Claude Code and Cursor. Check your tool’s documentation for details.

Troubleshooting

Connection fails with 401 Unauthorized

Your API token is missing or invalid. Double-check that:

The token is correct and has not expired
The Authorization header uses the Bearer prefix
There are no extra spaces or line breaks in the token

Tools are not showing up

Some MCP clients need a restart after adding a new server. Close and reopen your AI tool, then try again.

Environment variable is not resolved

Make sure the variable is exported in your shell and that your AI tool was started from a shell session where the variable is available. IDE-launched terminals sometimes do not inherit variables from your profile.

Next steps

Browse the supported tools to see everything you can do with SegmentStream MCP.

Project configuration

Dashboards

Attribution

Optimization

Geo Tests

MCP

Getting started

Prerequisites

Setup by tool

Verify the connection

Using environment variables

Troubleshooting

Next steps

Getting started

Project configuration

Dashboards

Attribution

Optimization

Geo Tests

MCP

​Prerequisites

​Setup by tool

​Verify the connection

​Using environment variables

​Troubleshooting

​Next steps

Prerequisites

Setup by tool

Verify the connection

Using environment variables

Troubleshooting

Next steps