GitHub Copilot

How to use Confluence with GitHub Copilot

You want Confluence inside GitHub Copilot 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 GitHub Copilot connects to, and it is where you decide which Confluence tools an agent may use. You create it once and every client reuses it.

Create an Arcade account

Sign up and open the dashboard. The free tier is enough to follow this through.
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.
Copy your gateway URL

Every client below needs it.
https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>

Connect the gateway to GitHub Copilot

Heads up

JetBrains IDEs do not support remote MCP servers with Dynamic Client Registration — configure the gateway as “Arcade Headers” in the dashboard first. Setup also differs on Visual Studio, Eclipse and Xcode; check the docs for yours.

In VS Code

Copilot picks up MCP servers configured in VS Code automatically, so follow the VS Code steps and you are done.
In JetBrains IDEs

Copilot icon → Open Chat → Agent mode → tools icon → “+ Add More Tools…”, which opens mcp.json.

Add the gateway with Arcade Headers

{
  "servers": {
    "mcp-arcade": {
      "url": "https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>",
      "requestInit": {
        "headers": {
          "Authorization": "Bearer {arcade_api_key}",
          "Arcade-User-ID": "{arcade_user_id}"
        }
      }
    }
  }
}

Try it out

Open Copilot Chat in Agent mode 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.

Get started with these Confluence prompts

GitHub Copilot 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.

How to use Confluence with GitHub Copilot

Create your Confluence gateway

Create an Arcade account

Create an MCP Gateway and select your Confluence tools

Copy your gateway URL

Connect the gateway to GitHub Copilot

In VS Code

In JetBrains IDEs

Add the gateway with Arcade Headers

Try it out

Get started with these Confluence prompts

Ready to actually ship your agent?