How to use YugabyteDB with Cursor
You want YugabyteDB inside Cursor so it can map the database before writing queries, investigate a data issue, check data quality across related tables, and answer an operational database question — without you copy-pasting between tabs. Here is the whole setup, once.
Create your YugabyteDB gateway
The gateway is the thing Cursor connects to, and it is where you decide which YugabyteDB 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 YugabyteDB tools
In the dashboard, create a gateway and pick the YugabyteDB 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 YugabyteDB tools.
Full Cursor guide in the docs steps verified 2026-08-13
Try these YugabyteDB prompts
Cursor can now act on your YugabyteDB account. Click a prompt to copy it.
Use a read-only database credential so an agent can inspect schemas and query data without changing records. Pair it with Contextual Access policies to limit which database access the agent can use.