Skip to Content

Use Arcade in Cursor

Setting Arcade up for yourself? The Arcade agent plugin installs in one command, needs no , and signs you in to each app in the browser. This guide is for pointing Cursor at a gateway you control, with your own list and your own end- identities.

Cursor is an client. Point it at an Arcade MCP Gateway URL over the Streamable HTTP transport and Cursor’s can call any you selected on that gateway — GitHub, Linear, Gmail, Slack, or any other toolkit from the Arcade integrations catalog, plus tools from your own custom MCP servers.

Outcomes

Connect Cursor to an Arcade Gateway.

Prerequisites

  1. Create an Arcade
  2. Get an Arcade API key
  3. Create an Arcade MCP Gateway and select the you want to use

Cursor currently does not refresh the OAuth tokens automatically. To set a persistent connection between Cursor and your , you should set the Authorization field to “Arcade Headers” in the dashboard.

Production end with their own identities? If your end users already sign in to Entra ID, Okta, Auth0, Clerk, or another OIDC provider, configure a User Source on your gateway. Arcade redirects each end user to your identity provider on sign-in and identifies them by an OIDC subject claim.

Set up Cursor

  1. Open the Command Palette (Cmd + Shift + P on macOS, Ctrl + Shift + P on Windows/Linux) and select Open Settings
  2. Click on the “New Server” button

Cursor will open the settings file, and you can add a new entry to the mcpServers object:

JSON
{ "mcpServers": { "mcp-arcade": { "url": "https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>" } } }

Try it out

  1. Open the chat pane (typically command-l)
  2. Make sure you are in mode
  3. Ask the to use a !

Pick which tools Cursor sees

A gateway is the filter that decides which Cursor can call. On the MCP Gateways dashboard , open your gateway’s Allowed Tools picker and search or filter across every server in scope — Arcade-hosted toolkits, remote MCP servers you registered, and your own Arcade-deployed MCP servers. Save the gateway and Cursor immediately sees the new tool list on its next request; no restart or client-side config change is needed.

Popular starting points for a Cursor gateway: GitHub, Linear, Gmail, Slack, Google Calendar, Notion, Jira, Confluence — plus any remote MCP server or custom MCP server you have registered. Browse the full integrations catalog for the rest.

Last updated on