Can I use Crisp as a CLI?

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

Can I expose Crisp through MCP?

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

Where are Crisp credentials stored?

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

Can I deny write access for Crisp MCP tools?

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

messaging

Crisp MCP Integration for Generic MCP Clients

Connect Crisp to Generic MCP Clients through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write API key auth

Submit Crisp feedback View package source

Connect Crisp to Generic MCP Clients

Connect any stdio-compatible MCP client to local KosmoKrator integration tools.

Register kosmo mcp:serve as the command for a local stdio MCP server. The gateway is local, scoped to this integration, and starts with --write=deny so MCP clients can inspect read-capable tools without receiving write access by default.

Crisp MCP Config for Generic MCP Clients

Start with read-only write policy and expand only for trusted projects.

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

Run the Gateway Manually

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

Why Use KosmoKrator Here

Scoped tools

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

Crisp Tools Visible to MCP clients

MCP clients sees stable MCP tool names generated from the Crisp integration catalog.

MCP tool	Source function	Type	Description
`integration__crisp__crisp_list_conversations`	`crisp.crisp_list_conversations`	Read	List chat conversations from Crisp. Returns conversation sessions with status, participant info, and last message preview. Supports pagination.
`integration__crisp__crisp_get_conversation`	`crisp.crisp_get_conversation`	Read	Get details and messages of a specific Crisp conversation. Returns the full message thread including sender info, timestamps, and message content.
`integration__crisp__crisp_send_message`	`crisp.crisp_send_message`	Write	Send a message in a Crisp conversation. Posts as an operator by default. Use the "type" parameter to send text, notes, or file messages.
`integration__crisp__crisp_list_contacts`	`crisp.crisp_list_contacts`	Read	List contacts from Crisp. Returns contact profiles with email, name, and custom data. Supports pagination.
`integration__crisp__crisp_get_contact`	`crisp.crisp_get_contact`	Read	Get details of a specific Crisp contact. Returns profile info, custom data, segments, and more.
`integration__crisp__crisp_list_campaigns`	`crisp.crisp_list_campaigns`	Read	List marketing campaigns from Crisp. Returns campaigns with status, template details, and delivery statistics. Supports pagination.
`integration__crisp__crisp_get_current_user`	`crisp.crisp_get_current_user`	Read	Get the currently authenticated Crisp user profile. Useful for verifying credentials and identifying the connected operator.

Related Crisp Pages

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