This article explains from scratch what the HelpKit MCP server is, shows what an AI assistant can actually do with your help center, and gets you to the point where you can connect your own tool. No technical background needed, and there is nothing to install. If you have seen "MCP" in your HelpKit dashboard and were not quite sure how to get started, this is the article for you.
MCP in one sentence
MCP stands for Model Context Protocol. It is an open standard that lets an AI assistant reach out to an outside service and work with live data from it.
The easiest way to picture it is a USB port for AI assistants. Before MCP, every app had to be wired into every assistant separately, and mostly that never happened. With MCP, a service publishes one port and any assistant that speaks the standard can plug straight into it.
Claude, ChatGPT, Cursor, VS Code, Claude Code and Codex all speak it. So does HelpKit.
What your assistant can do with your help center
Once it is connected, your assistant works on your real help center instead of guessing. It can:
- Find the gaps. It reads what visitors typed into your search bar and found nothing for, and the questions your AI chatbot answered badly.
- Spot the weak articles. It surfaces your lowest rated articles, reads them, and tells you what is actually wrong with them.
- Write. It drafts new articles, and whole new categories, straight into your Notion. Always unpublished, always ready for you to review.
- Keep things current. It updates existing articles, fixes their order, features one on your home page, and syncs your help center once you are happy.
So instead of opening your analytics, exporting the searches, pasting them somewhere and explaining your product from scratch, you just ask:
What did visitors search for last month that we have no article for? Group them by theme and tell me which three gaps are worth writing first.
The real advantage is combination. In the same conversation you can paste your release notes, a support thread or a spec, and ask for an article that matches your existing docs, in your voice, filed in the right category. That is the part a dashboard cannot do for you.
What you need
An active HelpKit project. MCP is included on every plan, and during your trial, at no extra charge. Nothing is metered and there is nothing to buy. Each project needs its own live subscription, and if one lapses its connection stops working until it is renewed.
An AI tool that speaks MCP. Claude, ChatGPT, Claude Code, Codex, Cursor and VS Code all do, and so do most others.
Your Notion pages shared with HelpKit. This is the one people miss. Your help center lives in Notion, so anything your assistant writes has to be written there, which means HelpKit needs access to your pages. Without it your assistant can still read your analytics and your live articles, but every attempt to draft or edit is politely refused. It takes about a minute to set up and it is worth doing before anything else.
The server address
Whatever tool you use, it will ask you for a server address. This is it:
It is the same for everyone and it never changes. You will also find it, ready to copy, in your dashboard under Account Settings → MCP.
How connecting works
Every connection follows the same three beats, whichever tool you use.
Step 1: Add the server
In your AI tool, find where it adds connectors or MCP servers and paste the address above. Name it HelpKit.
Step 2: Approve it in your browser
Your tool opens a HelpKit page in your browser. Sign in if you are not already, then click Approve.
This is the same idea as "Sign in with Google". Your AI tool never sees your HelpKit password, and you can disconnect it from your dashboard at any time.
Step 3: Ask your first question
Ask your assistant:
Check my HelpKit setup status.
That single question does a lot of work. It confirms the connection, names the projects your assistant can reach, and tells you whether Notion is connected and what your assistant is allowed to change. If something is missing, it says so in plain words.
Where to find all of this in your dashboard
Click MCP in the top bar, or open the account menu at the top right, go to Account & Billing settings, and pick the MCP tab. Everything lives there: the server address, a setup guide for each tool, the connections you have approved, and the switch that decides what your assistant may change.
Now pick your tool
The exact clicks differ per tool, so we wrote one short article for each.
- Connect HelpKit to Claude. Desktop, web and mobile. The most common setup, and the one that turns HelpKit on everywhere you use Claude.
- Connect HelpKit to Claude Code. One terminal command.
- Connect HelpKit to ChatGPT. On Plus and above.
- Connect HelpKit to Cursor. One-click install.
- Connect HelpKit to VS Code. One-click install.
- Connect HelpKit to Codex. Uses a key rather than the browser sign-in.
- Connect HelpKit to any other MCP client. Windsurf, Zed, the Gemini CLI and friends.
If a connection does not behave, this covers the messages you might see and what each one means:
Nothing reaches your visitors by accident
New articles are always created as drafts with Published unchecked, and a draft is invisible to your readers. Everything a visitor could notice, such as publishing, editing a live article, renaming a category or running a sync, sits behind a separate switch that you control per project. It is off unless you turn it on.
Once you are connected, this is where to look next for the prompts worth using:
Powered by