Integrations
Pageloop MCP
Use Pageloop from your AI tool to find documentation, propose changes, and review work.
Pageloop MCP
Pageloop MCP lets you use Pageloop from Claude, Cursor, and other AI tools that support the Model Context Protocol (MCP). You can ask your tool to find documentation, prepare updates, and help with your team's review work without leaving the conversation.
What you can do
Choose access to match the work you want your tool to do. The permission names below match the sign-in screen; see Choose what your AI tool can do for the full list and role limits.
| Area | Example requests | Access needed | Related guides |
|---|---|---|---|
| Read and search docs | “List our documentation pages.” “Find the articles about setting up a workspace.” | Read only | Working in the Knowledge Base |
| Draft and propose changes | “Draft an update to our setup guide with these steps.” “Prepare a troubleshooting article for review, without publishing it.” | Propose changes | Change Sets |
| Review Inbox items | “Show me the Inbox items waiting for my review.” “Summarize the changes in this item.” “Accept the wording change I selected and send the other suggestion back.” | Propose changes | Use the Inbox, Review an Inbox item |
| Start Pageloop's docs agent | “Ask Pageloop to document this product change.” “Have Pageloop check our onboarding guides against these release details.” | Custom → Run the docs agent | Where Inbox items come from |
| Manage workflows | “Pause our weekly documentation review workflow.” “Create a draft workflow to check for stale pages each month.” | Custom → Manage workflows | Workflows |
| Manage the workspace: team, templates and AI style, screenshot logins | “Invite a teammate as a Contributor.” “Create a template from our onboarding articles and set these product terms in our AI style.” “Test our saved screenshot login.” | Custom → Manage the team, Change settings, or Manage screenshot logins, for the task | Manage members, Style and Templates, Set up automated screenshots |
How changes stay safe
- Documentation edits are drafts by default. Your tool's edits land in a change set for review, not on your live site. Full access, or Custom with Publish live, is the exception: it can publish live without a person approving each change.
- You choose the access. Select the knowledge bases and permissions your tool needs. The connection cannot do more than your Pageloop role allows.
- You can disconnect at any time. End access in Pageloop's Connections page. Clearing sign-in inside the tool does not remove the Pageloop connection.
Permissions to manage workflows, the team, templates, AI style, or screenshot logins let your tool change those workspace settings directly. Those actions do not create documentation drafts.
Before you start
- Use a live knowledge base that Pageloop hosts: a docs site. Help centers connected through Intercom, Zendesk, Freshdesk, or Help Scout are not supported yet.
- Have access to the workspace in Pageloop. Your role sets the most access you can give a tool, and the connection follows role changes automatically.
- Use an AI tool that supports remote HTTP MCP servers with browser sign-in.

