Sign in Book a demo
Copilot Studio

How to use GitHub with Copilot Studio

You want GitHub inside Copilot Studio so it can review pull requests and assign follow-up work, triage repository issues, make a targeted repository change, and prepare and merge a pull request — without you copy-pasting between tabs. Here is the whole setup, once.

Create your GitHub gateway

The gateway is the thing Copilot Studio connects to, and it is where you decide which GitHub 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 GitHub tools

    In the dashboard, create a gateway and pick the GitHub 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 GitHub 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 GitHub tools. The first time it calls a GitHub tool, Arcade replies with an authorization link. Open it, sign in to GitHub and approve access, then ask again. You do this once per account.

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

Try these GitHub prompts

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

review pull requests and assign follow-up work

Review the open pull requests awaiting my review. Summarize the changed files, commits, review comments, and blocking issues, then recommend reviewers or follow-up owners. Do not merge anything, and return a concise action list.

triage repository issues

List the open issues in the repository I name, group them by urgency and topic, and identify duplicates or issues missing enough detail to act on. Suggest labels and return the issue numbers with your recommendations, but do not change anything.

make a targeted repository change

Find the repository and file I specify, inspect the surrounding code, and propose the smallest change needed to fix the described problem. Show the exact file and lines you would update, then wait for my approval before writing anything.

prepare and merge a pull request

Find the branch or changes I describe, inspect the commits and changed files, and prepare a pull request with a clear title and summary. Check whether it is ready to merge and return the status, reviewers, and blocking comments; do not merge it.

Control repository access and require approval before an agent creates files, merges pull requests, or changes labels with Contextual Access policies.

Ready to actually ship your agent?

Free to start. Ready for enterprise when you are.

Try Free Book a demo