Summary:
The Rovo MCP Server supports pages and blog posts (create, update, move) but has no tooling for Confluence folders. AI clients can create a page and move it under a folder that already exists, but they cannot create a folder, read a folder, or list a folder's contents. This is the single biggest gap for AI-assisted Confluence organization today.
Current behavior:
- Pages and blog posts: full create, update, and move support.
- Folders: no create, no read, no list. Folders must be provided or created manually before the MCP can place pages into them.
Desired behavior:
Treat folders as a first-class content type alongside pages:
- Create a folder (with parent and space context).
- Read folder metadata.
- List the contents of a folder.
- Move pages and folders into a folder.
Use cases this would unblock:
- Standing up a new space structure from a template or plan without a human pre-building every folder.
- Bulk reorganization and cleanup of an existing space (the most common reason teams reach for AI here).
- Auto-publishing structured documentation (for example, incident postmortems or product docs) into the correct folder hierarchy as part of a workflow.
- Mapping and auditing space structure, which requires reading folders, not just pages.
Current workaround:
Create folders manually in the Confluence UI first, then have the MCP create and move pages inside them. Functional for one-off cases, but it does not scale and undercuts the value of AI-assisted organization.
Note: Confluence already supports folders in the UI and via its REST API, so the gap is specifically in the MCP tool surface rather than in Confluence itself.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.