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 MCP Integration for CrewAI

Connect Autopilot to CrewAI through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write API key auth

Submit Autopilot feedback View package source

Connect Autopilot to CrewAI

Expose KosmoKrator integrations to CrewAI workers as scoped local tools.

Wrap kosmo integrations:call for specific tasks or connect workers to a local MCP gateway. The gateway is local, scoped to this integration, and starts with --write=deny so CrewAI can inspect read-capable tools without receiving write access by default.

Autopilot MCP Config for CrewAI

Use per-worker integration scopes to avoid giving every worker every tool.

{
  "mcpServers": {
    "kosmokrator-autopilot": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=autopilot",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=autopilot --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Autopilot instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Autopilot Tools Visible to CrewAI

CrewAI sees stable MCP tool names generated from the Autopilot integration catalog.

MCP tool	Source function	Type	Description
`integration__autopilot__autopilot_list_contacts`	`autopilot.autopilot_list_contacts`	Read	List contacts in your Autopilot account. Returns contact IDs, emails, and names.
`integration__autopilot__autopilot_get_contact`	`autopilot.autopilot_get_contact`	Read	Get detailed information about a specific Autopilot contact by ID or email address.
`integration__autopilot__autopilot_create_contact`	`autopilot.autopilot_create_contact`	Write	Create or update a contact in Autopilot. Requires an email address; other fields are optional.
`integration__autopilot__autopilot_list_lists`	`autopilot.autopilot_list_lists`	Read	List all lists in your Autopilot account. Returns list IDs and titles.
`integration__autopilot__autopilot_get_list`	`autopilot.autopilot_get_list`	Read	Get detailed information about a specific Autopilot list, including contacts.
`integration__autopilot__autopilot_list_journeys`	`autopilot.autopilot_list_journeys`	Read	List all journeys in your Autopilot account. Returns journey IDs and names.
`integration__autopilot__autopilot_get_current_user`	`autopilot.autopilot_get_current_user`	Read	Get the authenticated user's Autopilot account details.

Related Autopilot Pages

Autopilot CLIUse direct JSON commands instead of MCP discovery. Autopilot MCPFull gateway reference and MCP tool names. KosmoKrator for CrewAIClient-level gateway setup.