How to use Cursor Agents with Cursor
You want Cursor Agents inside Cursor 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 Cursor 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 Cursor
Cursor does not refresh MCP OAuth tokens automatically. For a persistent connection, set Authorization to “Arcade Headers” on the gateway in the dashboard.
-
Open MCP settings
Command Palette (⌘⇧P / Ctrl+Shift+P) → Open MCP Settings, then click “New MCP Server”.
-
Add the gateway to mcpServers
{ "mcpServers": { "mcp-arcade": { "url": "https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>" } } } -
Try it out
Ask Cursor to use one of your Cursor Agents tools.
Full Cursor guide in the docs steps verified 2026-08-13
Try these Cursor Agents prompts
Cursor 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.