Cursor

Cursor supports MCP servers through a mcp.json config file. The shape is the same as Claude Code’s .mcp.json, so the same Bearer-token snippet works in both.

The Connect Your AI window in PlaidCloud’s header toolbar offers an Install in Cursor one-click link that adds the server through an OAuth sign-in, no config file needed. Try that first. The Bearer-token config below is the setup this page documents in full, and the fallback if the one-click link doesn’t add the server or Cursor isn’t installed.

Setup

1. Get a Bearer token by visiting https://<your-workspace>.plaid.cloud/mcp/setup/token in a browser where you’re signed into PlaidCloud.

2. Open Cursor’s MCP config:

   • Project-scoped: create .cursor/mcp.json in your project root.
   • User-scoped (all projects): create ~/.cursor/mcp.json in your home directory.

3. Add the PlaidCloud server:

   {
     "mcpServers": {
       "plaidcloud": {
         "url": "https://<your-workspace>.plaid.cloud/mcp",
         "headers": {
           "Authorization": "Bearer eyJhbGc…"
         }
       }
     }
   }

4. Open Cursor’s Settings → MCP to verify the server is connected. If it shows an error, see Troubleshooting.

Using the Tools

In Cursor’s Composer or chat panel, you can prompt the agent in plain English (“describe the structure of project Q4 Forecast”) and it will pick the appropriate plaidcloud_* tool. Tool calls and responses appear inline — review mutating operations before approving.

Refreshing the Token

When the token expires, reload https://<your-workspace>.plaid.cloud/mcp/setup/token and paste the new value into mcp.json. Cursor picks up the change without a full restart — toggle the server off/on in Settings → MCP if needed.

Multiple Tenants

Repeat the entry under a different name:

{
  "mcpServers": {
    "plaidcloud-prod": { "url": "https://prod.plaid.cloud/mcp", "headers": { "Authorization": "Bearer …" } },
    "plaidcloud-dev":  { "url": "https://dev.plaid.cloud/mcp",  "headers": { "Authorization": "Bearer …" } }
  }
}