Kaosensei MCP Server

Kaosensei MCP server exists for a simple reason — assistants are far more useful when they can act on Kaosensei directly instead of describing what you should do. Intercom MCP server for Help Center content management and CS workflow automation.

What the assistant can call

Once Kaosensei is connected, these are the calls the assistant has available:

• Articles — The Articles tool exposed by this server
• Collections — The Collections tool exposed by this server
• Admin — The Admin tool exposed by this server
• Conversations — The Conversations tool exposed by this server
• get_article — The get_article tool exposed by this server
• list_articles — The list_articles tool exposed by this server
• search_articles — Search for articles using keywords. Supports full-text search across article content with multilingual support (English, Chinese, Japanese, etc.)
• create_article — The create_article tool exposed by this server
• update_article — Update an existing article. Only provided fields will be updated
• list_collections — The list_collections tool exposed by this server
• get_collection — The get_collection tool exposed by this server
• update_collection — Update an existing collection. Only provided fields will be updated. Perfect for adding missing translations!

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need 2 environment variables: INTERCOM_ACCESS_TOKEN, INTERCOM_ADMIN_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Kaosensei's toolset — Articles, Collections, Admin and 11 more — is a fair guide to whether it matches your workflow. It is maintained by chatflowdev; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Kaosensei's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Kaosensei.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the kaosensei mcp server does with a few real requests.