How to use Cursor Agents with Copilot Studio
You want Cursor Agents inside Copilot Studio so it can run coding tasks on reachable repositories, monitor cloud-agent runs and collect artifacts, iterate on an agent's pull request, and control the lifecycle of cloud agents — without you copy-pasting between tabs. Here is the whole setup, once.
Create your Cursor Agents gateway
The gateway is the thing Copilot Studio connects to, and it is where you decide which Cursor Agents 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 Cursor Agents tools
In the dashboard, create a gateway and pick the Cursor Agents 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 Cursor Agents tools — Arcade authorizes each service just in time.
Full Copilot Studio guide in the docs steps verified 2026-08-13
Try these Cursor Agents prompts
Copilot Studio can now act on your Cursor Agents account. Click a prompt to copy it.
Control which actions the agent can take before it starts or changes cloud coding runs. Pair it with Contextual Access policies so an agent can inspect runs and artifacts without being allowed to launch, cancel, archive, or delete agents.