
HelpGuides natively supports Model Context Protocol (MCP), which means you can connect your documentation directly to Claude as a custom connector. Once connected, Claude can search, retrieve, and reference your documentation in real time — without crawling or indexing.
Your MCP URL is unique to your HelpGuides project. It's your site's domain followed by /mcp:
To copy your exact URL, open your project, click AI Settings and look on the Model Context Protocol tab. See AI Settings.

For example, if your project is called "ACME Documentation" name the connector "ACME Documentation". This is especially useful if you have more than one project connected to Claude.

Once connected, Claude can query your documentation directly from any conversation.
Team and Enterprise plans: An owner adds the connector for the organization first. In Organization settings, then Connectors, they click Add, hover over Custom, select Web, enter the MCP URL and click Add. Each member then finds it in Customize, then Connectors, and clicks Connect.
If you use Claude Code, MCP servers are configured via the CLI rather than the connector UI. Run the following command in your terminal:
Then open a Claude Code session and run /mcp to trigger the OAuth authentication flow. Once authenticated, your HelpGuides documentation tools will be available in all Claude Code sessions.
To verify the server was added successfully:
By default, the server is only available in the current project directory. Add --scope user to make it available in all your projects:
Claude Desktop uses the connectors on your Claude account. Add HelpGuides as a custom connector using the steps above and it's available in Claude Desktop too, with nothing else to configure.
The claude_desktop_config.json file is for local MCP servers, and Claude Desktop won't connect to a remote URL placed in it directly. If you do need to configure HelpGuides in the file, run it through the mcp-remote bridge, which needs Node.js and signs you in with OAuth on first use:
The config file is located at:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonSave the file and restart Claude Desktop.
Claude will now have access to your documentation for the duration of that conversation.
Once connected, Claude can use every MCP tool your HelpGuides project exposes, including:
This lets you search for existing coverage, draft new articles and update content without leaving your conversation. For every tool and its parameters, see Model Context Protocol Endpoints.
Once your connector is enabled, here are some prompts to get started:
Claude will search your docs, draft content, and push updates as drafts for your review — you always have the final say before anything is published.
To disconnect HelpGuides from Claude at any time:
claude mcp remove helpguides in your terminal.helpguides entry from claude_desktop_config.json and restart Claude Desktop.You can reconnect at any time by following the setup steps above. To cut off every AI assistant at once, turn off Enable Model Context Protocol in AI Settings.
Re-authenticate by clicking Connect next to the connector in Customize, then Connectors, or run /mcp in Claude Code to start the OAuth flow again.
MCP connectors are loaded at session start. Start a new conversation and enable the connector from the + menu.
Make sure Enable Model Context Protocol is on in AI Settings; when it's off, the MCP URL doesn't respond. Sign in to HelpGuides with an account that has access to the project, and click Approve. If Claude reports that the token isn't authorized for this project, you approved access with a different HelpGuides account: remove the connector and connect again with the right one. Contact support if the problem continues.
For more on how HelpGuides implements MCP, see Model Context Protocol and Using LLMS.txt.