Plaid

Plaid

Official

Official Plaid MCP — developer sandbox tooling and dashboard diagnostics, not a live bank-data connector.

Score 74(?)PlaidMIT28Verified Top MCPs for Developer Tools →

Quick answer

What it does

AI Coding Toolkit: mock-data generation, documentation search, sandbox access tokens, and webhook simulation. Dashboard MCP: plaid_debug_item, plaid_get_link_analytics, plaid_get_usages, plaid_list_teams, plus usage guidance.

Best for

  • Building a Plaid integration with AI assistance
  • Generating sandbox/mock financial data for tests
  • Searching Plaid documentation from an agent
  • Debugging Items and Link conversion in production

Not for

  • Reading a live consumer's bank transactions or balances
  • Personal-finance dashboards over real accounts

Source: top-mcps.com/mcp/plaid — verified Sep 2026

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
      "mcpServers": {
        "plaid": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "https://api.dashboard.plaid.com/mcp/"
          ]
        }
      }
    }

    Claude Desktop launches stdio servers, so mcp-remote bridges to the hosted endpoint and opens the sign-in in your browser. On Pro, Max, Team and Enterprise you can skip the file: Settings → Connectors → Add custom connector → https://api.dashboard.plaid.com/mcp/. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    CLI or .mcp.json
    claude mcp add --transport http plaid https://api.dashboard.plaid.com/mcp/

    Then run /mcp inside Claude Code to finish the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    .cursor/mcp.json
    {
      "mcpServers": {
        "plaid": {
          "url": "https://api.dashboard.plaid.com/mcp/"
        }
      }
    }

    Global path: ~/.cursor/mcp.json. Cursor shows "Needs login" once it connects — click it to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    .vscode/mcp.json
    {
      "servers": {
        "plaid": {
          "type": "http",
          "url": "https://api.dashboard.plaid.com/mcp/"
        }
      }
    }

    VS Code uses the "servers" key. Run MCP: List Servers → Start Server and allow the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.codeium/windsurf/mcp_config.json
    {
      "mcpServers": {
        "plaid": {
          "serverUrl": "https://api.dashboard.plaid.com/mcp/"
        }
      }
    }

    Windsurf uses "serverUrl" for hosted servers. Open via Cascade → hammer icon → Configure. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    cline_mcp_settings.json
    {
      "mcpServers": {
        "plaid": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "https://api.dashboard.plaid.com/mcp/"
          ]
        }
      }
    }

    Bridged through mcp-remote. Open via the Cline sidebar → MCP Servers → Edit. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.continue/config.json
    {
      "experimental": {
        "modelContextProtocolServers": [
          {
            "transport": {
              "type": "streamable-http",
              "url": "https://api.dashboard.plaid.com/mcp/"
            }
          }
        ]
      }
    }

    Continue takes the hosted URL directly in the transport block. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    CLI
    codex mcp add plaid --url https://api.dashboard.plaid.com/mcp/

    Codex detects OAuth support and opens the browser to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ~/.config/zed/settings.json
    {
      "context_servers": {
        "plaid": {
          "command": {
            "path": "npx",
            "args": [
              "-y",
              "mcp-remote",
              "https://api.dashboard.plaid.com/mcp/"
            ]
          }
        }
      }
    }

    Bridged through mcp-remote under "context_servers". Settings live-reload on save. Authorization happens in the browser on first use (OAuth); no token goes in the config file.

    ChatGPT → Settings → Connectors (remote URL)
    {
      "name": "Plaid",
      "transport": "http",
      "url": "https://api.dashboard.plaid.com/mcp/"
    }

    Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled.

  2. 2

    Set required secrets

    No credentials required — this MCP runs over stdio without authentication.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope
Network
Sandbox
AI Coding Toolkit operates on sandbox/mock data only. Dashboard MCP authenticates with an OAuth token scoped to mcp:dashboard (client-credentials grant, 15-minute expiry).
Gotchas
  • Do not expect live bank-account access — that is a common misread of "Plaid MCP". These servers are for building and diagnosing integrations, not aggregating account data.
  • Dashboard MCP tokens expire after 15 minutes and must be refreshed; the toolkit is Python, so it needs a Python runtime rather than npx.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. developer tools work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-developer-tools
Compare Plaid against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Plaid MCP vs [QuickBooks Online MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/plaid
- top-mcps.com listing for QuickBooks Online
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Plaid MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/plaid (fetch https://top-mcps.com/mcp/plaid.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (no secrets) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.
  1. Refreshed install snippets and fact sheet; verified for 2026.

  2. Initial directory listing.

More Developer Tools MCPs

Other tools in the same category worth evaluating.

Official

Full GitHub API access: repos, PRs, issues, and code search.

git, github, repos, prs
5 minLow
GitLab

Full GitLab API access: repos, MRs, issues, pipelines, and registries.

git, gitlab, repos, mrs
5 minLow
Git
Official

Local Git operations: commit, diff, log, branch, and more.

git, local, commits, diff
2 minLow

Compared with Plaid

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Exploring Top MCPs for Developer Tools? See all Developer Tools MCPs →