Connect Intercom to Town
Support conversations mined for what customers are really asking, customer history in every brief, and Help Center updates drafted for your approval. One click through Intercom's official MCP server.
Flip read the week's support threads and flagged the article that needs updating.
See it work: a routine that keeps you ahead of your support queue
Surface support trends before Friday standup
The week's themes, surfaced every Friday. Nothing publishes without you.
Open Integrations in Town
Go to Integrations in your Town workspace (free to create) and find Intercom.
Authorize the connection
Sign in to Intercom when prompted. Town connects through Intercom's official MCP server (mcp.intercom.com), so there's nothing to install or configure.
Put your support data to work
Done — your Townie can search conversations, contacts, and companies, pull customer history into briefs, and draft Help Center updates that wait for your approval.
Routines that use Intercom
Ready-made routines from the Town library, built on Intercom. Install one and tailor it to how you work.
Just ask your Townie
Intercom holds the conversations. Town turns them into answers, briefs, and Help Center updates.
“What did customers complain about most this week?”
The week's conversations clustered into themes, with the threads to read first.
“Brief me on Acme before the renewal call.”
Their support history, open threads, and company details, drafted into your prep doc.
“Our onboarding flow changed — update the getting-started article.”
The article redrafted from what actually shipped, held for your approval.
Intercom integration FAQ
The Intercom MCP is Intercom's hosted Model Context Protocol server at mcp.intercom.com — the official integration surface Intercom maintains. MCP is the open standard that lets AI assistants securely work with data from apps — in this case your support conversations, contacts, companies, and Help Center. Town connects to it in one click; no API keys or local setup.
Town only reaches Intercom when you (or a routine you configured) ask for it, and access is scoped to the Intercom workspace you connect. Help Center edits — the only actions with outside effects — always wait for your approval. Read more about how Town approaches security.
No, on both counts. Town can't reply to or close conversations at all — reading them is as far as it goes. And the only write actions, creating or updating a Help Center article, are held for your approval every single time.
Your support conversations (search and full threads), contacts, companies, and Help Center articles. Under the hood these are Intercom's MCP tools: search across conversations and contacts, read full conversation threads, look up contacts and companies, list, search, and read Help Center articles, and — with your approval — create or update an article.
Intercom's MCP server currently supports US-hosted Intercom workspaces; EU- and AU-hosted workspaces aren't supported by Intercom yet. On the Town side you just need an account: free to start, and the connection works on every Town plan.
Intercom is where you talk to customers. Town is where what they said gets put to work: support themes surface in your weekly brief, customer history lands in your call prep, and Help Center gaps turn into drafted updates waiting for your approval.
What is Intercom?
Intercom is the customer service platform where support teams talk to customers — the Messenger, shared inbox, and Help Center that hold every question customers have ever asked you.
Intercom holds the conversations; Town puts them to work. Connected, support trends surface in your briefs, customer history arrives before every call, and Help Center updates are drafted for your approval.
