How To Connect Confluence Docs to LLMs and Coding Agents

Confluence is where most engineering organizations put the things worth writing down. The architecture decision record, the runbook, the spec somebody argued over for two weeks. Then a coding agent opens the repository, sees none of it, and reimplements a decision that was settled last year.

Confluence AI search does not fix this. It is built for a person with a question and a search box. A coding agent needs something it can call in the middle of a task, without a developer stopping to find the page and paste it into a prompt.

That is a connector problem, and the connectors differ more than their marketing suggests.

What actually separates a Confluence connector

Five things, and only the first is usually discussed.

Indexing coverage. Which spaces and page states end up in the index. Personal spaces, archived pages, drafts, and attachments are commonly excluded, and whether that matters depends entirely on where your team actually writes.

Sync latency. How long after an edit the agent sees the new version. A nightly sync means an agent can spend a day working from a spec somebody corrected yesterday morning.

Authentication and scoping. Whether you can point a connection at specific sites and spaces rather than handing over the whole instance.

Write-back. Whether the agent can only read, or can also propose the documentation change that its own code change just made necessary. This is the difference between a connector that keeps documentation drift constant and one that reduces it.

Permission behavior after indexing. Whether retrieval reproduces each user's Confluence permissions, or whether indexed content is available to everyone the connector serves. Both models are defensible. Only one of them is usually explained before you buy.

Dosu

Dosu connects Confluence for teams whose coding agents need that content during a task and whose documentation goes stale the moment code ships.

Reads and writes both run through MCP. read_knowledge supplies relevant context while an agent works. write_knowledge appends a Branch Note scoped to one repository and branch, readable immediately by members of the connected Library. Proposed changes to published Documents take the slower path through review_knowledge. By default a merge auto-accepts the changes it triggered; turn Auto-Accept Review off on the Library and a person approves, edits, or declines each one before it becomes shared truth. Developers stay in Claude Code, Cursor, or Codex rather than switching to a documentation tool.

Connected Confluence content syncs about every five minutes, so the gap between an edit and what an agent reads is measured in minutes rather than overnight. Three authentication methods are supported, OAuth, an email and API token, and a scoped API token, which matters when your security team has an opinion about which one they will approve.

Dosu indexes current pages. Drafts, archived, and trashed pages stay out, deleting a page removes it from the index, and attachments, personal spaces, and system spaces are excluded. If your team's real decisions live in personal spaces, know that going in.

Retrieval is scoped by Library rather than by individual Confluence permissions. You control exposure by choosing which spaces a connection indexes and which Libraries an Agent draws from, and an Agent returns only what the person asking is allowed to see. This is a different model from reproducing per-user Confluence ACLs, and it is the one to check against your own governance requirements first.

Confluence is a paid Source. It requires a paid plan (Pro or Enterprise), at $16 per month billed annually or $20 month to month, and Confluence Data Center and writing documentation back out to Confluence are Enterprise features. The connector is in beta, so confirm availability for your organization with Dosu before you build around it. Dosu pricing has the current breakdown.

Atlassian Rovo

If you want Confluence AI inside Atlassian, Atlassian sells it, and that is a genuinely reasonable place to start.

The Rovo MCP Server is hosted by Atlassian and reached general availability in February 2026. One OAuth 2.1 endpoint spans Confluence, Jira, Compass, Jira Service Management, and Bitbucket, and supported clients include Claude, ChatGPT, VS Code, and GitHub Copilot CLI. Its tools read and write, including creating and updating pages, and the agent inherits the signed-in user's own Atlassian permissions rather than a shared service account's. For a governance review, that last property is the strongest thing on this page.

Two limits shape the fit. It talks to Atlassian Cloud only, so Server and Data Center deployments need the community-maintained server instead. And it operates on Confluence as it finds it. Rovo will happily update a page you point it at, but nothing in it notices that a merged pull request made that page wrong.

Choose Rovo when you want per-user permission inheritance and your work already sits inside Atlassian. It is a retrieval and editing surface, not a drift-detection loop.

Unblocked

Unblocked is a context engine for engineering questions, and it is credible at that. One MCP server connects more than 25 tools, including source code, pull requests, Slack and Teams, Jira and Linear, Confluence and Notion, and Datadog and Sentry, serving Claude Code, Cursor, Codex, and GitHub Copilot along with a CLI, an API, and pull request review. It reports SOC 2 Type II compliance and applies access controls that mirror each source system.

The breadth is unusual for the category, and if your problem is that engineering context is scattered across a dozen tools, that breadth is the product.

Where it stops is agent-side write-back. Unblocked is positioned as a read path that supplies context, not as a way for an agent to update Confluence pages after the code changes. If closing the documentation loop is why you are shopping, that gap is the deciding one.

Dosu vs Unblocked covers the comparison in more depth.

Mintlify

Mintlify is a documentation platform, and a good one, for publishing external docs. API references, product guides, developer-facing content that needs to look right.

It is not a Confluence connector, and including it here is only useful as a category check. If what you actually need is a polished public documentation site rather than internal Confluence retrieval, you are shopping in the wrong aisle and Mintlify is where you should be. If Confluence is where your internal knowledge lives and needs to stay, moving it into a docs platform is a migration, not an integration.

How they compare

Which one fits

Choose Dosu when your coding agents need Confluence context during a task and you want the documentation change proposed after the code lands rather than remembered later. The tradeoff is the permission model, which is scoped by Library rather than by individual Confluence ACLs.

Choose Atlassian Rovo when per-user permission inheritance is a hard requirement and you are on Atlassian Cloud. You get retrieval and editing without the drift detection.

Choose Unblocked when the problem is breadth, and engineers need answers across code, tickets, chat, and observability. Not when you need an agent to write back.

Choose Mintlify when you are actually building a documentation site.

FAQ

How is a Confluence MCP server different from Confluence AI search?

AI search answers a person who has stopped to ask a question. An MCP server exposes tools a coding agent calls on its own, mid-task, without the developer breaking flow. The same content reaches a different consumer through a different interface, and only one of those consumers is writing your code.

Can a coding agent update Confluence through MCP?

Yes, in two different shapes. Rovo lets an agent create and update pages directly under the signed-in user's permissions. Dosu routes proposed changes to published Documents through review_knowledge, and whether a person approves each one first is the Library's Auto-Accept Review setting. Branch Notes write immediately and stay scoped to one branch. Writing back out to Confluence itself is a Dosu Enterprise feature.

What happens to Confluence permissions after content is indexed?

It depends on the model, and this is the question buyers skip. Rovo inherits each user's Atlassian permissions per query. Unblocked mirrors each source system. Dosu scopes retrieval by Library and by which spaces you connect, so you control exposure at the connection rather than per user. Decide which model your security review requires before comparing anything else.

Does Dosu index everything in Confluence?

No, and the exclusions are worth knowing. Current pages are indexed. Drafts, archived, and trashed pages are not, and neither are attachments, personal spaces, or system spaces. Deleting a page removes it from the index.

Connect the spaces your agents keep guessing about

Pick the Confluence space your engineers cite most often in code review, the one with the architecture decisions people keep relitigating. That is the space your agents are currently working without.

Connect it to Dosu and let the next coding session read it over MCP instead of rediscovering it. When the code changes what the page says, the correction gets proposed while the change is still fresh, and you decide whether those changes auto-apply on merge or wait for a person to approve them. Connect Confluence to Dosu and see what your agents have been missing.