Confluence Connector

Features & Workflows · 6 min read · Growth & Scale plans

Overview

The Confluence connector is MindBacklog's first knowledge connector — an MCP-based integration that lets Ask Mind search your team's own Confluence wiki live. Once connected, questions like "what does our wiki say about the onboarding redesign?" or "find the design doc for search filters" are answered from your actual Confluence pages, with clickable citations to the real pages — alongside the customer signals, roadmap data, and competitive intelligence Ask Mind already reasons over.

Unlike uploaded Knowledge documents, nothing is imported or indexed: every search runs against Confluence at the moment you ask, so answers always reflect the current state of your wiki.

Confluence is the first Connector on the Integrations page — see the Integrations overview for how Connectors and Native Apps differ.

How It Works

MindBacklog connects as a client to Atlassian's official remote MCP server — the same secure interface Atlassian built for AI tools like Claude and ChatGPT. At connect time, MindBacklog verifies your credentials, discovers the Confluence search tools your Atlassian site exposes, and runs a test search. From then on, Ask Mind gains two grounded tools: wiki search (find relevant pages) and page fetch (read one page in full). Everything is read-only — the connector never writes to Confluence.

Prerequisites

A MindBacklog Growth or Scale plan, and Admin role on the product.
An Atlassian Cloud site with Confluence (any Atlassian plan, including Free).
A scoped Atlassian API token created with Confluence access — create one at id.atlassian.com → Security → API tokens. Choose a scoped token and include the Confluence read/search scopes.
Your Atlassian organization admin must enable API-token access for the MCP server: Atlassian Administration → Rovo → Rovo MCP server → Authentication. If this is off, valid tokens are still rejected.

Connecting Confluence

Open the Integrations page

Click Integrations in the left sidebar (under "The Mind"). The page opens on the Connectors tab, where you'll find the Confluence card.

Enter your credentials

Click Connect on the Confluence card. Enter your Atlassian account email, the scoped API token, and your site URL (e.g. https://your-team.atlassian.net), then click Connect & Verify.

MindBacklog verifies the connection

MindBacklog performs a live handshake with Atlassian's MCP server, confirms the Confluence search tools are available to your token, and runs a test search. On success, the card shows Connected with your site, the discovered tools, and who connected it.

Using It in Ask Mind

No extra setup — once connected, Ask Mind automatically knows your wiki is available. Ask naturally:

"What does our Confluence say about the Q3 pricing change?"
"Find the design doc for the onboarding flow."
"Check the wiki — do we have a runbook for incident response?"
"Compare what customers are asking for with what our spec already covers."

Answers cite the actual pages, and a Sources list with links to the cited Confluence pages appears under the reply. Ask Mind keeps your three knowledge sources distinct: Confluence (your team wiki, searched live), Knowledge (documents uploaded to MindBacklog), and web search (public internet).

Connection Health & Testing

The Confluence card on the Integrations page shows the connection status, the last successful call, and any recent error. Use Test connection to re-verify on demand — it re-runs the handshake and refreshes the discovered tools. MindBacklog also health-checks every connection daily and automatically adapts if Atlassian renames its tools. If the wiki is temporarily unreachable mid-conversation, Ask Mind says the source failed rather than guessing.

Security & Data Handling

Credentials are encrypted at rest and never appear in logs.
Searches run live — no Confluence content is copied, indexed, or stored in MindBacklog (results are briefly cached for a few minutes for performance).
Access is limited to what the API token's account can see in Confluence, and everything is read-only.
Wiki content is treated as untrusted input and sanitized before Ask Mind reads it.

Disconnecting

Click Disconnect on the Confluence card. This immediately deletes the stored credentials and removes the wiki tools from Ask Mind. For complete hygiene, also revoke the API token in your Atlassian account (id.atlassian.com → Security → API tokens) — MindBacklog cannot revoke it for you. Disconnecting works on any active plan, including after a downgrade to Starter. If your subscription has fully lapsed, reactivate it first — the whole workspace is paywalled until then; your stored credentials stay dormant in the meantime, and you can revoke the token in Atlassian anytime.

Troubleshooting

Issue	Solution
"Authentication failed" when connecting	Check the email and token are correct — and confirm your Atlassian org admin has enabled API-token access for the MCP server (Atlassian Administration → Rovo → Rovo MCP server). This is the most common cause.
"No Confluence search tool was exposed"	The token connected, but lacks Confluence scopes. Create a new scoped API token and include the Confluence read/search scopes when creating it.
Card shows Auth failed later on	The token was revoked or expired on the Atlassian side. Click Reconnect and enter a fresh token — your connection settings are preserved.
Ask Mind says the wiki source failed	Temporary outage or rate limiting on the Atlassian side. Use Test connection on the Integrations page; the daily health check also recovers connections automatically.
Connected, but searches return nothing / "not among the accessible sites"	The site URL must match a site your Atlassian account can actually access. Re-check the site URL (e.g. `https://your-team.atlassian.net`) and reconnect — MindBacklog verifies a live test search before saving, so a mismatched site is caught at connect time.
Connectors tab shows an upgrade prompt	Knowledge connectors require a Growth or Scale plan. Existing connections can still be disconnected on any active plan (including Starter).