Confluence MCP server: scoped wiki access for every agent
Confluence MCP gives an agent search, page-reading and page-editing tools for a Confluence Cloud wiki. AIPx connects the official REST API using your site URL, email and API token, with separate tool rules for each connected account and agent.
What your agent can do with Confluence
Use CQL to find relevant content, inspect spaces and list pages, then fetch the exact page body and version. The adapter can create pages and update existing ones, but it has no page-deletion tool. Updates require the current version from get_page; the runtime reports a conflict instead of quietly replacing a concurrent revision.
| Tool | What it does | Access | Mode |
|---|---|---|---|
| search_content | CQL search | read | Allow |
| list_spaces | Visible spaces | read | Allow |
| list_pages | Pages by space/status | read | Allow |
| get_page | Read body and version | read | Allow |
| create_page | Create storage-format page | write | Confirm |
| update_page | Version-checked page update | write | Confirm |
Source labels describe the checked connection. Live discovery and provider access determine availability; account-specific agent names may be normalized. Modes in this table are recommendations, not a change to upstream permissions.
Capability snapshot: 14 October 2026 · provider source
Wiki work is usually a retrieval problem before it becomes an editing problem. Ask the agent to find the approved document inside a named space, read the page and cite its URL. Search matches alone can include old decisions, archived plans or drafts. A summary should say which page version it used.
For an update, let the agent read the current page immediately before preparing the replacement. The currentVersion value is part of the write request. If someone edits the page between those steps, the agent should fetch the newer content and show a revised proposal; repeating the old request is not a valid resolution.
The body format matters too. This adapter creates storage-format pages. Ask for a small, concrete change with the target page ID and a reviewable body, rather than expecting every Confluence editor feature to be reproduced from a chat message.
Confluence MCP server options: official Rovo, open-source mcp-atlassian, AIPx
| Option | Access path | Trade-off |
|---|---|---|
| Official Rovo | Atlassian-hosted OAuth MCP | Combined Jira and wiki access through the vendor |
| mcp-atlassian | Community runtime and credentials | You maintain execution, hosting and updates |
| AIPx Confluence | Direct Cloud REST adapter | Explicit wiki tools plus agent-specific controls |
The Confluence authentication reference documents the API token route. mcp-atlassian is a community alternative with its own supported products and operations. You can also choose the Atlassian Rovo connection within AIPx when you prefer the official combined surface.
A direct vendor server is easier to reason about for one wiki and one client. AIPx adds credential storage and request handling outside Atlassian, in exchange for reusing connections with different agent rules. There is no automatic expansion of space or page access.
Connect Confluence to Claude, Claude Code or Cursor
Connect a Confluence Cloud site with an Atlassian email and API token. Rovo OAuth is a separate catalog integration.
- Open the AIPx dashboard, choose Confluence under Integrations and complete its connection form or authorization.
- Create an MCP agent, enable that connection and choose the tools this particular agent needs. Save the rules before opening your AI client.
- Copy the agent’s complete URL. The examples below use
AGENT_ID; replace it with the actual value from your dashboard.
An endpoint identifies the AIPx agent, not a provider API key. Client authentication to AIPx is separate from connecting Confluence; adding the URL does not grant extra provider permissions. Our MCP gateway guide explains how several approved connections can share that endpoint.
Connect Claude to Confluence
In Claude, open Customize → Connectors and add a custom connector with your AIPx URL. Continue through AIPx sign-in, then check the tools available in a conversation. Custom connector access depends on account and workspace policy; administrators can restrict it. The Claude MCP setup guide covers the current controls. A direct vendor connection can be simpler when Confluence is the only service you need.
Confluence MCP in Claude Code
claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_ID
Authorize with /mcp, then read one known Confluence page and check its version. Keep updates hidden while verifying the correct space. Claude Code MCP setup describes server configuration and login.
Confluence MCP in Cursor
Add this server to .cursor/mcp.json for the project or ~/.cursor/mcp.json for your user:
{
"mcpServers": {
"aipx": { "url": "https://dash.aipx.run/mcp/AGENT_ID" }
}
}
In Cursor, complete sign-in and search the named Confluence space before fetching a page. A later update needs its current version and client approval. See Cursor MCP configuration for setup troubleshooting.
Confluence MCP in Codex
codex mcp add aipx --url https://dash.aipx.run/mcp/AGENT_ID
codex mcp login aipx
codex mcp list
Codex uses the HTTP endpoint and browser OAuth; it does not need a copy of the Confluence credential in its config. See Codex MCP setup for TOML configuration and project trust requirements.
Where ChatGPT custom MCP is enabled, use this endpoint to read a named wiki page. That does not make every space accessible or authorize page edits. ChatGPT MCP setup explains tier and administration requirements.
Scope Confluence per agent: search and read on Allow, page edits on Confirm
A documentation researcher needs search_content, list_spaces, list_pages and get_page. It does not need create_page or update_page. Hide both writes for that agent. A separate documentation assistant can have those writes on Confirm, with the target space and page shown in the client before approval.
Hide removes callable tools; it does not alter the underlying Confluence user’s permissions. Confirm is a client-facing approval hint, so a client that does not honor it needs stricter tool hiding. The MCP permissions guide explains this distinction.
Use Confluence with Jira
A Jira MCP connection can supply issue status while Confluence supplies the decision record. Ask the agent to compare a named ticket with its linked specification and produce a discrepancy list. Approve a Jira comment only after the sources are visible; no wiki write is necessary for that task.
If specifications also live in Notion, include that connection only for the pages the agent needs. GitHub adds implementation evidence, and Linear can be used for a tracker outside Atlassian. Different providers remain separate accounts behind the agent URL.
Confluence API limits and version conflicts
Confluence Cloud access controls still decide which spaces and pages a user may read or edit. Tool rules cannot narrow one search tool to an arbitrary subset of spaces, so use a provider account with the required space restrictions. Specify a space in the prompt to make results relevant, but treat that prompt as task guidance rather than an authorization boundary.
A stale version error protects a teammate’s newer edit. Return to get_page, compare revisions and review the proposed update again. The connector does not promise full parity with macros, attachments or every editor feature. Its advertised boundary is search, spaces, pages, creation and version-checked updates.
Browse all MCP integrations to choose another connection for this agent.
The Confluence connection can use AIPx Free with 3 active accounts and 1 agent; check AIPx pricing for gateway plans and keep provider or client charges separate.
What to ask your agent
Name the Confluence account and a bounded task. Ask for source identifiers and a proposed result before approving a change.
FAQ
Can I connect Confluence to Claude?
Yes. Connect Confluence in AIPx, create an MCP agent and add its copied URL as a Claude custom connector when your account and workspace permit. Choose tools before using the connection.
How do I add Confluence MCP to Claude Code?
Run claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_ID with your actual agent endpoint, then use /mcp to authorize and inspect tools. See Claude Code MCP setup.
Is the Confluence integration free?
AIPx Free includes 3 active connected accounts and 1 agent; Pro is $3/month. Provider subscriptions, API charges and the AI client's own connector access are separate. See AIPx pricing.
Can I connect two Confluence accounts?
Yes. Add separately authorized Confluence connections and choose each account's tools independently for the agent. One endpoint can include both; it does not merge accounts or synchronize provider data.
Can my agent change Confluence data?
Yes. The adapter can create and update pages when the connected Confluence user has permission. It does not expose page deletion. Keep edits on Confirm and require a fresh page version.
When should I use the official Confluence connection?
Use a direct vendor connection when one service and one client meet your needs and you prefer fewer services handling data. For an API-only service, that can mean using the official API or a compatible server you maintain. AIPx adds shared connections and agent-specific rules.