HelpCenter.io for AI agents

Let AI agents build and run your help center.

Connect Claude, ChatGPT or your own agent. It moves your articles in, designs the help center around your brand, keeps every answer current and puts it inside your product. Your customers get the same right answer wherever they ask.

The MCP server is included in Growth and Catalyst, and in their 14-day trials. No credit card needed.

The HelpCenter.io MCP server, in 50 seconds.

Works where you already work

  • Claude

    The HelpCenter.io plugin in Claude's directory, with six skills for your help center. On the web, in Claude Desktop and in Claude Code.

    Add the plugin
  • ChatGPT

    The HelpCenter.io plugin in ChatGPT's Plugin Directory, with five skills for your help center.

    Add the plugin
  • Your own agent

    Any MCP client that signs in with OAuth, or an API key from your help center's Settings.

    See the setup
  • Your customers' assistants

    Every public help center answers AI assistants at its own /mcp address, read-only, on every plan.

    How it works
1 · Move in

Bring every article over in one conversation.

Point your agent at the help center you have now, an export, or the docs in your repository. It writes them into HelpCenter.io 50 at a time, in the categories you already use, and copies their images across so nothing still loads from your old vendor.

Each article keeps its old address as a stable ID, so a run that stops halfway is simply sent again: what exists is updated, what is missing is created, nothing is duplicated.

Rather have people do it? Our team moves you over for free: free migration.

Northwind help center Example
  1. You: Move our old help center at help.northwind.example over. Keep everything unpublished until I have looked.

  2. Tool call: helpcenter_create_category ×6, the categories it found

  3. Tool call: helpcenter_bulk_create_articles ×3, 124 articles, saved as drafts

  4. Assistant: 124 articles are in, as drafts, in the six categories you had, and their 312 images now load from your help center. Two of them link to pages that no longer exist:

    • Exporting invoices Check a link
    • Two-step sign-in Check a link
An example on Northwind, a fictional help center. The numbers are illustrative; the tools are the real ones your agent calls.
2 · Design it

A help center that looks like your brand, from one paragraph.

Describe your product and the feel you want. Your agent picks a starting theme, sets the colours for light and dark mode, the type and the layout of every page, checks the contrast, and leaves it all in the Template Editor's draft for you to preview. Visitors see nothing until it is published.

Each of these three started as the same stock help center and the brief beside it. A fresh Claude session with the HelpCenter.io plugin built and published each one in about four minutes. No one touched the design by hand.

One of these runs, recorded and sped up: Claude Code with the HelpCenter.io plugin turns the Pebble brief into a published help center, 3 minutes 33 seconds from brief to live.

Every kind of design edit is a tool of its own, from colours and fonts to layouts, components and custom CSS, so the assistant asks before the exact change it is about to make. Every published design can be restored.

Rather not write a brief? Paste your website's address into the AI theming agent and get a help center that already looks like you.
3 · Keep it current

Keep every answer current, without the busywork.

Tell your agent what changed and it finds every article that mentions it. On Catalyst, it stages the edits to live articles privately, gathers them into one release with any new drafts, and schedules it for launch day. Readers see the old answers until then, and the new ones the minute it ships.

  • Write and translate Draft new articles and fill in every language your help center offers.
  • Staged edits Change a live article privately, then publish or discard it. Catalyst
  • Change sets Release edits and drafts together, now or on launch day. Catalyst, early preview
  • Version history Restore any earlier published version of an article. Catalyst
  • Editorial notes Answer and resolve the notes your team leaves on articles.
  • Reader comments Moderate comments and reply as yourself.
Northwind help center Example
  1. You: Our Starter plan becomes Basic on 1 November. Update everything, but nothing should change before then.

  2. Tool call: helpcenter_search_articles 9 articles mention Starter

  3. Tool call: helpcenter_stage_article_changes ×9, readers see nothing yet

  4. Tool call: helpcenter_create_change_set “Plan rename”

  5. Tool call: helpcenter_add_change_set_items 9 staged edits

  6. Tool call: helpcenter_publish_change_set scheduled for 1 November, 09:00

  7. Assistant: All nine edits are staged in the change set Plan rename, scheduled for 1 November at 09:00. You can read each one in the dashboard before then, or cancel the schedule.

    • Compare plans Staged
    • Upgrade or downgrade Staged
An example on Northwind, a fictional help center. Staged edits and change sets need Catalyst; change sets are in early preview.
4 · Find the gaps

