Skip to main content
The Confluence MCP server lets you govern access to Confluence Cloud — pages, blog posts, spaces, comments, attachments, whiteboards, groups, users, and CQL search — as tools your AI clients can call through C1. Confluence supports two ways to authenticate, and you choose one when you register the server:
  • Per-user OAuth (recommended). Each person authorizes with their own Atlassian account, so every tool call runs under that user’s identity and permissions.
  • Atlassian API token (scoped). A single API token, created for a person or a service account, authenticates everyone as one shared identity. C1 sends it as a Bearer token.
For a deeper comparison of shared versus per-user credentials, see Configure authentication.

How C1 connects to Confluence

C1 hosts the Confluence MCP server, so your users’ AI clients only ever see MCP tools — they never call Confluence directly. When an AI client calls one of these tools, C1 makes the matching request to the Confluence API using the credentials you configure here, then returns the result to the AI client. The credentials you set up below are what C1 uses to call Confluence on your users’ behalf.

Before you begin

  • AI access management must be enabled for your tenant. See Enable AI access management.
  • For per-user OAuth, an Atlassian account that can create an OAuth 2.0 integration. See Atlassian’s OAuth 2.0 (3LO) apps guide.
  • For an API token, an Atlassian account or service account that can create API tokens with scopes, with access to Confluence.
  • Your Atlassian site’s Cloud ID. To find it, open https://your-site.atlassian.net/_edge/tenant_info in a browser, replacing your-site with your site’s name, and copy the cloudId value.
If you don’t see Confluence in your MCP server catalog, contact the C1 support team to enable it for your tenant.

Option 1: Create an Atlassian OAuth 2.0 integration

With per-user OAuth, you register one Atlassian OAuth 2.0 (3LO) integration and each user authorizes individually. This keeps every action attributable to the user who took it, with only the access that user already has in Confluence.
1
Sign in to the Atlassian Developer Console with your Atlassian account. For the full walkthrough, see Atlassian’s OAuth 2.0 (3LO) apps guide.
2
Select Create > OAuth 2.0 integration, enter a recognizable name such as C1, and if prompted for an Access type, choose Resource-level. Then select Create.
3
Open the Permissions tab. Next to Confluence API, select Add, then Configure, and add the scopes from Confluence scopes below — the default read scopes, plus any optional write or delete scopes you need.
4
Open the Authorization tab. Next to OAuth 2.0 (3LO), select Configure and set the Callback URL exactly to whichever matches your C1 tenant’s domain:
  • Default instance: https://accounts.conductor.one/auth/callback
  • EU data residency instance: https://accounts.c1eu.ai/auth/callback
Select Save changes.
5
Open the Settings tab. Under Authentication details, copy the Client ID and the Secret. Reveal the secret to copy it, and treat it as a high-value credential.

Confluence scopes

C1 requests the default read scopes automatically. The default is read-only; to enable write or delete tools, add the optional scopes below in the Developer Console (Permissions > Confluence API > Configure) and in C1’s scopes field when configuring authentication. Grant only what you need. These are Confluence’s granular scopes — the Confluence MCP server targets the Confluence v2 API, which the classic scopes (write:confluence-content, and so on) do not authorize. Default scopes (enable all of them) read pages, spaces, attachments, comments, and related content, and let the search tools run CQL queries (read:content-details:confluence), plus offline_access for token refresh: read:app-data:confluence, read:attachment:confluence, read:comment:confluence, read:configuration:confluence, read:content-details:confluence, read:content.metadata:confluence, read:custom-content:confluence, read:database:confluence, read:embed:confluence, read:folder:confluence, read:hierarchical-content:confluence, read:label:confluence, read:page:confluence, read:space.permission:confluence, read:space:confluence, read:task:confluence, read:user:confluence, read:whiteboard:confluence, offline_access Optional scopes enable the write and delete tools: Create and update: write:app-data:confluence, write:attachment:confluence, write:comment:confluence, write:configuration:confluence, write:custom-content:confluence, write:database:confluence, write:embed:confluence, write:folder:confluence, write:page:confluence, write:space.permission:confluence, write:space:confluence, write:task:confluence, write:whiteboard:confluence Delete: delete:attachment:confluence, delete:comment:confluence, delete:custom-content:confluence, delete:database:confluence, delete:embed:confluence, delete:folder:confluence, delete:page:confluence, delete:whiteboard:confluence
Every default scope must be enabled on your integration. If C1 requests a scope the integration doesn’t have, authorization fails and Atlassian shows only “Something went wrong.”
Atlassian recommends keeping an app under 50 scopes. Scope changes take effect the next time a user connects — adding an optional scope after users have connected requires each user to reconnect their Atlassian account.

Register the Confluence MCP server with OAuth

With your OAuth 2.0 integration ready, register the server and provide its credentials.
1
Follow Register an MCP server and select Confluence from the catalog.
2
Enter your Atlassian site’s Cloud ID.
3
When you configure authentication, choose per-user OAuth and enter your integration’s client ID and client secret.
4
Save your changes. The first time a user calls a Confluence tool from their AI client, they’re prompted to connect their Atlassian account.

