Can I use Karbon as a CLI?

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

Can I expose Karbon through MCP?

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

Where are Karbon credentials stored?

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

Can I deny write access for Karbon MCP tools?

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

productivity

Karbon CLI for CI

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

7 functions 6 read 1 write Bearer token auth

Submit Karbon feedback View package source

Karbon CLI for CI

Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status.

Use this shape when a pipeline needs to read or update an external service. The Karbon CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Karbon CLI for CI
kosmokrator integrations:configure karbon --set access_token="$KARBON_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call karbon.karbon_list_contacts '{"page":1,"limit":1}' --json

Discovery Before Execution

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

kosmo integrations:docs karbon --json
kosmo integrations:docs karbon.karbon_list_contacts --json
kosmo integrations:schema karbon.karbon_list_contacts --json
kosmo integrations:search "Karbon" --json
kosmo integrations:list --json

Useful Karbon CLI Functions

Function	Type	Parameters	Description
`karbon.karbon_list_contacts`	Read	page, limit	List contacts in Karbon. Returns a paginated list of contacts with their names, emails, companies, and other details.
`karbon.karbon_get_contact`	Read	id	Get a single contact from Karbon by its unique identifier. Returns full contact details including name, email, phone, company, and any associated notes.
`karbon.karbon_create_contact`	Write	firstName, lastName, email, company, phone	Create a new contact in Karbon. Provide at least a first name and last name. Optionally include email, company, and phone number.
`karbon.karbon_list_work_items`	Read	page, limit, status, assignee	List work items in Karbon. Returns a paginated list of work items. Optionally filter by status (e.g., "Open", "InProgress", "Completed") or by assignee.
`karbon.karbon_get_work_item`	Read	id	Get a single work item from Karbon by its unique identifier. Returns full details including title, description, status, assignee, due date, and any associated notes.
`karbon.karbon_list_users`	Read	limit	List users in the Karbon account. Returns user details including names, emails, and roles. Use this to find assignees for work items.
`karbon.karbon_get_current_user`	Read	none	Get the currently authenticated Karbon user. Returns the profile of the user whose access token is configured for this integration.

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 Karbon CLI Pages

Cron Jobs Karbon CLI for cron jobs. Shell Scripts Karbon CLI for shell scripts. Headless Automation Karbon CLI for headless automation. Coding Agents Karbon CLI for coding agents.