Confluence Data Center is the self-hosted edition of Confluence by Atlassian, run on your own servers. This connector lets your AI agents search, read, create, and update pages, spaces, and labels on your Confluence Data Center server through Agen.co.
Use this page if you host Confluence yourself. If you use Confluence on Atlassian's cloud (an address ending in atlassian.net/wiki), see Confluence instead. To reach Jira and Confluence on Atlassian's cloud through Atlassian's own MCP server, see Atlassian.
You can connect with either of two methods:
| Method | Best for | Minimum Confluence version |
|---|---|---|
| OAuth | Each person acts with their own Confluence permissions. You create an incoming application link on your Confluence server. | 7.17 |
| Personal Access Token | A single token tied to one Confluence user, for example a dedicated service account. No application link needed. | 7.9 |
Prerequisites
Prerequisites
- A Confluence Data Center server, version 7.17 or later for OAuth, or 7.9 or later for a Personal Access Token.
- Network access from Agen.co to your Confluence server. If the server is behind a firewall or VPN, allow Agen.co's outbound traffic before you connect.
- For OAuth: a Confluence administrator who can create application links.
- For a Personal Access Token: a Confluence user whose permissions match what your agents should be able to do.
Agen.co asks for your server's host, which it uses to build every request. Use the address you type in the browser to open Confluence, without https:// and without a trailing slash:
| If Confluence is at | Enter |
|---|---|
https://confluence.acme.com | confluence.acme.com |
https://confluence.acme.com:8443 | confluence.acme.com:8443 |
https://acme.com/confluence | acme.com/confluence |
Include the port or the context path if your server uses one. The connector always uses HTTPS.
- In the Agen.co portal, go to Connectors → My connectors and click Add connector.
- In the Select connector drawer, search for
Confluence Data Centerand select it. The Add Confluence Data Center panel opens. - Under Authentication method, select OAuth.
- Copy the read-only Callback URL. Copy the whole value, including the path, rather than assembling it yourself. See How to get your Redirect URL.
Leave the panel open. You return to it after creating the application link.
- Sign in to Confluence as an administrator, open the administration menu (the cog icon), and go to Application links. In some versions it sits under General Configuration.
- Click Create link, select External application, and set the direction to Incoming.
- Enter a name, for example
Agen.co. - Paste the Callback URL you copied into the Redirect URL field.
- Set the permission to Write. Write includes read access, so this is the only permission the connector needs.
- Save the link, then copy the Client ID and Client secret that Confluence shows.
Keep the client secret secure
Keep the client secret secure
Never share or commit the client secret to version control. If you lose it, open the link in Application links to view its details, or create a new link.
Return to the Add Confluence Data Center panel and fill in the fields:
| Field | Required | Description |
|---|---|---|
| Connector Name | Yes | A name for this connection, for example Confluence Data Center. |
| Client ID | Yes | The Client ID from the application link. |
| Client Secret | Yes | The client secret from the application link. |
| Confluence server host | Yes | Your server host, as described in Find your Confluence server host. |
Click Add. The connector is created right away. The first time a user's agent calls one of its tools, that user signs in to your Confluence server and approves access.
- Sign in to Confluence as the user the connector should act as.
- Select your profile picture in the top-right corner, then select Settings → Personal Access Tokens.
- Click Create token, enter a name, and optionally set an expiry in days.
- Click Create and copy the token. Confluence shows it only once.
The token acts as its owner
The token acts as its owner
Every request runs with the permissions of the user who created the token. Use a dedicated user with only the access your agents need. An expired token cannot be reactivated, so create a new token and update the connector before the old one expires.
- In the Agen.co portal, go to Connectors → My connectors and click Add connector.
- Search for
Confluence Data Centerand select it. In the Add Confluence Data Center panel, under Authentication method, select Personal Access Token. - Fill in the fields:
| Field | Required | Description |
|---|---|---|
| Connector Name | Yes | A name for this connection, for example Confluence Data Center. |
| Personal Access Token | Yes | The token you created in Confluence. |
| Confluence server host | Yes | Your server host, as described in Find your Confluence server host. |
- Click Add.
Enabling the connector isn't enough on its own. Tool calls remain denied until you create a policy that grants access to the specific tools you want to expose.
The connector exposes 17 tools:
| Area | What it covers |
|---|---|
| Pages and blog posts | Reading, creating, updating, and deleting pages and blog posts, listing child pages and all descendants of a page, and searching with CQL |
| Spaces | Reading and listing spaces, creating and updating a space, and listing the pages in a space |
| Labels | Reading, adding, and removing labels on a page |
| Users | Reading the connected user and looking up a user by username or key |
- Page content uses Confluence storage format. Page bodies are read and written as Confluence's XHTML storage format, for example
<p>Hello</p>, not Markdown. - Updating a page replaces its body. The update must carry the page's current version number plus one and its title, and the body you send replaces the existing content. Read the page first.
- Page titles must be unique within a space. Pick a title that no other page in the space already uses.
- Deleting a page moves it to the trash. Deleting it again from the trash removes it permanently.
- Spaces are identified by key, and people by username or user key. The space key is the short identifier such as
DOCS, not a numeric ID. New space keys can contain only letters and numbers. - Space changes need space administrator rights. Updating a space requires the connected user to be an administrator of that space.
- Listing descendants needs a numeric page ID. The ID of the ancestor page must be numeric.
- Label names are lowercase with no spaces.
- Everything runs with the connected user's permissions. An agent can only see and change what that user can, whichever method you use.
- Fewer tools than Confluence on Atlassian's cloud. Archiving pages, space labels, label details, and listing Atlassian cloud sites have no equivalent on Data Center and are not included.