What MCP is in plain English, what an AI assistant can do with your help center, and the three things you need before you connect one.
Why your AI assistant needs access to your Notion pages, how to check whether you already gave it, and the one minute setup if you have not.
The prompts worth stealing, everything your assistant can look up about your help center, and the few things it can actually change.
What your AI assistant is allowed to touch, how the write and sync access switch changes that, and how to disconnect a tool you no longer use.
How your assistant picks the right help center, why every project and every language needs its own Notion access, and how to point it at the right one.
The messages you might see when connecting HelpKit to your AI tool, what each one actually means, and how to get past it.
Add HelpKit as a connector in Claude for desktop, web and mobile, so your help center is available everywhere you use Claude.
One terminal command adds HelpKit to Claude Code across every project, then you sign in from inside the tool itself.
Add HelpKit to ChatGPT on Plus, Pro, Business or Enterprise, then switch it on inside a chat so it can work on your help center.
Install HelpKit in Cursor with one click from your dashboard, or add the server to your Cursor config by hand.
Open the VS Code installer with the HelpKit server already filled in, or add it to your mcp.json by hand.
Codex uses a HelpKit key rather than the browser sign-in. Paste one prompt and it writes its own configuration.
Windsurf, Zed, the Gemini CLI and anything else that speaks MCP over HTTP, with the standard config and the key fallback.