You want to point Claude at your Intercom help center and say rewrite every article in the new brand voice, cap each intro at two sentences, and fix the ones that still mention the old plan names. What stops you is who reads it. These articles are in front of customers, and most ways of wiring AI to a help center republish straight to it, so one bad pass ships to every article before you can read it.
Scratch changes where the edit happens. Claude does 99% of the work, reading and rewriting every article as files on your laptop. The last 1%, deciding what actually publishes, stays with you. Nothing goes live until you have seen the change as a diff and approved it.
How it works
- Scratch pulls your help center into files. Every article comes down to a folder on your laptop, one file each, with its title, body, and placement.
- Claude edits the articles. Open the folder in the Claude desktop app. Try a prompt on one article in Chat, then let Cowork or Code run it across the whole center. Rewrite every article in the new brand voice and cap each intro at two sentences. Claude edits the files, never the live help center.
- You review every diff and publish. Scratch shows each change next to the original, word by word. Approve what ships, and Scratch writes only those articles back through the Intercom API.
What people use it for
Most people arrive with a help center that has fallen behind the product, because updating it by hand means opening every article one at a time.
- Run a tone pass across every article after a brand or product update.
- Cap long intros and tighten structure so the answer comes first.
- Fix articles that still reference old plan names, prices, or features.
- Reorganize articles into the right collections and sections.
- Clean up content migrated in from another knowledge base.
Pull a few articles to feel the loop, then point Claude at the whole help center.
Why not an MCP server?
An Intercom MCP server or app hands Claude a direct line to your live help center. The publish button is wired straight in, so one bad pass republishes every article at once, in front of your customers.
Scratch gives Claude the same full read and write access, but against a local copy. The publish step is pulled out and handed to you. Claude can change anything; only you can ship it. On a help center your customers actually read, that is the difference that matters.
What Claude edits in Intercom
- Help center article title, body, and description
- Article state, draft or published
- Article hierarchy, parent collection or section
- Collection name, description, and icon
- Translated content
Conversations are pulled for context but stay read-only, and validators check length caps and required fields so an article never publishes broken. For the full picture, see Scratch for Intercom.
Questions people ask
Is this an MCP server or an Intercom app?
No. An MCP or app gives Claude the publish button straight to your help center. Scratch does not. Claude gets the same access, but publishing is a separate step you approve, one article at a time.
Will Claude touch my customer conversations?
No. Conversations are pulled read-only for context. Claude edits help center articles and collections, nothing in your inbox.
Can it keep my translated articles in sync?
Yes. Translated content is in scope, so Claude can carry an edit through each language you maintain, and you review every version as its own diff before it ships.
Can I undo a change after it ships?
Yes. Every published article is reversible from Scratch, per row. The original sits next to the rewrite until you decide which one stays.
Why not just edit in Intercom or run a script?
Editing in Intercom is one article at a time, and a script writes straight to the live help center with no per-article approval. Scratch puts an agent on the edit, so a whole refresh happens in one pass, and holds every change as a word-level diff you approve before anything publishes.
Can it handle the whole help center at once?
Yes, that is the use case. Pull a few articles to feel the flow, then pull the whole center. Cowork and Code are built for help-center-scale jobs.
Do I need to be technical?
No. Install Scratch, connect Intercom, point Claude at the folder, and approve the diffs.
See it on your own help center
The fastest way to trust it is to watch it run on your articles. See it run on your Intercom help center →, or download Scratch free and run the first pass yourself.