How to use MongoDB with Cursor
You want MongoDB inside Cursor so it can investigate records across collections, explore an unfamiliar database, analyze operational trends, and validate records before a migration — without you copy-pasting between tabs. Here is the whole setup, once.
Create your MongoDB gateway
The gateway is the thing Cursor connects to, and it is where you decide which MongoDB 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 MongoDB tools
In the dashboard, create a gateway and pick the MongoDB 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 MongoDB tools.
Full Cursor guide in the docs steps verified 2026-08-13
Try these MongoDB prompts
Cursor can now act on your MongoDB account. Click a prompt to copy it.
Use a read-only MongoDB credential scoped to the databases and collections the agent needs. Pair it with Contextual Access policies so an agent can inspect approved collections without receiving broader database access.