Can I use Missive as a CLI?

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

Can I expose Missive through MCP?

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

Where are Missive credentials stored?

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

Can I deny write access for Missive MCP tools?

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

communication

Missive MCP Integration for CrewAI

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

6 functions 4 read 2 write Bearer token auth

Submit Missive feedback View package source

Connect Missive 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.

Missive MCP Config for CrewAI

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

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

Expose only Missive 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.

Missive Tools Visible to CrewAI

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

MCP tool	Source function	Type	Description
`integration__missive__missive_list_conversations`	`missive.missive_list_conversations`	Read	List conversations from Missive. Supports filtering by inbox, assignee, and state. Returns paginated results.
`integration__missive__missive_get_conversation`	`missive.missive_get_conversation`	Read	Get a single Missive conversation by ID, including messages and metadata.
`integration__missive__missive_create_comment`	`missive.missive_create_comment`	Write	Create a comment on a Missive conversation. Use this to add internal notes or replies.
`integration__missive__missive_list_tasks`	`missive.missive_list_tasks`	Read	List tasks from Missive. Supports filtering by state and assignee. Returns paginated results.
`integration__missive__missive_create_task`	`missive.missive_create_task`	Write	Create a new task in Missive. Requires a title. Optionally set description, assignee, and due date.
`integration__missive__missive_get_current_user`	`missive.missive_get_current_user`	Read	Get the profile of the currently authenticated Missive user, including name, email, and organization info.

Related Missive Pages

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