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 CLI for AI Agents

Use the Crisp CLI from KosmoKrator to call Crisp tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

7 functions 6 read 1 write API key auth

Submit Crisp feedback View package source

Crisp CLI Setup

Crisp can be configured headlessly with `kosmokrator integrations:configure crisp`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure crisp --set api_key="$CRISP_API_KEY" --set website_id="$CRISP_WEBSITE_ID" --enable --read allow --write ask --json
kosmokrator integrations:doctor crisp --json
kosmokrator integrations:status --json

Credentials

Authentication type: API key api_key. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

Key	Env var	Type	Required	Label
`api_key`	`CRISP_API_KEY`	Secret `secret`	yes	API Key (Token ID)
`website_id`	`CRISP_WEBSITE_ID`	Text `string`	yes	Website ID
`url`	`CRISP_URL`	URL `url`	no	API Base URL

Call Crisp Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call crisp.crisp_list_conversations '{
  "page": 1,
  "per_page": 1
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:crisp crisp_list_conversations '{
  "page": 1,
  "per_page": 1
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs crisp --json
kosmo integrations:docs crisp.crisp_list_conversations --json
kosmo integrations:schema crisp.crisp_list_conversations --json
kosmo integrations:search "Crisp" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Crisp.

`crisp.crisp_list_conversations`

Read read

List chat conversations from Crisp. Returns conversation sessions with status, participant info, and last message preview. Supports pagination.

Parameters: page, per_page

Generic CLI call

kosmo integrations:call crisp.crisp_list_conversations '{"page":1,"per_page":1}' --json

Provider shortcut

kosmo integrations:crisp crisp_list_conversations '{"page":1,"per_page":1}' --json

`crisp.crisp_get_conversation`

Read read

Get details and messages of a specific Crisp conversation. Returns the full message thread including sender info, timestamps, and message content.

Parameters: conversation_id

Generic CLI call

kosmo integrations:call crisp.crisp_get_conversation '{"conversation_id":"example_conversation_id"}' --json

Provider shortcut

kosmo integrations:crisp crisp_get_conversation '{"conversation_id":"example_conversation_id"}' --json

`crisp.crisp_send_message`

Write 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.

Parameters: conversation_id, text, type, from

Generic CLI call

kosmo integrations:call crisp.crisp_send_message '{"conversation_id":"example_conversation_id","text":"example_text","type":"example_type","from":"example_from"}' --json

Provider shortcut

kosmo integrations:crisp crisp_send_message '{"conversation_id":"example_conversation_id","text":"example_text","type":"example_type","from":"example_from"}' --json

`crisp.crisp_list_contacts`

Read read

List contacts from Crisp. Returns contact profiles with email, name, and custom data. Supports pagination.

Parameters: page, per_page

Generic CLI call

kosmo integrations:call crisp.crisp_list_contacts '{"page":1,"per_page":1}' --json

Provider shortcut

kosmo integrations:crisp crisp_list_contacts '{"page":1,"per_page":1}' --json

`crisp.crisp_get_contact`

Read read

Get details of a specific Crisp contact. Returns profile info, custom data, segments, and more.

Parameters: contact_id

Generic CLI call

kosmo integrations:call crisp.crisp_get_contact '{"contact_id":"example_contact_id"}' --json

Provider shortcut

kosmo integrations:crisp crisp_get_contact '{"contact_id":"example_contact_id"}' --json

`crisp.crisp_list_campaigns`

Read read

List marketing campaigns from Crisp. Returns campaigns with status, template details, and delivery statistics. Supports pagination.

Parameters: page, per_page

Generic CLI call

kosmo integrations:call crisp.crisp_list_campaigns '{"page":1,"per_page":1}' --json

Provider shortcut

kosmo integrations:crisp crisp_list_campaigns '{"page":1,"per_page":1}' --json

`crisp.crisp_get_current_user`

Read read

Get the currently authenticated Crisp user profile. Useful for verifying credentials and identifying the connected operator.

Parameters: none

Generic CLI call

kosmo integrations:call crisp.crisp_get_current_user '{}' --json

Provider shortcut

kosmo integrations:crisp crisp_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

`crisp.crisp_list_conversations`

List chat conversations from Crisp. Returns conversation sessions with status, participant info, and last message preview. Supports pagination.

Operation: Read read
Schema command: kosmo integrations:schema crisp.crisp_list_conversations --json

Parameter	Type	Required	Description
`page`	integer	no	Page number (1-based). Default: 1.
`per_page`	integer	no	Number of conversations per page (max 100). Default: 25.

`crisp.crisp_get_conversation`

Get details and messages of a specific Crisp conversation. Returns the full message thread including sender info, timestamps, and message content.

Operation: Read read
Schema command: kosmo integrations:schema crisp.crisp_get_conversation --json

Parameter	Type	Required	Description
`conversation_id`	string	yes	The conversation session ID.

`crisp.crisp_send_message`

Send a message in a Crisp conversation. Posts as an operator by default. Use the "type" parameter to send text, notes, or file messages.

Operation: Write write
Schema command: kosmo integrations:schema crisp.crisp_send_message --json

Parameter	Type	Required	Description
`conversation_id`	string	yes	The conversation session ID to send the message to.
`text`	string	yes	The message text to send.
`type`	string	no	Message type: "text" (default), "note" (internal note), "file", etc.
`from`	string	no	Message origin: "operator" (default) or "user".

`crisp.crisp_list_contacts`

List contacts from Crisp. Returns contact profiles with email, name, and custom data. Supports pagination.

Operation: Read read
Schema command: kosmo integrations:schema crisp.crisp_list_contacts --json

Parameter	Type	Required	Description
`page`	integer	no	Page number (1-based). Default: 1.
`per_page`	integer	no	Number of contacts per page (max 100). Default: 25.

`crisp.crisp_get_contact`

Get details of a specific Crisp contact. Returns profile info, custom data, segments, and more.

Operation: Read read
Schema command: kosmo integrations:schema crisp.crisp_get_contact --json

Parameter	Type	Required	Description
`contact_id`	string	yes	The contact identifier (email or Crisp contact ID).

`crisp.crisp_list_campaigns`

List marketing campaigns from Crisp. Returns campaigns with status, template details, and delivery statistics. Supports pagination.

Operation: Read read
Schema command: kosmo integrations:schema crisp.crisp_list_campaigns --json

Parameter	Type	Required	Description
`page`	integer	no	Page number (1-based). Default: 1.
`per_page`	integer	no	Number of campaigns per page (max 100). Default: 25.

`crisp.crisp_get_current_user`

Get the currently authenticated Crisp user profile. Useful for verifying credentials and identifying the connected operator.

Operation: Read read
Schema command: kosmo integrations:schema crisp.crisp_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.