---
ref: tool:atlassian/create-confluence-page
name: Create a Confluence page
company: company:atlassian
workflows: []
access: [mcp, api]
tags: [capability:manage-docs, category:project-management, has:api, has:mcp]
docs: https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-page/#api-pages-post
updated: 2026-09-27
---

# Create a Confluence page

Creates a page in a Confluence space, under a parent page if you pass one, and returns the new page.

Note: Needs the space's `spaceId`. The page publishes immediately unless `status` is `draft`, and a published page needs a `title`.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "atlassian": { "url": "https://mcp.atlassian.com/v2/mcp" } } }
```

Call the MCP tool `createConfluenceContent`.

Server URL: https://mcp.atlassian.com/v2/mcp

Note: Tools beyond the listed ones are found with `discover` and run with `executeRead` or `executeWrite`; some spend Rovo credits.

### API (official)

- Base URL: https://{site}.atlassian.net
- Endpoint: `POST /wiki/api/v2/pages`
- Auth: send the header `Authorization: Basic $ATLASSIAN_API_KEY`
- Get a key: https://id.atlassian.com/manage-profile/security/api-tokens
- Docs: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/

Note: `{site}` is your Atlassian site name, as in `acme.atlassian.net`. `ATLASSIAN_API_KEY` holds the base64 of `<email>:<api token>`, and Confluence paths start with `/wiki`.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.