Confluence
Connect Confluence to search, read and write pages and blog posts, organize spaces, comment, label, and manage attachments and page access.
You enter three values into PopMCP: your Confluence Cloud site (yourcompany.atlassian.net), the email you sign in to Atlassian with, and an Atlassian API token, either a classic one or one with scopes.
- Setup time
- 4 min
- Auth
- API credentials
- API base URL
- https://YOUR-SITE.atlassian.net/wiki/api/v2
- Rate limits
- API token traffic is governed by Confluence Cloud's burst limits, measured over a few seconds, with extra protection on search, permission and admin endpoints. The hourly points quota (65,000 points an hour for an app on Tier 1) applies to apps, not to API tokens. Throttled requests get 429 with Retry-After and a RateLimit-Reason header.
Before you begin
- A Confluence Cloud site on atlassian.net. Confluence Server and Confluence Data Center are not supported
- An Atlassian account that can open Confluence on that site. The MCP works as this account and sees only the spaces and pages it can see
- Access to the inbox of your Atlassian email: if you sign in with a password or a third-party login, Atlassian emails a one-time code before it lets you create a token
- Permission to create API tokens. An organization admin can block them for managed accounts through an authentication policy
Get your credentials
Copy your Confluence site address
Open Confluence in your browser and copy the host from the address bar, for example yourcompany.atlassian.net (Confluence itself lives under /wiki). The name on its own (yourcompany) or a link to any page is enough for PopMCP. Older sites that still answer on yourcompany.jira.com work too.
Open https://YOUR-SITE.atlassian.net/wiki (replace YOUR-SITE with your Confluence site).
Open API tokens in your Atlassian account
Go to id.atlassian.com, open Security and click Create and manage API tokens, or use the direct link. If Atlassian asks you to verify your identity, enter the one-time code it emails you.
API tokens
A script or other process can use an API token to perform basic authentication with Jira Cloud applications or Confluence Cloud.
| Name | Created | Expires | |
|---|---|---|---|
| Docs exportScopes: read:page:confluence | Mar 4, 2026 | Mar 4, 2027 | Revoke |
Create API token makes a classic token that can do whatever your account can. Create API token with scopes limits it to the scopes you pick.
Create a classic API token
Click Create API token. Name it PopMCP, choose an expiry date between 1 and 365 days from today, and click Create. When the token expires, the connection stops working until you paste a new one.
API tokens
A script or other process can use an API token to perform basic authentication with Jira Cloud applications or Confluence Cloud.
Copy the token
Click Copy to clipboard in the dialog. Tokens created now start with ATATT. Atlassian does not show the token again, so paste it somewhere safe or straight into PopMCP.
API tokens
A script or other process can use an API token to perform basic authentication with Jira Cloud applications or Confluence Cloud.
Lost it? Revoke the token on this page and create a new one.
Or create a token with scopes
To limit what the MCP can do, click Create API token with scopes instead. Name it and set its expiry, choose Confluence as the app, then tick the scopes the tools need: read:page:confluence, read:space:confluence, read:comment:confluence, read:attachment:confluence, read:label:confluence and read:content-details:confluence (search and users) for reading, and write:page:confluence, write:comment:confluence, write:label:confluence and write:attachment:confluence to change things. Click Create and copy the token. PopMCP detects a scoped token when you connect and sends it through Atlassian's API gateway, which is the only place Atlassian accepts it.
API tokens
A script or other process can use an API token to perform basic authentication with Jira Cloud applications or Confluence Cloud.
A scoped token answers 401 for any tool outside its scopes. Tick the scopes for every kind of work you want the AI to do.
Enter the three values in PopMCP
In PopMCP, fill in Confluence site with your site address, Atlassian email with the email you sign in to Atlassian with, and API token with the token you copied. Connect, and PopMCP checks the token against your site (and Atlassian's API gateway for a scoped token) straight away.
Connect in PopMCP
Open your workspace, choose Confluence in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Confluence sitetext | The address you open Confluence at. The name on its own (yourcompany) or a link to any page works too. |
| Atlassian emailtext | The email you sign in to Atlassian with. The MCP works as this person and sees only what they can see in Confluence. |
| API tokensecret | At id.atlassian.com go to Security, then Create and manage API tokens, then Create API token. Name it PopMCP, choose when it expires (a year at most) and copy it. A token with scopes works too: give it the Confluence scopes the MCP should use. Stored encrypted.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Confluence immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP marks the Confluence connection Verified, labelled with your site (yourcompany.atlassian.net) and a note saying which Atlassian user it acts as. For a scoped token it also notes that Confluence only allows what the scopes cover. Asking the AI to find a page you know returns its real title and link.
Troubleshooting
"Confluence rejected that email and API token for yourcompany.atlassian.net."
Why: The email is not the one the Atlassian account signs in with, the token was copied incompletely or has expired, or the account cannot open Confluence on that site.
Fix: Check the email under **Email** in your Atlassian account, create a fresh token and paste it in one piece, and confirm you can open Confluence on that site in your browser.
"There is no Atlassian Cloud site at yourcompany.atlassian.net."
Why: The site name is mistyped or belongs to a different Atlassian organization.
Fix: Copy the host from your browser's address bar while Confluence is open and paste it into **Confluence site**.
"yourcompany.atlassian.net is an Atlassian site, but Confluence did not answer there."
Why: The site exists but has no Confluence on it, for example a Jira-only site.
Fix: Use the site where your spaces live. Its address is in the browser when you open a Confluence page.
The site address is refused as "not a Confluence Cloud site"
Why: The address is a Confluence Server or Data Center host, or anything other than an atlassian.net (or older jira.com) site.
Fix: This connector works with Confluence Cloud only. Enter your site's atlassian.net address.
Some tools answer 401 while others work
Why: The connection uses a token with scopes, and those tools need a scope it was not given.
Fix: Create a new token with the missing scopes (or a classic token) and reconnect Confluence with it.
A page you can see answers 404
Why: Confluence answers 404 both when a page does not exist and when the connected account cannot see it, for example because of a page restriction or space permission.
Fix: Check the page id or link, and that the connected account can open the page in Confluence.
There is no way to create an API token, or a working token suddenly stops
Why: Your organization admin blocks API tokens for managed accounts through an authentication policy, or the token reached its expiry date (one year at most).
Fix: Ask your Atlassian organization admin to allow API tokens for your account, or create a new token and reconnect.
Reference
Superhuman Docs
Connect Superhuman Docs (formerly Coda) to read and edit docs, pages and tables, add and update rows, run buttons and automations, and manage sharing.
Dropbox
Connect Dropbox to find, read, upload and organize files and folders, share links and folders, request files, and manage your team.