Can I use Attio as a CLI?

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

Can I expose Attio through MCP?

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

Where are Attio credentials stored?

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

Can I deny write access for Attio MCP tools?

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

other

Attio CLI for Headless Automation

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

7 functions 6 read 1 write Bearer token auth

Submit Attio feedback View package source

Attio 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 Attio CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Attio CLI for Headless Automation
kosmokrator integrations:configure attio --set access_token="$ATTIO_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call attio.attio_list_records '{"object_id":"example_object_id","limit":1,"offset":1,"sorts":"example_sorts","filters":"example_filters"}' --json

Discovery Before Execution

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

kosmo integrations:docs attio --json
kosmo integrations:docs attio.attio_list_records --json
kosmo integrations:schema attio.attio_list_records --json
kosmo integrations:search "Attio" --json
kosmo integrations:list --json

Useful Attio CLI Functions

Function	Type	Parameters	Description
`attio.attio_list_records`	Read	object_id, limit, offset, sorts, filters	List records for an object type in Attio (e.g. people, companies, deals). Supports filtering, sorting, and pagination via a POST query endpoint. Use filters to narrow results by attribute values and sorts to control ordering.
`attio.attio_get_record`	Read	object_id, id	Get a single record from Attio by its object type and record ID. Returns full record details including all attribute values.
`attio.attio_create_record`	Write	object_id, data	Create a new record in Attio for a given object type. Pass attribute values keyed by their attribute slug in the data parameter.
`attio.attio_list_objects`	Read	none	List all object types defined in the Attio workspace (e.g. people, companies, deals, custom objects). Useful for discovering available objects before querying records.
`attio.attio_get_object`	Read	id	Get details for a specific object type in Attio, including its attributes and their types. Useful for understanding what fields are available before creating or updating records.
`attio.attio_list_workspaces`	Read	none	List all Attio workspaces accessible to the authenticated user. Returns workspace IDs and names useful for understanding the context of the current integration.
`attio.attio_get_current_user`	Read	none	Get the currently authenticated Attio user profile. Useful for verifying API connectivity and identifying which workspace the integration is connected to.

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

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