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 CLI for Headless Automation

Use the Split CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write Bearer token auth

Submit Split feedback View package source

Split CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Split CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Split CLI for Headless Automation
kosmokrator integrations:configure split --set access_token="$SPLIT_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call split.split_list_splits '{"workspace_id":"example_workspace_id","limit":1,"offset":1}' --json

Discovery Before Execution

Agents and scripts can inspect Split docs and schemas before choosing a function.

kosmo integrations:docs split --json
kosmo integrations:docs split.split_list_splits --json
kosmo integrations:schema split.split_list_splits --json
kosmo integrations:search "Split" --json
kosmo integrations:list --json

Useful Split CLI Functions

Function	Type	Parameters	Description
`split.split_list_splits`	Read	workspace_id, limit, offset	List feature splits in a Split workspace. Returns split names, descriptions, traffic type, and creation date.
`split.split_get_split`	Read	split_name, workspace_id	Get detailed information about a specific Split feature split, including its definition and traffic allocation.
`split.split_create_split`	Write	name, traffic_type_name, description, workspace_id	Create a new feature split in a Split workspace. Specify a name, traffic type, and optional description.
`split.split_list_environments`	Read	workspace_id	List all environments for a Split workspace. Returns environment IDs, names, and their status.
`split.split_get_environment`	Read	environment_id, workspace_id	Get detailed information about a specific Split environment, including its name, type, and status.
`split.split_list_workspaces`	Read	none	List all Split workspaces. Returns workspace IDs, names, and the number of environments.
`split.split_get_current_user`	Read	none	Get information about the currently authenticated Split user. Useful for verifying API credentials.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Split CLI Pages

CI Split CLI for CI. Cron Jobs Split CLI for cron jobs. Shell Scripts Split CLI for shell scripts. Coding Agents Split CLI for coding agents.