Once the Published Docs MCP Server is enabled, everything a reader needs to connect is already in your portal — the Connect with MCP block on every page gives them the endpoint URL and ready-to-run commands. What is missing is the reason to look there at all. Most readers do not know the option exists.
A short page in your own documentation closes that gap. This topic gives you a template to adapt.
Template
Copy the following into a topic in your own documentation and adjust the product name and tone to match your style:
Use our documentation with your AI agent
Our documentation is available to AI agents over the Model Context Protocol (MCP). Connect your agent once, and you can ask it questions about our product without leaving your own tools — it answers from this documentation rather than from whatever it remembers.
To connect, open any page in our documentation, click Copy page, and use the Connect with MCP block. You can copy the connection details for a supported agent or the server URL address to configure an agent yourself.
Access is read-only and covers our public documentation only.
| As an alternative way to inform your readers, you can disable the Connect with MCP block via the Reader interface settings and provide the MCP server URL directly in your docs. The MCP server URL can be obtained in the AI integrations → MCP server settings section. |
What Not to Include
We recommend keeping the page short and pointing readers to the Connect with MCP block rather than reproducing what it contains. In particular, we recommend not listing the supported agents or the connection commands in your own text. The block is generated by the portal and stays correct as the list of supported agents grows; a copy in your topic does not, and a reader who follows an outdated command will conclude that the feature is broken.
For the same reason, avoid documenting agent-specific setup. Configuring Claude, Cursor, or any other agent is that vendor's subject; it changes on their schedule, and readers who use an agent already know their own tool.
Where to Put It
Readers look for this in the same places they look for other ways of consuming your documentation, so a getting-started section or a page about using the documentation itself usually works better than a dedicated section of its own. If you publish release notes, mentioning the option once when you turn it on reaches the readers who are already following your updates.