Plone MCP for AI. Manage CMS content and workflows from chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
Plone manages your enterprise CMS content, users, and complex workflows directly from your AI agent. You search for resources, create new pages, update user profiles, or push content through its lifecycle—all using natural conversation.
It skips the manual navigation of a traditional web UI.
What your AI can do
Create content
Creates a new page or document within Plone.
Create group
Adds a brand-new administrative group to the site.
Create user
Registers an entirely new user account for Plone.
Build new content pages or documents by calling the create_content tool.
List, create, update, or delete user accounts and administrative groups using specialized tools like list_users or update_user.
Locate specific content by its exact path or search across the entire site using get_content or search_content.
See where a piece of content sits in its life cycle and push it to the next stage with transition_workflow.
Modify details on existing pages or objects without having to download, edit, and re-upload them.
Ask an AI about this
Waiting for input…
Plone: 17 Tools for Enterprise CMS Management
These tools let you manage every aspect of a Plone site—from creating new users to moving content through its entire publishing lifecycle—all via chat commands.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Plone on VinkiusCreate Content
Creates a new page or document within Plone.
Create Group
Adds a brand-new administrative group to the site.
Create User
Registers an entirely new user account for Plone.
Delete Content
Removes content objects from the CMS.
Delete Group
Deletes an administrative group.
Delete User
Permanently removes a user account.
Get Content
Retrieves the details of one specific content object using its full path.
Get Group
Pulls all current details for a specified administrative group.
Get User
Gets the profile and status of one specific user account.
Get Workflow
Shows the current workflow state and history for any given piece of content.
List Groups
Returns a list of all existing groups on the site.
List Users
Provides a manager-level list of every user account in Plone.
Search Content
Searches for content across the site using full-text search, filtering by type or path.
Transition Workflow
Moves a piece of content to the next stage in its defined publishing workflow.
Update Content
Modifies existing content, supporting partial updates so you don't have to rewrite...
Update Group
Changes details or permissions for an established group.
Update User
Updates a user's profile details, like name changes or role adjustments.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Plone integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Plone, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Plone. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 17 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Content governance shouldn't require deep web UI knowledge.
Right now, if a content manager needs to update an article or check its status, they have to navigate through multiple menus: the Content Dashboard, then the Article Settings tab, then maybe clicking 'Version History,' and finally using specialized forms. It's tedious, slow, and easy to get lost in the hierarchy.
With this MCP Server, you just talk to your agent. You tell it what needs fixing—like, 'Check if the About Us page is ready for publication.' Your AI client runs `get_content` and `get_workflow`, gives you the status right away, and confirms what's next. It’s immediate.
Plone MCP Server: Control publishing state via chat.
Before this server, moving content from 'Draft' to 'Review' required a specific click on a status dropdown within the article view. If that button was disabled or if you needed to move it three steps later (e.g., Review -> Legal Approval -> Published), you had to follow a rigid, linear path of clicks.
Now, you just tell your agent: 'Move this content from Draft to Legal Review.' The server uses `transition_workflow` and handles the entire state change process for you. It's direct, precise, and bypasses every single intermediate click.
What your AI can actually do with this
You manage your entire enterprise CMS content—users, groups, and complex workflows—straight from your AI agent. Forget clicking through a labyrinth of web menus; you just talk to it. Your AI client acts like a site editor and admin rolled into one, giving you full control over Plone without ever touching the dashboard.
Creating and Modifying Content Objects
The create_content tool lets you build new pages or documents right in the CMS. You just tell it what you need, and boom—it gets created. Need to tweak an existing page? The update_content tool modifies content objects; it supports partial updates, so you don't gotta re-upload the whole damn thing every time you change a headline.
Advanced Content Retrieval and Search
Finding stuff is simple. If you know the exact path of a page, use get_content to grab all its details instantly. For anything else, search_content uses full-text searching across the whole site, letting you filter by type or path until you find what you're looking for. You can also pull up specifics with get_workflow, which shows the current state and history for any piece of content.
Controlling Content Workflow State
Content doesn't just appear; it goes through a process. The transition_workflow tool moves an article or page to the next stage in its defined publishing lifecycle. It handles the official status change, letting you push that draft straight into review or publication.
User and Group Administration
This is where your agent shines for site management. To get a list of every user on the system, run list_users. Need to register somebody new? Use the create_user tool to set up an account instantly. You'll also find tools for managing groups: you can use list_groups to see what groups exist, and if you need more admin muscle, create_group adds a brand-new administrative group.
If things change—maybe someone gets promoted or leaves—you modify roles with update_user or adjust permissions by running update_group. And if an account or group is dead weight? You can permanently remove it using delete_user, delete_group, or even wipe out old pages with delete_content.
Putting It All Together: A Complete Workflow Example
You wanna build a new resource center page for the marketing team? First, you use create_content. Then, you'll check who needs access by running list_users, and maybe create a specific group with create_group to limit permissions. You might need to adjust that group later; then, hit up update_group to change its read/write settings.
Once the content is drafted, you use get_workflow to verify it's ready, and when it is, you tell your agent to run transition_workflow. This sends it from 'Draft' to 'Review.' If a user needs their profile updated—say, they changed their title—you just send the command for update_user, no logins or forms required.
The system handles everything in plain English commands.
019ea5ff-25c7-718f-a477-e211185baea2 
Here's how it actually works
The bottom line is you manage complex CMS tasks using simple chat prompts, bypassing the need for manual web UI navigation entirely.
Subscribe to the server. You'll need your Plone Instance URL and a Personal Access Token.
Input those credentials into your preferred AI client (Claude, Cursor, etc.).
You start giving commands in natural language—like 'Find all documents about Q4 budget changes.'—and your agent runs the appropriate tools.
Who is this actually for?
This server is built for content governance teams and site architects. If your job involves coordinating content across multiple stages—from draft to published—you'll use this. It targets the Content Manager tired of clicking through five different menus, or the Site Admin who needs bulk data searches without writing complex database queries.
Creates news items, updates product pages, and manages publication status by using create_content and advancing content state via transition_workflow.
Adds new users or groups with create_user, runs site-wide user lists (list_users), and handles cleanup using deletion tools like delete_group.
Inspects content structure, checks metadata via get_content, or performs complex queries with search_content directly from the chat interface.
What Changes When You Connect
Find specific resources instantly. Instead of clicking through complex folder hierarchies, use search_content to query by path or metadata—you get the result list immediately in your chat window.
Control publishing state without logging into a dashboard. Use get_workflow to see if content is 'Draft' or 'Needs Review,' then run transition_workflow to push it forward, all from one command.
Handle user lifecycles fast. Need to disable an account? Run update_user or use delete_user. It’s faster and less error-prone than manually navigating the administration panel.
Build content on demand. If you need a new landing page, don't start at the root directory. Just ask your agent to run create_content, providing all necessary paths and initial details.
Eliminate data silos. You can list users with list_users and then get specific details for one person using get_user. All user governance happens in a single conversation thread.
See it in action
The Content Audit
A content manager needs to know every article published about 'Q3 Budget' but only within the /finance folder. Instead of running multiple manual searches, they prompt: 'Search for all documents containing Q3 Budget in /finance.' The agent uses search_content, and returns a list of precise document titles and paths.
The Promotion Push
A writer finishes an article. They ask the AI to check its status using get_workflow. Seeing it's still 'Pending Review,' they immediately command: 'Transition this content to Published.' The agent uses transition_workflow, moving it instantly and updating the site.
The User Cleanup
An admin notices several employees left last month. They prompt: 'List all users who haven't logged in since May.' The agent runs list_users (after verifying permissions) and identifies the accounts, allowing the admin to use delete_user immediately.
The Page Update
A product page needs a small text change. Instead of going into the web UI, they ask: 'Update the content at /products/widget-v2 with this new paragraph.' The agent uses update_content, applying only the necessary changes without risking accidental edits.
The honest tradeoffs
Trying to manage users manually
Logging into the admin panel, finding a user's profile, clicking 'Edit,' and manually changing permissions. This takes five clicks and risks forgetting a permission layer.
Just ask your agent: 'Update the group for marketing with read-only access.' The tool update_group handles all the necessary changes in one go.
Guessing content paths
Trying to use a general search when you know the exact path, which often yields too many irrelevant results and forces manual filtering.
Use get_content with the full path. If you need to find it first, run search_content, then confirm the specific object using its path.
Overwriting content entirely
When making a small fix, copying and pasting all the text into a new draft just to ensure no formatting is lost.
Use update_content and specify only the fields you need to change. This method supports partial updates, so you keep everything else intact.
When It Fits, When It Doesn't
Use this Plone MCP Server if your workflow requires multi-step governance: checking a status (get_workflow), making a state change (transition_workflow), and then updating the content itself. This server is essential when process compliance matters more than simple data entry.
Don't use it if you just need to read unstructured text or perform basic search that doesn't involve paths or metadata. If your only task is 'find documents mentioning X,' a general document retrieval tool might suffice, but for CMS-specific operations (like user management via list_users or content creation via create_content), this server is required because it understands the underlying Plone structure and rules.
Questions you might have
Can I delete a user account using the delete_user tool? +
Yes. The delete_user tool handles permanent removal of user accounts. It's an irreversible action, so always confirm the target user ID before running it.
How do I search for content using search_content? +
You provide your search query and any required filters (like a specific path or metadata type) to search_content. It runs a full-text search across the defined scope.
What is the difference between get_content and search_content? +
get_content requires you to know the exact, full path of an object. search_content, however, lets you query by keywords or metadata across a broader area.
Can I update content using update_content if I only change one paragraph? +
Yes. The update_content tool supports partial updates. You don't have to send the entire article; you just tell it what field and what new value to use.
Does list_users require special permissions? +
Yes. The listing data indicates that list_users requires a Manager role, so your AI client will only run this if the connected account has those privileges.
When I use the `transition_workflow` tool, how does it handle invalid state changes? +
The tool validates the requested transition against the content's current status. If the change is invalid or requires a step not completed (like an editor sign-off), it returns a specific error code listing the missing prerequisite action.
Does running `create_group` require permissions beyond just general administrator access? +
Yes, creating groups needs explicit Group Admin rights in Plone. Your agent must use an API token scoped specifically for group creation and modification; standard user roles won't authorize this action.
If I use the `delete_content` tool, does it also remove all related child assets or metadata? +
No, delete_content removes only the primary content object specified by path. Associated metadata or separate child assets remain intact unless you explicitly target them with a subsequent deletion command.
Can I search for specific content types like Folders or Documents? +
Yes! Use the search_content tool and provide the portal_type parameter (e.g., 'Folder' or 'Document') to filter your results.
How do I update the title or description of an existing page? +
Use the update_content tool. Provide the path to the content and a json_body containing the fields you want to change, such as {"title": "New Title"}.
Is it possible to manage user accounts through this server? +
Yes, if your credentials have sufficient permissions, you can use list_users, get_user, and create_user to manage the site's membership.
We've already built the connector for Plone. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 17 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.