PagibleAI exposes CMS operations through the Model Context Protocol. Supported clients can search content, create drafts, manage media, move pages, control frontend access and run AI tools.
Every request uses the authenticated user's permissions and tenant. Content changes remain drafts until they are published, while frontend access changes take effect immediately.
add-* and save-* tools create drafts.get-* tools return a latest_id; pass it to the matching save-* tool.publish-* tools make a draft public now or at a scheduled time.drop-* tools soft-delete content; restore-* tools recover retained items.set-page-access changes frontend access immediately and is not part of page versioning.The MCP server exposes only the tools allowed by the user's cmsperms. A user with page:view can read pages but cannot publish without page:publish. AI and file-editing tools may require more than one permission.
All queries and changes stay within the authenticated user's tenant. Use a separate account for each person or integration so audit history records the correct identity. Authorization and Permissions covers roles and individual permissions.
get-locales and get-schemas.search-pages, then read it with get-page.add-page, or update it with save-page and latest_id.publish-page.Access changes use set-page-access and take effect as soon as the call succeeds.
The pagible-mcp package provides 30 tools for discovery, pages, shared elements, files and frontend access. Installing and configuring pagible-ai adds 11 tools for text, media analysis and image work.
The client may show fewer tools when the current user lacks the required permissions. The PagibleAI MCP Tools Reference lists every tool.