Can I use Split as a CLI?

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

Can I expose Split through MCP?

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

Where are Split credentials stored?

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

Can I deny write access for Split MCP tools?

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

productivity

Split MCP Integration for LangChain

Connect Split to LangChain through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write Bearer token auth

Submit Split feedback View package source

Connect Split to LangChain

Bridge LangChain agents to local KosmoKrator integration tools through MCP or headless CLI calls.

Use the MCP gateway when the agent should discover tools, or wrap kosmo integrations:call for fixed chains. The gateway is local, scoped to this integration, and starts with --write=deny so LangChain can inspect read-capable tools without receiving write access by default.

Split MCP Config for LangChain

Keep the gateway scoped to the integration and operation class needed by the chain.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

Expose only Split 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.

Split Tools Visible to LangChain

LangChain sees stable MCP tool names generated from the Split integration catalog.

MCP tool	Source function	Type	Description
`integration__split__split_list_splits`	`split.split_list_splits`	Read	List feature splits in a Split workspace. Returns split names, descriptions, traffic type, and creation date.
`integration__split__split_get_split`	`split.split_get_split`	Read	Get detailed information about a specific Split feature split, including its definition and traffic allocation.
`integration__split__split_create_split`	`split.split_create_split`	Write	Create a new feature split in a Split workspace. Specify a name, traffic type, and optional description.
`integration__split__split_list_environments`	`split.split_list_environments`	Read	List all environments for a Split workspace. Returns environment IDs, names, and their status.
`integration__split__split_get_environment`	`split.split_get_environment`	Read	Get detailed information about a specific Split environment, including its name, type, and status.
`integration__split__split_list_workspaces`	`split.split_list_workspaces`	Read	List all Split workspaces. Returns workspace IDs, names, and the number of environments.
`integration__split__split_get_current_user`	`split.split_get_current_user`	Read	Get information about the currently authenticated Split user. Useful for verifying API credentials.

Related Split Pages

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