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.

productivity

Autopilot MCP, CLI, and Lua Integration for AI Agents

Autopilot integration docs for AI agents: MCP gateway setup, Autopilot CLI commands, Lua API reference, credentials, and function schemas.

Autopilot for agents

Credentials can be configured manually in web or CLI hosts.

Use this integration from Lua code mode, the headless integrations CLI, or the KosmoKrator MCP gateway. The same package metadata powers all three surfaces.

Agent Surfaces

Autopilot CLIHeadless setup, JSON output, direct function calls. Autopilot MCPExpose selected tools to local MCP clients. Autopilot LuaAgent-facing namespace and Lua reference. FeedbackReport missing tools, auth issues, or bad metadata.

Machine-Readable Metadata

integration_slug: autopilot
route_slug: autopilot
package: autopilot
auth_strategy: api_key_header
cli_setup_supported: true
cli_runtime_supported: true
mcp_gateway_supported: true
lua_supported: true

Function Catalog

Function	Type	Description
`autopilot.autopilot_create_contact`	Write `write`	Create or update a contact. Autopilot de-duplicates contacts by Email and merges provided fields. Official Autopilot API Blueprint endpoint: POST https://api.autopilothq.com/v1/contact.
`autopilot.autopilot_get_contact`	Read `read`	Retrieve one contact by Autopilot contact_id or email address. Official Autopilot API Blueprint endpoint: GET https://api.autopilothq.com/v1/contact/{contact_id_or_email}.
`autopilot.autopilot_delete_contact`	Write `write`	Permanently delete one contact by Autopilot contact_id or email address. Official Autopilot API Blueprint endpoint: DELETE https://api.autopilothq.com/v1/contact/{contact_id_or_email}.
`autopilot.autopilot_get_contacts_on_list`	Read `read`	Retrieve contacts belonging to a specific Autopilot list. Official Autopilot API Blueprint endpoint: GET https://api.autopilothq.com/v1/list/{list_id}.
`autopilot.autopilot_add_list`	Write `write`	Create a new Autopilot list. Official Autopilot API Blueprint endpoint: POST https://api.autopilothq.com/v1/list.
`autopilot.autopilot_delete_list`	Write `write`	Delete an Autopilot list. Supply the documented list identifier in payload. Official Autopilot API Blueprint endpoint: DELETE https://api.autopilothq.com/v1/list.
`autopilot.autopilot_eject_contact_from_journey`	Write `write`	Remove a contact from a specific journey before they complete all steps. Official Autopilot API Blueprint endpoint: DELETE https://api.autopilothq.com/v1/journey/{journey_id}/contact/{contact_id_or_email}.
`autopilot.autopilot_register_rest_hook`	Write `write`	Register a REST hook target URL for a supported Autopilot event. Official Autopilot API Blueprint endpoint: POST https://api.autopilothq.com/v1/hook.
`autopilot.autopilot_unregister_rest_hook`	Write `write`	Unregister a REST hook by hook_id. Official Autopilot API Blueprint endpoint: DELETE https://api.autopilothq.com/v1/hook/{hook_id}.
`autopilot.autopilot_list_rest_hooks`	Read `read`	List registered REST hooks. Official Autopilot API Blueprint endpoint: GET https://api.autopilothq.com/v1/hooks.