How to Connect Chatwoot to Gemini via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Chatwoot, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Chatwoot + Gemini

Chatwoot omnichannel support inbox, Cloud or self-hosted: conversations and messages across WhatsApp, e-mail, web chat and social channels, contacts, labels, agents, teams, canned responses and support reports (first response, resolution and reply times). Replies, private notes and new conversations are included, installed switched off.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

CHATWOOT_URL, CHATWOOT_API_TOKEN, CHATWOOT_ACCOUNT_ID

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a Chatwoot account, on Chatwoot Cloud or self-hosted, and the access token of the user the AI should act as.

1. Sign in to Chatwoot with that user. Agents only see conversations of the inboxes they belong to and cannot read reports, so use an administrator for the full picture.
2. Click your avatar, then Profile Settings, and copy the Access Token at the bottom of the page into CHATWOOT_API_TOKEN. It does not expire; you can reset it on the same page.
3. Set CHATWOOT_URL to the address you open Chatwoot at: https://app.chatwoot.com on Chatwoot Cloud, or your own domain such as https://chat.example.com when self-hosted. No path, no /app, no /api.
4. Set CHATWOOT_ACCOUNT_ID to the number after /app/accounts/ in the browser address bar: https://app.chatwoot.com/app/accounts/3/dashboard means 3.
5. Install the connector and run chatwoot_get_profile: it shows the user behind the token, their role, and every account the token can reach with its id.

Account token, not Platform API: the token of a self-hosted super admin's Platform App (/platform/api) does not work here. The connector uses the Chatwoot Application API of one account.

Self-hosted behind nginx: the token travels in the api_access_token header, and nginx drops headers with an underscore unless underscores_in_headers on; is set. That shows up as 401 on every call although the token is right. On AnythingMCP Cloud, a self-hosted Chatwoot that only lives in a private network cannot be reached; run a self-hosted AnythingMCP inside that network instead.

What it reads: the account and the user behind the token; your inboxes (WhatsApp, e-mail, web widget, API, Instagram, Telegram and so on) with their members; agents and administrators with their availability; teams and their members; labels, canned responses and custom attribute definitions; conversations with status, priority, inbox, labels, contact, assignee and team, as lists, counts or with filters such as created after a date and assigned to one agent; the messages of a conversation including private notes and attachments; contacts by name, e-mail, phone number or identifier, with all their conversations across inboxes; and the support reports: totals for a period next to the previous period, a metric over time, agents, inboxes or teams compared side by side, and what is open and unattended right now. Inbox channel secrets and the user's own access token are removed from responses.

Times and figures: conversation and message times and report periods are Unix timestamps in seconds (UTC), and the AI converts them before quoting a time. First response, resolution and reply times in reports are seconds.

Asks before every change: chatwoot_set_conversation_labels. Chatwoot replaces the whole label list of a conversation, so the AI first reads the current labels and sends them together with the new one (or without the one to remove). Labels must already exist in the account. The AI shows you the conversation and the new label list and waits for your yes.

Switched off at install: chatwoot_send_message (a reply, or a private note only agents see) and chatwoot_create_conversation. A reply or a first message reaches the customer at once on WhatsApp, e-mail or chat, so an administrator turns them on deliberately. Even then the AI shows you the text and the recipient and waits for your yes. On WhatsApp Cloud API inboxes, free text only reaches a contact within 24 hours of their last message; outside that window Chatwoot needs an approved template, which this connector does not send.

Limits: conversation lists come 25 per page, contacts 15 per page and messages 20 at a time, so the AI pages through them; for a plain number it counts instead of listing. Reports and live stats need an administrator token.

Common errors: 401 means a wrong or reset token, or nginx dropping the header. 404 on every call usually means a wrong CHATWOOT_URL or CHATWOOT_ACCOUNT_ID; 404 on one conversation means an id this user cannot see. Reports answer 401 or 403 for agents who are not administrators.

The connector does not use the Platform API, send WhatsApp templates, resolve, reassign or delete existing conversations, or edit or delete contacts.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Gemini

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Gemini CLI reads MCP servers from ~/.gemini/settings.json (on Windows %USERPROFILE%\.gemini\settings.json). Add:

{
  "mcpServers": {
    "anythingmcp": {
      "httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
      "headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
    }
  }
}

1. Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of YOUR_MCP_API_KEY.
2. Save the file and restart gemini.
3. Run /mcp inside Gemini CLI (or gemini mcp list in your shell): anythingmcp should show as connected.
4. Start prompting: Gemini CLI can now call the Chatwoot tools.

Available tools

Example prompts

• "How many open conversations are unassigned right now, and which agents have unattended chats?"
• "Read conversation 1284 and summarise what the customer wants and what we already promised."
• "Find the contact [email protected] and list all her conversations across WhatsApp and e-mail."
• "Compare our agents over the last 30 days: conversations handled, first response time and resolution time."
• "Add the label refund to conversation 1284 and keep its other labels. Show me the new list first."

FAQ

Where does Gemini CLI look for MCP servers? In ~/.gemini/settings.json for your user, or in .gemini/settings.json inside a project. gemini mcp list shows each server and whether it connects.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT