Rovo and AI tools
PageCycle has 24 tools that cover its page, board and settings screens, and each acts with exactly its user's permissions. They work in Rovo, in agents you build in Rovo Studio, and in Claude, Codex, Cursor and other MCP clients.
In Rovo
PageCycle adds itself to Rovo as an agent called PageCycle. Open Rovo chat, pick PageCycle from the agent list and ask in plain words:
- "Which pages in our Product space need my attention?"
- "Is this page approved and current?"
- "What happened to the Search filters spec?"
- "Approve it again, next review in 6 months."
- "Send the Integrations roadmap back to Maya. It needs the Q1 partners."
Every tool runs as you: your groups, your edit permission, a comment where the move needs one. Confluence's page history names you, and the move is recorded in the page's History with your name, with Rovo as the channel. A space admin's changes that touch many pages (renaming a status, moving pages out of one, turning PageCycle on) leave pages you can't edit as they are. The preview says how many before you confirm, the answer names the ones you can view, and a page you can't view is never named. In Rovo, a move also shows Rovo's review card first. If a move isn't allowed, the agent quotes the reason and nothing changes.
If the page's Confluence status was removed (that is how a Confluence approval starts), the agent asks before moving it, because the move can end an approval. Nothing changes until you say yes.
In Rovo Studio, add PageCycle's tools to your own agent as you would any Atlassian tool.
Name a page by its link, its exact title (a page you can view, unique among those), or say "this page" while you have it open. Name a space by its key or its exact name.
The tools
Tool names are exact and case-sensitive.
| Tool | What it does | Who can use it |
|---|---|---|
| getPagecyclePageStatus | A page's status, who moved it there and when, the version approved, its next review, and the moves you can make | Anyone who can view the page |
| movePagecyclePage | Moves a page to another status, with a comment and a next review | People who can edit the page, within the move's groups |
| getPagecyclePageHistory | Every move with who, when and why, and whether the page changed since sign-off | Anyone who can view the page |
| setPagecycleReviewDate | Sets or clears the next review: a date, or "in 6 months" | People who can edit the page |
| getPagecycleSpaceSummary | Pages in each status, and the pages that need attention | Anyone who can view the space |
| listPagecyclePages | Pages by status, overdue for review, or stuck for some days, with owner and version | Anyone who can view the space |
| getPagecycleSpaceHistory | A space's History, by person, status or dates | Anyone who can view the space |
| listPagecycleSpaces | The spaces that use PageCycle, with their counts | Anyone |
| getPagecycleWorkflow | A space's statuses, moves and who may make them | Anyone who can view the space |
| getPagecycleAutomations | A space's automations, and for space admins whether they run well | Anyone who can view the space |
| addPagecycleStatus | Adds a status after an existing one | Space admins |
| updatePagecycleStatus | Renames, recolors or changes the kind of a status, and updates every page that has it | Space admins |
| removePagecycleStatus | Removes a status after moving its pages to another one | Space admins |
| addPagecycleMove | Adds a move between two statuses | Space admins |
| updatePagecycleMove | Changes a move's name, groups or comment rule | Space admins |
| removePagecycleMove | Removes a move | Space admins |
| setPagecycleWorkflowDefaults | Sets "Pages start in" and "New pages get" | Space admins |
| addPagecycleAutomation | Adds an automation, written as when, if and then | Space admins |
| updatePagecycleAutomation | Changes an automation, switches it on or off, or reorders it | Space admins |
| removePagecycleAutomation | Removes an automation | Space admins |
| updatePagecycleSpaceSettings | What happens when someone breaks the workflow, and how long History is kept | Space admins |
| enablePagecycleSpace | Turns PageCycle on in a space: scan, map statuses, import | Space admins |
| disablePagecycleSpace | Turns PageCycle off in a space; History is kept | Space admins |
| getPagecycleOperation | Where a long change stands, and its next part | Space admins |
Pages you can't view never appear in a list, a count or a History line.
Changing a space's settings
Every change to a space's settings shows you a preview first. The agent tells you what will change and asks; nothing changes until you say yes, and only you can confirm your own preview. In Rovo you also confirm each step on Rovo's own review card. A preview expires after 15 minutes, and if someone changes the space's settings in the meantime the agent shows you a fresh one. Page counts in a preview include every page in the space, as the settings screen's do, and a page you can't view is never named.
Removing or renaming a status that many pages hold, and turning PageCycle on in a large space, can take more than one step. The agent tells you how far it got and carries on.
An automation is written in three parts:
- when: "a page is edited", "moved to Approved", "moved to any status" or "the review date passes"
- if (optional): "status is In review or Draft", "kind is signed off", "mover in group pagecycle-approvers", "label policy"
- then: "move to Review due", "review in 180 days", "add label checked", comment "Please check this page"
From Claude, Codex or Cursor
PageCycle's tools work in any MCP client, through Atlassian's MCP server. A site or org admin switches this on once; then each person signs in.
- A site or org admin opens Atlassian Administration › Connected apps › PageCycle and allows external MCP clients.
- In your AI client, add the MCP server
https://mcp.atlassian.com/forge/<PageCycle app id>. Your site admin sees the app id in Connected apps. - Sign in with your Atlassian account when the client asks. The tools act as you, with exactly your Confluence permissions.
Atlassian marks external AI clients as experimental. Keep your client asking before it runs a tool: a settings change applies when its confirmation comes back, and the client's approval is how you see it first.
From your own scripts
Every tool is also an HTTPS route, acting as the person who signed in, with the same rules and the same words. See the REST API.