Cogny CLI · Support

Crisp mined from the shell.

List conversations, read message history, pull people profiles and events, and post replies — from Bash over the Crisp MCP. Turn live-chat transcripts into JSON you can mine for objections, FAQs, and ad-copy verbatims.

# 1. sign up (free for 15 calls) — uses your git email
$ npx @cogny/cli init --agent claude-code

# 2. see every Crisp tool
$ cogny tools list

# 3. call any tool from Bash — no MCP wiring
$ cogny tools call mcp__Crisp__list_conversations --input '{…}'

❯ start Cogny Solo — $9/mo@cogny/cli on npm →

❯

cogny --who

TWO PATHS

You're a human

Reading support history in the Crisp inbox is manual scroll-and-skim. The CLI pulls whole conversations as JSON so an agent can surface recurring objections, content gaps, and the exact phrases customers use. Connect Crisp once in Cogny Solo and let your coding agent — or scheduled reports — do the querying for you.

❯ start Solo

You're an agent

Self-onboard with one command. The CLI issues a key, wires nothing, and exposes every Crisp tool over JSON-RPC. First 15 calls are free.

$ npx @cogny/cli init --agent claude-code

❯

cogny tools call

3 EXAMPLES

Real tool names from the Crisp MCP. Send --input JSON, get JSON back.

mcp__Crisp__list_conversationsList a website inbox, newest first.

$ cogny tools call mcp__Crisp__list_conversations \
  --input '{"website_id":"8c842c8e-4f1e-4f9a-9d2a-1a2b3c4d5e6f","page_number":1,"filter_state":"resolved"}'

example response

{
  "conversations": [
    {
      "session_id": "session_a1",
      "state": "resolved",
      "last_message": "Thanks, that fixed it!",
      "meta": {
        "nickname": "Jordan",
        "email": "jordan@example.com"
      }
    },
    {
      "session_id": "session_a2",
      "state": "resolved",
      "last_message": "Does it work with WooCommerce?",
      "meta": {
        "nickname": "Sam",
        "email": "sam@example.com"
      }
    }
  ]
}

mcp__Crisp__get_conversation_messagesRead full message history for one conversation.

$ cogny tools call mcp__Crisp__get_conversation_messages \
  --input '{"website_id":"8c842c8e-4f1e-4f9a-9d2a-1a2b3c4d5e6f","session_id":"session_a2"}'

example response

[
  {
    "from": "user",
    "type": "text",
    "content": "Does it work with WooCommerce?",
    "timestamp": 1718530000000
  },
  {
    "from": "operator",
    "type": "text",
    "content": "Yes — connect your store keys once and you are set.",
    "timestamp": 1718530120000
  }
]

mcp__Crisp__get_website_statisticsInbox volume and response stats.

$ cogny tools call mcp__Crisp__get_website_statistics \
  --input '{"website_id":"8c842c8e-4f1e-4f9a-9d2a-1a2b3c4d5e6f"}'

example response

{
  "conversations": {
    "total": 1822,
    "resolved": 1690,
    "pending": 14,
    "unresolved": 118
  }
}

❯

cogny tools list

A sample of the rest of the Crisp surface. Run cogny tools list --json for every tool and its input schema.

mcp__Crisp__get_websitemcp__Crisp__list_website_operatorsmcp__Crisp__get_conversationmcp__Crisp__get_conversation_metamcp__Crisp__send_message_in_conversationmcp__Crisp__list_people_profilesmcp__Crisp__get_people_profilemcp__Crisp__list_people_conversationsmcp__Crisp__list_people_events

❯

cogny --faq

Is this an official Crisp CLI?

No — it is the Cogny CLI calling the Crisp MCP over the cogny-mcp-proxy. You connect your Crisp workspace once in Cogny, then read conversations, profiles, and stats from Bash. Crisp IM SARL is not affiliated.

What is the conversation-mining use case?

Pull resolved conversations with `list_conversations` + `get_conversation_messages` and feed the transcripts to an agent to extract objections, FAQ gaps, and the verbatim language customers use for landing-page and ad copy.

Can it reply, or only read?

Both. `send_message_in_conversation` posts a reply and `update_conversation_state` changes status; the rest of the surface is read tools for mining and reporting.

❯

Building an agent? The full tool map for all servers is one fetch: /cli/llms.txt

Crisp mined from the shell.

cogny --who

cogny tools call

cogny tools list

cogny --faq

related CLIs