Can I use Autopilot as a CLI?

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

Can I expose Autopilot through MCP?

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

Where are Autopilot credentials stored?

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

Can I deny write access for Autopilot MCP tools?

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

marketing

Autopilot CLI for Headless Automation

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

7 functions 6 read 1 write API key auth

Submit Autopilot feedback View package source

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

Command Shape

# Autopilot CLI for Headless Automation
kosmokrator integrations:configure autopilot --set api_key="$AUTOPILOT_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call autopilot.autopilot_list_contacts '{"limit":1,"bookmark":"example_bookmark"}' --json

Discovery Before Execution

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

kosmo integrations:docs autopilot --json
kosmo integrations:docs autopilot.autopilot_list_contacts --json
kosmo integrations:schema autopilot.autopilot_list_contacts --json
kosmo integrations:search "Autopilot" --json
kosmo integrations:list --json

Useful Autopilot CLI Functions

Function	Type	Parameters	Description
`autopilot.autopilot_list_contacts`	Read	limit, bookmark	List contacts in your Autopilot account. Returns contact IDs, emails, and names.
`autopilot.autopilot_get_contact`	Read	contact_id	Get detailed information about a specific Autopilot contact by ID or email address.
`autopilot.autopilot_create_contact`	Write	email, first_name, last_name, phone, title, company, custom_fields	Create or update a contact in Autopilot. Requires an email address; other fields are optional.
`autopilot.autopilot_list_lists`	Read	none	List all lists in your Autopilot account. Returns list IDs and titles.
`autopilot.autopilot_get_list`	Read	list_id	Get detailed information about a specific Autopilot list, including contacts.
`autopilot.autopilot_list_journeys`	Read	none	List all journeys in your Autopilot account. Returns journey IDs and names.
`autopilot.autopilot_get_current_user`	Read	none	Get the authenticated user's Autopilot account details.

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

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