Find what customers could not, and fix it the same day.

Every search that comes back empty is a customer telling you what to write next, and every article with views and poor ratings is one telling you what to fix. Your agent reads both, ranked by demand, checks what you already have so a near miss gets improved instead of duplicated, and drafts the rest for your review.

Search data is aggregated daily: your agent sees questions and demand, never a trail of individual visitors.

Northwind help center Example
  1. You: Which articles should we fix first, and what is missing?

  2. Tool call: helpcenter_get_content_performance views and ratings, last 30 days

  3. Tool call: helpcenter_get_search_queries searches that found nothing

  4. Assistant: “Connect your bank” has 2,140 views and only 38% found it helpful: the screenshots show the old settings page. And 41 people searched for “pause instead of cancel” and found nothing. I can fix the first and draft the second.

  5. You: Do both.

  6. Tool call: helpcenter_update_article new steps and screenshots

  7. Tool call: helpcenter_create_article saved as a draft

  8. Assistant: Done. The bank article is updated, and the new one is waiting for your review:

    • Pause your plan instead of cancelling Draft
An example on Northwind, a fictional help center. The numbers are illustrative; the tools are the real ones your agent calls.
A real review, recorded and sped up: Claude Code with the HelpCenter.io plugin reads Northwind's failed searches, drafts what was missing from the release notes and schedules it all in one change set for launch day, a minute from brief to scheduled. Nothing goes live before then.
5 · Put it in your product

Put your help center inside your product, in one pull request.

Open Claude Code in your app's repository and ask for help where your customers need it. It adds the HelpCenter.io widget the way your framework expects, follows your routes in a single-page app, opens the right article from your own buttons, and drops FAQ sections onto the pages that need them.

It sets up the HelpCenter.io side as well, through the connector: it reads your install code, creates the FAQ sections, and adds your site to the websites the widget may run on once you say yes.

For signed-in users it writes the endpoint that signs them in with single sign-on, and keeps the shared secret in your server's environment, where no agent ever reads it.

The widget is on every plan; AI answers inside it need Catalyst or the AI add-on, and single sign-on needs Catalyst. More about the widget.

northwind-app · Claude Code Example

You: Add the HelpCenter.io widget to our app, open Getting started from the Help menu, and sign our users in to it.

  • +14 app/layout.tsx loads the widget
  • +31 app/api/helpcenter-token/route.ts signs the sign-in token
  • +6 components/HelpMenu.tsx opens the article
// app/layout.tsx
<Script id="helpcenter-widget" strategy="afterInteractive">
  {`window.hcOptions = { app_id: "YOUR_APP_ID" };`}
</Script>
<Script src="https://helpcenter.io/js/init.js" strategy="afterInteractive" />

Assistant: The widget loads on every page and follows route changes. Signed-in users get a short-lived token signed on your server from HELPCENTER_SSO_SECRET, which stays in your environment.

An example in a fictional Next.js app. The snippet is the widget's real one; Claude reads your app id through the connector, and it is also under Embeddables in your dashboard.
A real run, recorded and sped up: Claude Code with the HelpCenter.io plugin adds the widget, single sign-on and an FAQ section to Northwind's Partner Hub, 2 minutes 41 seconds from request to done.
6 · Answer everywhere

One knowledge base. Every place a customer asks.

Everything your agents write lands in one place, and everything that answers your customers reads from it. Fix an answer once and every one of these shows the new one.

Your help center

The articles your team and your agents write, in every language you offer.

  • Your team
  • Claude
  • ChatGPT
  • Your own agent

Your help center site

Search and every article, on your own domain or under a folder of your website.

The widget in your product

Answers on the very page the question comes from.

FAQ sections

Live answers on pricing, checkout and landing pages.

Your support team's assistant

Claude or ChatGPT answers your team from your articles, with links.

Your customers' AI assistants

Read-only MCP at your help center's own /mcp, on every plan.

AI search and crawlers

Clean Markdown on every page, with llms.txt and ai.txt.

You stay in control

Agents do the work. You decide what ships.