Option 2: Set up an Atlassian API token

An Atlassian API token authenticates every user as one shared identity: the Atlassian account that owns the token. Use it when per-user attribution in Confluence isn’t required, or when you want a service account to own the connection. C1 sends the token as a Bearer token.

Create an API token

Create an API token with scopes, either for a person or for a service account, so C1 can authenticate to the Confluence API. The token’s scopes are fixed when you create it, so select every scope below. To change them later, create a new token.
1
Open Atlassian API tokens and select Create API token with scopes. For details, see Atlassian’s Manage API tokens for your Atlassian account documentation.
2
Enter a name such as C1.
3
Choose an expiration between 1 and 365 days, then select Next.
4
Select Confluence as the app, then select Next.
5
Select these scopes, then select Next:
  • read:app-data:confluence
  • read:attachment:confluence
  • read:comment:confluence
  • read:configuration:confluence
  • read:content-details:confluence
  • read:content.metadata:confluence
  • read:custom-content:confluence
  • read:database:confluence
  • read:embed:confluence
  • read:folder:confluence
  • read:hierarchical-content:confluence
  • read:label:confluence
  • read:page:confluence
  • read:space.permission:confluence
  • read:space:confluence
  • read:task:confluence
  • read:user:confluence
  • read:whiteboard:confluence
To enable write or delete tools, also select the matching write: or delete: scopes from Confluence scopes. Keep read:content-details:confluence selected, because the search tools need it.
6
Review the token and select Create.
7
Copy the token. Atlassian shows it only once.
To own the token with a service account instead of a person, create it from the service account in Atlassian Administration under Directory > Service accounts > Create credentials > API token, and select the same scopes. Give the service account access to Confluence and to the spaces C1 should read. For the full procedure, see Atlassian’s Manage API tokens for service accounts documentation. A dedicated service account keeps activity attributable to C1 rather than a person. The token expires on the date you chose, so rotate it before then.

Register the Confluence MCP server with an API token

With your API token ready, register the server and provide it.
1
Follow Register an MCP server and select Confluence from the catalog.
2
Enter your Atlassian site’s Cloud ID.
3
When you configure authentication, choose Bearer token and paste your API token.
4
Save your changes. C1 runs tool discovery against Confluence.

How Confluence credentials are shared

With per-user OAuth, each user authorizes with their own Atlassian account, so tool calls run under that user’s Confluence identity and inherit only the access they already have. Atlassian attributes each action to the individual user. With an API token, every user’s tool calls use the one credential you provided, so Confluence sees a single shared identity: the account that owns the token. C1 still attributes each call to the individual user in the AI tool usage audit log. For how shared and per-user credentials work across MCP servers, see Configure authentication.

Discover and govern tools

After you register the server, C1 runs tool discovery against Confluence. Discovered tools appear on the server’s Tools tab. Each tool starts as either Pending review or automatically Approved, depending on the option chosen when the server was set up or your tenant’s default tool settings in AI > MCPs > Settings. See Require tool approval and Default tool classification. Before anyone can call a Confluence tool, it must be approved, added to a toolset, and bound to an access profile. Continue to Govern tools and toolsets to set this up.
Tool discovery runs even if your credentials are incorrect, so seeing discovered tools doesn’t confirm that authentication is working. You confirm your Confluence credentials when an approved user successfully calls a Confluence tool from their AI client.

Manage your Confluence credentials

  • Rotate the OAuth client secret in the Atlassian Developer Console under your integration’s Settings tab, then update the secret on the server’s authentication settings in C1.
  • Rotate an API token by creating a new token in Atlassian with the same scopes and updating it in C1, then revoking the old one. Create the new token before the current one expires.
  • Adjust access by editing the integration’s Confluence scopes on the Permissions tab in the Atlassian Developer Console. For an API token, create a replacement token with different scopes.

Troubleshooting Confluence authorization and scopes

Most Confluence tool errors that mention authorization come from a scope that is missing on your OAuth 2.0 integration or in C1.
The search tools need read:content-details:confluence. Without it, Confluence returns 401 with Unauthorized; scope does not match while the other Confluence tools keep working, so the error can look like an expired login. Retrying doesn’t help.To enable search, add the scope in both places, then reconnect:
1
In the Atlassian Developer Console, open your integration’s Permissions tab, select Configure next to Confluence API, and add read:content-details:confluence.
2
In C1, open the Confluence server’s authentication settings and add read:content-details:confluence to the scopes field if it isn’t listed.
3
Have each user reconnect their Atlassian account so their new authorization includes the scope.
If you authenticate with an API token, the scopes are fixed when the token is created. Create a new token that includes read:content-details:confluence, then replace the token in C1’s authentication settings.
C1 requested a scope that isn’t enabled on your integration. Compare the scopes in C1’s authentication settings with the integration’s Confluence scopes on the Permissions tab, enable any that are missing, and have the user connect again.