How to use Jira with Copilot Studio
You want Jira inside Copilot Studio so it can triage sprint work, prepare issue updates, move work into a sprint, and close the loop on completed work — without you copy-pasting between tabs. Here is the whole setup, once.
Create your Jira gateway
The gateway is the thing Copilot Studio connects to, and it is where you decide which Jira 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 Jira tools
In the dashboard, create a gateway and pick the Jira 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 Copilot Studio
Needs a Microsoft 365 subscription with access to Copilot Studio, plus an Arcade API key.
-
Add an MCP tool to your agent
In Copilot Studio, open your agent → Tools → Add a tool → Model Context Protocol → New tool.
-
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.
-
Authorize and try it out
Saving redirects you to Arcade to approve access. Then start a conversation and use your Jira tools — Arcade authorizes each service just in time.
Full Copilot Studio guide in the docs steps verified 2026-08-13
Try these Jira prompts
Copilot Studio can now act on your Jira account. Click a prompt to copy it.
Control write access so an agent can read issues without being able to update tickets, move sprint work, or add comments. Pair it with Contextual Access policies to require approval for changes that affect project status.