Sign in Book a demo

  • Productivity & Docs

  • OAuth

Let an agent search Confluence, read page content, create pages, and update or rename existing documentation.

Set Up Confluence View Confluence Docs

Available Tools

17 tools available in this integration

Confluence.CreatePage

Create a new page at the root of the given space.

Confluence.GetAttachmentsForPage

Get attachments for a page by its ID or title.

Confluence.GetAvailableAtlassianClouds

Get available Atlassian Clouds.

Confluence.GetPage

Retrieve a SINGLE page's content by its ID or title.

Confluence.GetPagesById

Get the content of MULTIPLE pages by their ID in a single efficient request.

Confluence.GetSpace

Get the details of a space by its ID or key.

Confluence.ListAtlassianClouds

Get available Atlassian Clouds.

Confluence.ListAttachments

List attachments in a workspace

Confluence.ListDirectChildren

List one page of direct children for a Confluence content item.

Confluence.ListPageAttachments

Get attachments for a page by its ID or title.

Confluence.ListPages

List pages with their content, newest first by default, optionally only the pages with

Confluence.ListSpaces

List all spaces sorted by name in ascending order.

Confluence.RenamePage

Rename a page by changing its title.

Confluence.SearchContent

Search for content in Confluence.

Confluence.UpdatePageContent

Update a page's content.

Confluence.UpdatePageTitle

Rename a page by changing its title.

Confluence.WhoAmI

CALL THIS TOOL FIRST to establish user profile context.

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "find the latest launch decision and summarize the supporting pages." Arcade picks the right Confluence actions without guessing page IDs, space keys, or the page hierarchy first.

Up to 100x fewer tokens

Confluence searches and page listings return page-level results so the agent can identify the right documents before loading full page content, avoiding the cost of putting an entire documentation space in the model.

Complete the workflow end to end

Search the space, inspect the relevant pages, check their attachments, draft the update, and publish it after approval through one toolkit designed around the complete documentation task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing Confluence

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For Confluence, you can implement some of these policies:

Access when tools are listed for a user
  • Hide Confluence.CreatePage from agents outside the roles your IDP marks as content publishers, so unreviewed agents cannot add pages to shared spaces.
  • Deny Confluence.RenamePage to agents that are not operating under your space-owner role, so automation cannot change titles that people use to find approved guidance.
  • Hide Confluence.UpdatePageContent from read-only agents, so they cannot overwrite published procedures or records.
  • Hide Confluence.UpdatePageTitle from agents without your space-administrator role, so automated workflows cannot rename pages that serve as canonical navigation targets.
Pre-execution before each tool call
  • Require human approval before Confluence.CreatePage runs in a shared space, so an agent cannot publish an unreviewed page.
  • Block Confluence.RenamePage when the new title removes your required document identifier or approval status, so links and review labels do not become misleading.
  • Refuse Confluence.UpdatePageContent for pages in spaces marked production unless the request comes from your designated content owner, so an agent cannot alter controlled documentation without authorization.
  • Require an owner sign-off before Confluence.UpdatePageTitle runs on a page with inbound links, so an agent cannot silently break references to published guidance.
Post-execution after the tool returns
  • Redact credentials, API keys, access tokens, and personal contact details from the page body Confluence.GetPage returns before they reach the model.
  • Strip private download URLs and attachment metadata from Confluence.GetAttachmentsForPage results, so the model cannot expose links to restricted files.
  • Redact page excerpts, comments, and search-result text containing customer records, secrets, or legal-hold material from Confluence.SearchContent before the model sees it.
  • Redact tenant IDs, base URLs, and organization names from Confluence.ListAtlassianClouds results before they reach the model, so it cannot expose your Atlassian account inventory.
  • Strip attachment filenames, media types, and download URLs from Confluence.ListPageAttachments results for restricted pages, so the model cannot reveal files that the agent should not disclose.

How to use Confluence with your agent

Pick your MCP client and follow the walkthrough to connect Confluence with per-user OAuth. Then ask your agent to search spaces, inspect page hierarchies, or update documentation.

Your questions, answered

A Confluence MCP server exposes Confluence capabilities as structured tools that an AI agent can call through the Model Context Protocol. After a user authorizes their Atlassian account, the agent can search, read, organize, and update permitted Confluence content.

Arcade provides the MCP access layer for Confluence rather than relying on a separate Confluence-hosted MCP endpoint. It adds per-user OAuth, approval workflows, response redaction, scope controls, and one connection path for supported agents and frameworks.

Arcade agents can search Confluence content, read individual or multiple pages, inspect spaces and page hierarchies, list attachments, retrieve attachment details, create root-level pages, update page content, and rename pages. They can also identify the authorized user and available Atlassian Cloud accounts.

Arcade needs the Confluence OAuth permissions required by the actions you enable and the pages or spaces each user can access. Read-only workflows need read access; creating, editing, or renaming pages also requires the corresponding Confluence write permission. Grant the narrowest access that supports the workflow.

Yes. Each user authorizes their own Confluence account through OAuth. Actions run under that user's authorization, so the agent can access only the Confluence content and write permissions that user has approved.

Yes. Contextual Access policies can require human approval before consequential Confluence actions such as creating a page, changing page content, or renaming a page. The call proceeds only after the policy's conditions have been satisfied.

Arcade proxies Confluence API calls and does not persist Confluence content as part of normal tool execution. OAuth credentials are brokered and stored encrypted at rest, and the model never receives raw credentials.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade refreshes access while the user's Confluence authorization remains valid. If it is revoked, rotated, or can no longer be refreshed, actions stop until the user reconnects their Confluence account.

Confluence's API rate limits and any limits associated with the user's Atlassian Cloud account still apply through Arcade. The available actions do not add a separate batch quota; large searches or page reads may still need to be split across calls.

Ready to actually ship your agent?

Connect your agent to Confluence with managed OAuth, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the Confluence Quickstart