Search Confluence with CQL

Search Confluence with CQL

Returns the Confluence pages, blog posts and other content that match a CQL query.

Note: CQL here no longer supports user fields such as user or user.accountid. When more results exist, follow the cursor in the response's next link.

Set up

Use the first option your agent supports.

MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

{ "mcpServers": { "atlassian": { "url": "https://mcp.atlassian.com/v2/mcp" } } }

Call the MCP tool searchConfluence.

Server URL: https://mcp.atlassian.com/v2/mcp

Note: Tools beyond the listed ones are found with discover and run with executeRead or executeWrite; some spend Rovo credits.

API (official)

• Base URL: https://{site}.atlassian.net
• Endpoint: GET /wiki/rest/api/search
• Auth: send the header Authorization: Basic $ATLASSIAN_API_KEY
• Get a key: https://id.atlassian.com/manage-profile/security/api-tokens
• Docs: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/

Note: {site} is your Atlassian site name, as in acme.atlassian.net. ATLASSIAN_API_KEY holds the base64 of <email>:<api token>, and Confluence paths start with /wiki.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

Rules

• Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
• Never print API keys.