# Plaid Dashboard MCP server

> Diagnose Plaid Items, review Link conversion data and check usage metrics from your AI assistant.

- Listing: https://mcp.tc/i/plaid
- Connect: use the server's own URL `https://api.dashboard.plaid.com/mcp/` (with your API key); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: API key
- Category: [Finance & Payments](https://mcp.tc/c/finance-payments)
- Vendor: Plaid
- Verified: yes, mcp.tc checked that this is the official server (https://mcp.tc/verify). It says who runs the server, not that it is safe.
- Homepage: <https://plaid.com/docs/resources/mcp/>

## About

The Plaid Dashboard MCP server gives an LLM application access to Production diagnostics and analytics from your Plaid account. The docs describe tools for debugging Items, reviewing Link conversion data and checking usage metrics.

It is a remote server hosted by Plaid at https://api.dashboard.plaid.com/mcp/ using Streamable HTTP. It works with Production data only, so your team needs Production access to at least one Plaid product. Authentication uses a bearer token from /oauth/token with the client\_credentials grant and the mcp:dashboard scope. Plaid notes the server is under active development and may have breaking changes.

## What it can do

- Debug Plaid Items in Production
- Review Link conversion data
- Check usage metrics
- Assess integration health

## Example prompts

- "Why is this Plaid Item failing to update?"
- "Show Link conversion data for the last month."
- "Check my Plaid usage metrics for this billing period."
- "Summarize the health of my Plaid integration."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http plaid https://api.dashboard.plaid.com/mcp/
```

2. Start Claude Code and type `/mcp`. **plaid** should show as connected.

Plaid Dashboard needs an API key. Plaid’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

### Claude Desktop

1. Custom connectors can’t send this server’s key header, so use the `mcp-remote` bridge. Open **Settings → Developer → Edit Config** and add:

`claude_desktop_config.json`:

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

2. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=plaid&config=eyJ1cmwiOiJodHRwczovL2FwaS5kYXNoYm9hcmQucGxhaWQuY29tL21jcC8ifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

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

Plaid Dashboard needs an API key. Plaid’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=plaid&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fapi.dashboard.plaid.com%2Fmcp%2F%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"plaid","type":"http","url":"https://api.dashboard.plaid.com/mcp/"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

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

Plaid Dashboard needs an API key. Plaid’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "plaid": {
      "serverUrl": "https://api.dashboard.plaid.com/mcp/"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

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

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.plaid]
url = "https://api.dashboard.plaid.com/mcp/"
```

Plaid Dashboard needs an API key. Plaid’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

### Gemini CLI

```bash
gemini mcp add --transport http plaid https://api.dashboard.plaid.com/mcp/
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

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

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://api.dashboard.plaid.com/mcp/`.

Plaid Dashboard needs an API key. Plaid’s docs say which header carries it; most servers use `Authorization: Bearer <YOUR_API_KEY>`.

## Details

- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-04

---
Source: https://mcp.tc/i/plaid (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report