Confluence Wiki Search and Page Editing

Search, read, and create pages in Confluence spaces. Agents can reference internal docs or publish content. Connect in one click with OAuth.

Overview

OneCLI connects AI agents to Confluence Cloud. Agents can search your wiki, read pages, and create or update them. The gateway injects the token into every request, so your agent never sees it.

Connecting takes one click. You don’t create an Atlassian app or copy any keys.

Connect Confluence

1. Click Connect

   In the OneCLI dashboard, open Connections > Confluence and click Connect Confluence.

   

   The Confluence connect window in OneCLI.

2. Accept in Atlassian

   Sign in to Atlassian, pick your Confluence site, and click Accept. You’re done. OneCLI keeps the connection active from then on.

You don’t need to be a Confluence admin. Atlassian may show a notice that the app hasn’t been reviewed by Atlassian yet. It’s safe to continue.

What agents can do

• Search all spaces with CQL, filtered by space, type, label, or contributor
• Read a page’s full content, metadata, comments, and attachments
• Create pages and update existing ones
• Add comments and labels
• List spaces and browse page hierarchies

Controlling access

Grant the connection to each agent that needs it, and choose per tool what runs freely, what needs approval, and what’s blocked. Organization rules add guardrails on top. A blocked request never reaches Confluence.

To disconnect, remove the connection in Connections > Confluence, then revoke OneCLI in Atlassian under Account settings > Connected apps.

---

Self-hosted: use your own Atlassian app

Skip this section on OneCLI Cloud. It’s only for self-hosted OneCLI without ATLASSIAN_CLIENT_ID and ATLASSIAN_CLIENT_SECRET set, or if you want your own company name on Atlassian’s consent screen. One Atlassian app serves both Jira and Confluence: if you already set one up for Jira, add the Confluence scopes below and you’re done.

1. Create the Atlassian app

Follow Create the Atlassian app on the Jira page. If you already have one for Jira, reuse it.

2. Add the Confluence permissions

Open Permissions, click Add next to Confluence API, then Configure. Add these on both tabs:

Tab	Scopes
Classic scopes	read:confluence-content.all, write:confluence-content, read:confluence-space.summary
Granular scopes	read:page:confluence, write:page:confluence, read:space:confluence, read:content:confluence

Also add read:me under User identity API if it isn’t there yet, and the Jira scopes from the Jira page. Atlassian keeps one consent per person for each app, so OneCLI asks for the Confluence and Jira scopes together. If any of them is missing from the app, Atlassian shows an error instead of the consent screen.

Use read:confluence-space.summary (space), not read:confluence-content.summary (content). If the space scope is missing, Atlassian shows “Something went wrong” instead of the consent screen.

3. Add the callback URL and connect

In OneCLI, open Connections > Confluence > Custom credentials and copy the Redirect URI. It ends in /v1/apps/oauth/atlassian/callback, the same URI as Jira. Add it to the app’s Callback URLs under Authorization. Then paste the app’s Client ID and Secret, select Save & Connect, and accept in Atlassian.

Copy the Redirect URI from Custom credentials in OneCLI.