Access is granted help center by help center, on our own consent screen, so your password never reaches the assistant. You can take it back whenever you like.

  • You choose the help centers

    Agents sign in through HelpCenter.io over OAuth 2.1. You pick which help centers a connection reaches and see every permission it asks for before you allow it.

  • Asked before it changes anything

    Every tool that edits, publishes, discards, restores or deletes is labelled destructive, so clients like Claude ask you before they run it.

  • Drafts until you publish

    New articles can be saved as drafts, design changes stay in the Template Editor's draft, and on Catalyst edits to live articles can be staged.

  • Take it back any time

    Change what a connection reaches, or disconnect it, in Account → Connected Apps. Delete an API key and it stops working.

  • Reader privacy by default

    Reader email addresses are withheld unless a connection with write access asks for them, IP addresses are never exposed, and search data is aggregated daily.

  • Public means published

    Your customers' assistants only ever see what any visitor could read: published, public articles. Private categories and internal notes never reach them.

Prompts to start with

Say it the way you would say it to a teammate.

Copy one into Claude or ChatGPT once your help center is connected, and change the details to yours.

  • Move in

    “Move every article from our current help center at help.example.com into HelpCenter.io as drafts, in the same categories.”

  • Design it

    “Redesign our help center to match our brand: we are a payments app for startups, and it should feel dark, premium and precise. Leave it as a draft for me to review.”

  • Keep it current

    “Our Starter plan is now called Basic. Find every article that mentions Starter and stage the updates for my review.”

  • Find the gaps

    “What did customers search for last month and not find? Draft articles for the top three.”

  • Put it in your product

    “Add the HelpCenter.io widget to this app, and open the Getting started article from our Help menu.”

  • Translate

    “Translate our five most viewed articles into German and Spanish.”

For agencies

Every client's help center, from one conversation.

One connection can reach every help center you give it. Your agent names the help center on each call instead of guessing, so you can turn a new client's brief into a branded help center, then check last month's gaps across all of them.

Availability

Included in Growth and Catalyst.

No add-on and no charge per tool call. The MCP server comes with the plan, and your 14-day trial includes it. Your customers' assistants can read your public help center on every plan.

Growth

$119 /mo, billed annually

or $149 month to month

  • Move in, design, write, translate and find the gaps with Claude, ChatGPT or your own agent
  • Up to 10 teammates
  • Not included: Staged changes, version history and change sets, which need Catalyst
Start a Growth trial

Catalyst

With staged changes

$179 /mo, billed annually

or $199 month to month

  • Everything in Growth, plus staged changes and version history, and change sets in early preview
  • Unlimited teammates
  • AI answers in your help center and widget, translations and single sign-on
Start a Catalyst trial

Bootstrap and older plans priced below Growth do not include the MCP server. Compare every plan.

FAQ

Questions, answered.

Setting one up? Connect Claude or your own agent, or add the ChatGPT plugin.

What can an AI agent do with my help center?

Through the HelpCenter.io MCP server, an agent can do most of the day-to-day work on a help center: search and read articles, write, translate and import them, organize categories, upload images, restyle the help center in the Template Editor's draft, read search and content analytics, and answer reader comments and editorial notes. That is 77 tools, listed on the MCP server page, each inside the permissions you approve.

Which AI assistants work with it?

Claude on the web, Claude Desktop and Claude Code, ChatGPT through the HelpCenter.io plugin (see the ChatGPT plugin), and any MCP client that supports remote servers with OAuth sign-in. An agent you build yourself can use an API key from Settings → API Keys instead.

Do I need to write code?

No. Moving in, designing, writing and finding gaps all happen in a conversation with Claude or ChatGPT. Code only comes into it when you put the help center inside your own product, and that is the part Claude Code does in your repository for you.

Can the agent publish without me?

Only if you give it write access and ask it to. Ask for drafts and publishing stays your call. Design changes stay in the Template Editor's draft until the design is published, and on Catalyst edits to live articles can be staged for your team. Every tool that edits, publishes, discards, restores or deletes is labelled destructive, so clients like Claude ask you before running it.

Which plans include it?

The MCP server is included in Growth and Catalyst, and in the 14-day trials of both, with no add-on and no charge per tool call. Staged changes and version history need Catalyst. The read-only /mcp address your customers' assistants use is on every plan.

What do my customers' AI assistants see?

Every public help center answers MCP at its own address, for example help.example.com/mcp, so an assistant your customer uses can search your articles and quote them. It is read-only and anonymous, and it only ever sees what any visitor could read: published, public articles. You can switch it off in your help center's Settings.

Your help center, with an agent on the team.

Start a 14-day trial, connect Claude or ChatGPT, and give it the first job. No credit card needed.