How to use Jira with Cursor
You want Jira inside Cursor 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 Cursor 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 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 Jira tools.
Full Cursor guide in the docs steps verified 2026-08-13
Try these Jira prompts
Cursor 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.