Sign in Book a demo
Copilot Studio

How to use Confluence with Copilot Studio

You want Confluence inside Copilot Studio so it can find and summarize project decisions, audit a documentation space, assemble a project brief, and publish an approved project update — without you copy-pasting between tabs. Here is the whole setup, once.

Create your Confluence gateway

The gateway is the thing Copilot Studio connects to, and it is where you decide which Confluence tools an agent may use. You create it once and every client reuses it.

  1. Create an Arcade account

    Sign up and open the dashboard. The free tier is enough to follow this through.

  2. Create an MCP Gateway and select your Confluence tools

    In the dashboard, create a gateway and pick the Confluence tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.

  3. Copy your gateway URL

    Every client below needs it. 

    https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>

Create a Confluence gateway Opens the gateway builder in your Arcade dashboard.

Connect the gateway to Copilot Studio

Heads up

Needs a Microsoft 365 subscription with access to Copilot Studio, plus an Arcade API key.

  1. Add an MCP tool to your agent

    In Copilot Studio, open your agent → Tools → Add a tool → Model Context Protocol → New tool.

  2. Point it at your gateway

    Give the server a name and description, put your gateway URL in Server URL, set Authentication to OAuth 2.0 and Type to Dynamic discovery.

  3. Sign in to Arcade

    Saving redirects you to Arcade. Approve access there.

  4. Try it out

    Start a conversation with your agent and ask it to use one of your Confluence tools. The first time it calls a Confluence tool, Arcade replies with an authorization link. Open it, sign in to Confluence and approve access, then ask again. You do this once per account.

Full Copilot Studio guide in the docs steps verified 2026-08-13

Get started with these Confluence prompts

Copilot Studio can now act on your Confluence account. Copy a prompt and paste it in.

find and summarize project decisions

Search Confluence for pages about the project decisions made in the last six months. Read the most relevant pages, group the decisions by project, and return the decision, date, owner, and source page title for each one.

audit a documentation space

Review the pages in the product documentation space and identify pages that are outdated, duplicated, or missing an owner. Return the page titles, the reason for each finding, and a suggested next step. Do not change any pages.

assemble a project brief

Find the project brief, roadmap, meeting notes, and decision pages for the launch project. Read the relevant content and return a concise brief with goals, milestones, open risks, decisions, and links or page titles for each source.

publish an approved project update

Create a new page at the root of the project space titled "Weekly project update" with the status, completed work, next steps, risks, and decisions from the source pages I identify. Show me the proposed content and ask for approval before creating or changing anything.

Control which spaces an agent can read or change, and require approval before it creates, renames, or edits a page. Pair it with Contextual Access policies so an agent can search documentation without being able to alter it.

Ready to actually ship your agent?

Free to start. Ready for enterprise when you are.

Try Free Book a demo