How to use Gmail with Cursor
You want Gmail inside Cursor so it can clear a backlogged inbox, draft replies you would have written yourself, find the one thread you half-remember, and chase the things waiting on other people — without you copy-pasting between tabs. Here is the whole setup, once.
Create your Gmail gateway
The gateway is the thing Cursor connects to, and it is where you decide which Gmail 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 Gmail tools
In the dashboard, create a gateway and pick the Gmail 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 Gmail tools.
Full Cursor guide in the docs steps verified 2026-08-13
Get started with these Gmail prompts
Cursor can now act on your Gmail account. Click a prompt to copy it.
Thinking “this is one prompt injection away from my inbox leaking”? So do we. That is what Contextual Access policies are for — approval before anything is sent or deleted, redaction on the message bodies that never needed to reach the model.