Skip to content
Talk to sales Start building
Chatwoot logo

Chatwoot MCP server

Receive and reply to customer messages with Chatwoot

Chatwoot is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Start building See the Chatwoot integration
Tools
2
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
September 2026

About the Chatwoot MCP server

Connect Chatwoot once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Chatwoot and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Chatwoot tools your AI can run

Once connected, your assistant can call any of these Chatwoot actions by asking in plain language.

  • Send Message

    Send a message reply to a Chatwoot conversation

    3 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Triggers

Chatwoot events your agent can watch

These start a run the moment something happens in Chatwoot, so work gets picked up on its own.

  • New Incoming Message

    Triggers when a contact sends a new message in a Chatwoot conversation

Give your assistant Chatwoot

Connect Chatwoot once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Get your server URLTalk to sales

Chatwoot MCP, answered.

No. That is the point of it. One Activepieces server exposes Chatwoot alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Chatwoot in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 2 tools, including Send Message, Custom API Call, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.