Can I use Segment as a CLI?

Yes. KosmoKrator exposes a Segment CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Segment through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Segment tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Segment credentials stored?

Segment credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Segment MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

analytics

Segment MCP Integration for Generic MCP Clients

Connect Segment to Generic MCP Clients through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

8 functions 4 read 4 write API token auth

Submit Segment feedback View package source

Connect Segment to Generic MCP Clients

Connect any stdio-compatible MCP client to local KosmoKrator integration tools.

Register kosmo mcp:serve as the command for a local stdio MCP server. The gateway is local, scoped to this integration, and starts with --write=deny so MCP clients can inspect read-capable tools without receiving write access by default.

Segment MCP Config for Generic MCP Clients

Start with read-only write policy and expand only for trusted projects.

{
  "mcpServers": {
    "kosmokrator-segment": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=segment",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=segment --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Segment instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Segment Tools Visible to MCP clients

MCP clients sees stable MCP tool names generated from the Segment integration catalog.

MCP tool	Source function	Type	Description
`integration__segment__segment_identify`	`segment.segment_identify`	Write	Identify a user in Segment with their traits. Links metadata about a user (name, email, plan, etc.) to a known userId so all their events can be attributed correctly.
`integration__segment__segment_track`	`segment.segment_track`	Write	Track a custom event for a user in Segment. Records actions your users perform along with optional properties describing the action.
`integration__segment__segment_page`	`segment.segment_page`	Write	Record a page view in Segment. Tracks when a user views a page, along with optional properties about the page.
`integration__segment__segment_group`	`segment.segment_group`	Write	Associate a user with a group (organization, company, account) in Segment. Lets you record group membership along with optional group traits.
`integration__segment__segment_get_workspace`	`segment.segment_get_workspace`	Read	Get details of a Segment workspace by its slug. Requires an API token to be configured.
`integration__segment__segment_list_sources`	`segment.segment_list_sources`	Read	List all sources in a Segment workspace. Requires an API token to be configured.
`integration__segment__segment_get_source`	`segment.segment_get_source`	Read	Get details of a specific Segment source by ID. Requires an API token to be configured.
`integration__segment__segment_get_current_user`	`segment.segment_get_current_user`	Read	Get the currently authenticated Segment user. Useful for verifying API token credentials are correct.

Related Segment Pages

Segment CLIUse direct JSON commands instead of MCP discovery. Segment MCPFull gateway reference and MCP tool names. KosmoKrator for MCP clientsClient-level gateway setup.