Confluence page creation via Atlassian MCP (Rovo) returns 404, but REST works fine — anyone else seeing this?

Rovo
1

Hi all,

I’ve been experimenting with creating Confluence pages programmatically via the Atlassian MCP (Rovo integration used through ChatGPT).

I ran into something surprising and wanted to see if others have observed the same behavior.

Scenario

Goal: Create a draft child Confluence page under an existing page.

Using MCP tool:

createConfluencePage

With:

  • Valid cloudId

  • Valid spaceId

  • Valid parentId

  • write:page:confluence scope present

Result:

404 NOT_FOUND

Control Experiments

1. Direct Confluence REST v2 (works)

POST https://{site}.atlassian.net/wiki/api/v2/pages

Draft page successfully created.

2. Global API route (also works)

POST https://api.atlassian.com/ex/confluence/{cloudId}/wiki/api/v2/pages

Also successful.

3. MCP createJiraIssue

Works fine.

4. MCP Confluence reads

Also work fine.

Conclusion

Confluence page creation works via REST but fails via MCP.

That suggests the issue is in the MCP/Rovo bridge layer, not permissions or plan tier.

Has anyone successfully created Confluence pages via MCP?

If so:

  • Are you on Free, Standard or Premium tier?

  • Are you using markdown or storage format?

  • Are you passing parentId?

I would appreciate confirmation whether this is:

  • A known limitation,

  • A routing bug,

  • Or a configuration nuance I’m missing.

Thanks.