Turn Support Meeting Decisions into Help Center Drafts with SuperIntern MCP and Intercom
Every support team meeting has the same recurring line: "We got this question again this week. We should really turn it into a help article."
The problem is what happens next. Writing the article becomes someone's homework, ticket volume buries it, and a week later the same meeting asks, "Whatever happened to that article?" Meanwhile, the frontline keeps answering the same question by hand, one conversation at a time. From "let's document this" to a published article, two weeks is normal and a month is not rare. Count the tickets that arrive in between and the cost of that gap gets uncomfortable.
Here is the thing: the questions raised in the meeting, and even the exact phrasing customers used, are already sitting in your SuperIntern transcripts and meeting summaries. In this guide, you will connect SuperIntern's MCP and Intercom's MCP to Claude, and go from "support meeting ends" to "unpublished article drafts waiting in your Intercom help center" with a single prompt, real prompt examples included.
⚠️ This article was independently compiled based on publicly available information and user feedback as of August 2026.
Table of Contents
- Today's Goal: Before / After
- How It Works: Three Roles
- Setup
- Demo 1: Batch-Create Article Drafts Right After the Support Meeting
- Demo 2: Fix Confusing Articles Using Customer Call Transcripts
- Demo 3: A Weekly Audit of Your Help Center's Blind Spots
- Tips for Day-to-Day Use
- Beyond Intercom: The Same Pattern Elsewhere
- FAQ
Today's Goal: Before / After
Before: The weekly support sync reliably surfaces the top questions and even decides "let's write this up." Then the drafting sits in a backlog. Whoever picks it up days later reconstructs the answer from meeting notes and memory, trying to recall how customers actually phrased the question. Until it ships, the team keeps typing the same reply.
After: Right after the meeting, you ask Claude once. The questions the team decided to document appear in your Intercom help center as unpublished drafts, written from the answers shared in the meeting and phrased the way customers actually asked. The only human work left is reviewing the drafts and hitting publish.
Some context first: SuperIntern is a botless desktop app. No bot joins your calls; it transcribes and summarizes meetings automatically, whether they happen on a video platform or in person. Your support syncs and customer calls are already being captured without anyone lifting a finger. The one manual step left was "turn what we learned into help articles." Today we hand that step to AI.
How It Works: Three Roles
Three participants make this workflow run.
| Role | Player | What it does |
|---|---|---|
| Meeting data | SuperIntern MCP | Serves transcripts, live transcripts, AI summaries, and meeting notes, read-only |
| Judgment and drafting | Claude (the AI client) | Picks what to document, checks for duplicate articles, writes the drafts |
| Action target | Intercom (MCP) | Searches help center articles, creates and updates drafts, searches conversations |
MCP (Model Context Protocol) is an open standard for connecting AI assistants to external tools safely. SuperIntern's MCP serves your meeting data to the AI client read-only, while Intercom's official remote MCP server handles the help center side: searching articles (search_articles), creating them (create_article), updating them (update_article), and searching past customer conversations.
In other words, the one writing to Intercom is Claude, not SuperIntern. Your SuperIntern data can never be modified through MCP, and the AI can only see meetings you can see yourself. Writes happen only on the Intercom side, and in this workflow everything is created as an unpublished draft. A human review always stands between the AI and your customers.
Setup
You need exactly two connections. Neither requires an API key; both complete with an in-browser login.
1. Connect SuperIntern MCP to Claude
In Claude, open Settings, then Connectors, choose "Add custom connector," and register the connection URL.
https://mcp.app.super-intern.com/mcp
SuperIntern's login screen opens; sign in and approve, and you are done. Plan requirements (Plus or above for personal workspaces, admin enablement on Enterprise) and setup steps for Claude Code, Cursor, and other clients are covered in our MCP setup guide.
2. Connect Intercom MCP to Claude
Intercom offers an official remote MCP server as well. Add it as a custom connector the same way and approve the OAuth prompt with your Intercom account.
https://mcp.intercom.com/mcp
If your workspace is hosted in the EU region, use https://mcp.eu.intercom.com/mcp instead. What the AI can do is bounded by your own permissions in Intercom. For client-specific details, see the Intercom documentation.
Not sure the connections took? Ask this first:
List my 3 most recent SuperIntern meetings and 3 articles from our Intercom help center
If both come back, you are ready.
Demo 1: Batch-Create Article Drafts Right After the Support Meeting
This is the workhorse. Two things matter here: always run a duplicate check against existing articles before writing anything, and pin every creation to unpublished draft state.
Get the AI summary and transcript of the "Support Weekly Sync" that just ended.
List every question we decided to turn into a help article.
For each one, search our Intercom help center and drop the ones already covered.
For the rest, draft the article body based on the answers shared in the meeting,
and create them in Intercom as unpublished drafts.
Title each article the way a customer would phrase the search,
and match the tone of our existing published articles.
Claude reads the meeting, searches your existing articles, and reports back like this:
The meeting flagged 4 questions for documentation. One (password reset) already has an article, so I skipped it and created 3 drafts:
- "How to change the name and address on your invoices": 4-step walkthrough plus a note on when changes take effect
- "Fixing garbled characters in CSV exports": includes the Excel import steps explained in the meeting
- "What happens to data when you remove a member": structured from the walkthrough Sara gave in the sync All three are unpublished drafts. Review and publish them from your Intercom article list.
Notice that the seed here is the transcript, not someone's meeting notes. In most support syncs, the most accurate answer is the one a senior teammate gave verbally, in passing. Drafting from the transcript means that explanation becomes the backbone of the article, and nobody has to reconstruct it from memory three days later.
Demo 2: Fix Confusing Articles Using Customer Call Transcripts
The same pattern improves existing articles, not just new ones. On onboarding and discovery calls, customers say some version of "I did check the help docs, but I couldn't figure it out." That sentence is a precise pointer to a weak spot in an existing article.
From today's "Acme onboarding call" transcript, pull out every place
the customer got stuck on our docs or setup steps.
For each one, search Intercom for the matching article and point out
where the article diverges from the actual screens or from where the customer struggled.
Show me your proposed edits first. Once I approve, update the article.
This prompt deliberately puts a proposal step before any update. Unlike fresh drafts, editing an existing article touches live content, so bake the sequence "propose, get human approval, then update" into the prompt itself. After you approve, Claude applies the edit through Intercom MCP.
The transcript holds two things at once: the customer's unfiltered "I did not get this," and the explanation your teammate gave on the spot to resolve it. That is why the proposed edits come out concrete, not "make it clearer" but "between steps 2 and 3, add the screen the customer was actually looking at."
Demo 3: A Weekly Audit of Your Help Center's Blind Spots
Even if you miss things meeting by meeting, a weekly cross-meeting pass catches the leftovers. Working across many meetings at once is exactly what MCP is good at.
Get all meetings from the "Customer Support" project this week and
pull out every customer question, sticking point, and request across them.
Rank the themes by how often they recurred, then search our Intercom
help center for a matching article for each theme.
Themes with no article go in a "new draft candidates" list;
themes where the article exists but contradicts what we said in meetings
go in an "update candidates" list.
For the top 3 new draft candidates, go ahead and create unpublished drafts.
The output doubles as next week's meeting agenda. Starting the sync from "here is what spiked this week, here is where the help center falls short, and the top three drafts are already written" turns the meeting from a brainstorming session into a review and decision session.
Intercom MCP can also search past customer conversations, so you can ask Claude to verify a theme against actual ticket volume: "is this really showing up in conversations, and how often?" Pairing the team's gut feel with conversation counts makes the prioritization defensible.
Tips for Day-to-Day Use
Pin creation to unpublished drafts. Make "create as an unpublished draft" a fixed phrase in your prompts. The publish decision and the publish button stay with a human. Holding that one line makes delegating the drafting feel safe.
Run the duplicate check before any write. Two articles on the same topic confuse both customers and search. Bake "search existing articles first and drop what is covered" into the prompt, as in Demo 1.
Bake your style guide into the prompt. "Title as a question," "answer first, steps second, caveats last," "match our published tone": specify the same rules every time and draft quality stabilizes. Once it feels right, save the whole prompt as a snippet.
Writes stay on the Intercom side, inside your own permissions. Nothing in SuperIntern changes through MCP. On Intercom, the AI is limited to what your account can do. If a draft misses, fix or delete it in Intercom; the source meeting data is untouched and always re-readable.
Improve accuracy at the source. The better your product terms transcribe, the better the drafts. Register feature names, screen names, and plan names in SuperIntern's custom dictionary.
Beyond Intercom: The Same Pattern Elsewhere
"SuperIntern MCP serves the data, Claude judges, another tool receives the action" extends well past help articles.
- Internal knowledge bases: for team-facing support know-how rather than customer-facing docs, see the Notion meeting database article
- Product feedback loops: routing feature requests from calls into GitHub issues follows the same shape as the bug triage article
- Instant team sharing: for pushing call highlights to Slack without waiting for an article, see the original Slack article
We will keep unpacking combinations like this, one tool at a time, with real prompts.
FAQ
Q. Is SuperIntern MCP available on the free plan?
A. No. Personal workspaces need the Plus plan or above. Team plan workspaces can use it as is, and on Enterprise it works once an admin turns on "MCP access" in workspace settings.
Q. Does SuperIntern write the articles to Intercom directly?
A. No. Claude creates and updates drafts using Intercom's MCP. SuperIntern MCP only serves meeting data read-only; SuperIntern itself never writes to external tools.
Q. Could the AI publish an article without review?
A. Every prompt in this guide specifies "create as an unpublished draft," so publishing stays a human action inside Intercom. For edits to existing articles, we also recommend fixing the "propose first, update after approval" sequence in the prompt.
Q. Can the AI modify my meeting data?
A. No. All SuperIntern MCP tools are read-only; no create, edit, or delete operations exist. Writes only happen on the Intercom side.
Q. How does the meeting recording work?
A. SuperIntern is a botless desktop app that transcribes from your device audio. It works across video platforms and in person, and no bot ever appears in the call, so customers never see an extra participant.
Q. Does this work with Zendesk or other support tools?
A. The pattern is the same. If your tool offers an MCP server or AI client connector that supports creating and updating help articles, the meeting-to-draft flow carries over. Check your tool's and your AI client's current support.
SuperIntern already handles "hear the question, answer it, keep the record" automatically. The next thing to automate is feeding what you learned back into your help center.