Plaid Dashboard MCP server
Endpoint: https://api.dashboard.plaid.com/mcp/ · Authentication: Bearer token
Reads Plaid Dashboard diagnostics, Item health, Link conversion, and usage analytics for a Production Plaid team. Requires a bearer access token obtained with the team's Plaid client credentials.
How do I authenticate?
Create a scoped provider token and supply it using the credential header and value format documented in the client setup below. Keep credentials out of shared URLs and logs.
Authentication and connection guideConnection specification
- Remote endpoint
https://api.dashboard.plaid.com/mcp/- Live-validated endpoint
https://api.dashboard.plaid.com/mcp- Browser access
- Not yet measured
- Declared MCP transport
- Streamable HTTP
- Live-validated MCP transport
- Not yet verified — Latest validation did not verify a transport
- Declared authentication
- Bearer token
- Detected authentication
- Bearer token detected or retained from publisher evidence
- Protocol lifecycle
- Not yet negotiated
- Required header
Authorization— Access token from /oauth/token with scope mcp:dashboard: Bearer <PLAID_MCP_ACCESS_TOKEN>- Category
- Finance
Product documentation · Official listing documentation
Provider guidance
- Works with Production data only; the team must be approved for Production access with at least one Plaid product.
More Finance MCP servers · Browse all MCP servers · Test this endpoint in the MCP Playground
Connect it
Live-validated endpoint: https://api.dashboard.plaid.com/mcp · Streamable HTTP. Bearer token authentication uses a named environment placeholder.
Agent prompt for Claude Code or Codex
Add the Plaid Dashboard MCP server to my MCP client configuration and verify that it works.
What it is: Reads Plaid Dashboard diagnostics, Item health, Link conversion, and usage analytics for a Production Plaid team. Requires a bearer access token obtained with the team's Plaid client credentials.
Server URL: https://api.dashboard.plaid.com/mcp
Transport: Streamable HTTP (remote MCP server, no local install).
Authentication: Bearer token. Bearer token authentication uses a named environment placeholder.
Tools: not yet observed by mcptest; tools/list will show them.
Reference: https://mcptest.io/servers/plaid-dashboard/
Steps:
1. Work out which MCP client I use (Claude Code, Codex, Cursor, VS Code or another) and add the server under the name "plaid-dashboard" in that client's MCP configuration, user scope unless I ask otherwise.
Claude Code: claude mcp add --transport http --scope user --header 'Authorization: Bearer '"${PLAID_MCP_ACCESS_TOKEN}" 'plaid-dashboard' 'https://api.dashboard.plaid.com/mcp'
Codex: codex mcp add 'plaid-dashboard' --url 'https://api.dashboard.plaid.com/mcp' --bearer-token-env-var 'PLAID_MCP_ACCESS_TOKEN'
Other clients: use the setup for that client on the reference page.
2. Never write a credential value into a file that could be committed; reference an environment variable or the client's secret store, and ask me for any value you need.
3. Verify: connect to the server and call tools/list. Confirm the tools above are listed, and report any sign-in step I still have to complete.Claude Code setup
Run in a terminal. This user-scoped entry is available across projects.
claude mcp add --transport http --scope user --header 'Authorization: Bearer '"${PLAID_MCP_ACCESS_TOKEN}" 'plaid-dashboard' 'https://api.dashboard.plaid.com/mcp'- Store PLAID_MCP_ACCESS_TOKEN in your operating system keychain, secret manager, or protected environment; never commit the value. The Authorization header syntax is Bearer <PLAID_MCP_ACCESS_TOKEN>.
Codex CLI setup
Run in a terminal; Codex stores the entry in ~/.codex/config.toml.
codex mcp add 'plaid-dashboard' --url 'https://api.dashboard.plaid.com/mcp' --bearer-token-env-var 'PLAID_MCP_ACCESS_TOKEN'- Store PLAID_MCP_ACCESS_TOKEN in your operating system keychain, secret manager, or protected environment; never commit the value. The Authorization header syntax is Bearer <PLAID_MCP_ACCESS_TOKEN>.
Cursor setup
Add to .cursor/mcp.json for this project, or ~/.cursor/mcp.json for all projects.
{
"mcpServers": {
"plaid-dashboard": {
"url": "https://api.dashboard.plaid.com/mcp",
"headers": {
"Authorization": "Bearer ${env:PLAID_MCP_ACCESS_TOKEN}"
}
}
}
}- Store PLAID_MCP_ACCESS_TOKEN in your operating system keychain, secret manager, or protected environment; never commit the value. The Authorization header syntax is Bearer <PLAID_MCP_ACCESS_TOKEN>.
VS Code setup
Add to .vscode/mcp.json, or run “MCP: Open User Configuration” for a private user-level entry.
{
"servers": {
"plaid-dashboard": {
"type": "http",
"url": "https://api.dashboard.plaid.com/mcp",
"headers": {
"Authorization": "Bearer ${input:plaid_mcp_access_token}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "plaid_mcp_access_token",
"description": "PLAID_MCP_ACCESS_TOKEN for Plaid Dashboard",
"password": true
}
]
}- VS Code requests PLAID_MCP_ACCESS_TOKEN as a masked input; use a secret manager and do not put a default value in mcp.json. The Authorization syntax remains Bearer <PLAID_MCP_ACCESS_TOKEN>.
Claude setup
Add the endpoint above in Claude:
- Customize > Connectors > Add custom connector
- Team/Enterprise: Organization settings > Connectors > Add > Custom > Web
Claude Desktop setup
Add the endpoint above in Claude Desktop:
- Remote: Customize > Connectors (same as claude.ai)
- Local: Settings > Developer > Edit Config, or Settings > Extensions for .mcpb files
~/Library/Application Support/Claude/claude_desktop_config.json(macOS) or%APPDATA%\Claude\claude_desktop_config.json(Windows), local servers only
ChatGPT setup
Add the endpoint above in ChatGPT:
- ChatGPT web: Plugins > Add custom MCP server, then configure authentication and accept the risk warning
Windsurf setup
Add the endpoint above in Windsurf:
~/.config/devin/mcp_config.json(%APPDATA%\devin\mcp_config.jsonon Windows),serverUrlorurl- Cascade panel > ... > MCPs > Open MCP config file
Gemini CLI setup
Add the endpoint above in Gemini CLI:
gemini mcp add --transport http <name> <url>~/.gemini/settings.json(user) or.gemini/settings.json(project),mcpServers
MCP SDK setup
Add the endpoint above in MCP SDK:
- Programmatic:
new Client(...).connect(new StreamableHTTPClientTransport(url))
Notes for every client
- Provider guidance: Works with Production data only; the team must be approved for Production access with at least one Plaid product.
Client compatibility
| Client | Status | Why |
|---|---|---|
| Claude Code | Supported | Claude Code supports Streamable HTTP servers and bearer-token headers. |
| Codex | Supported | Codex supports Streamable HTTP servers and bearer-token headers. |
| Cursor | Supported | Cursor supports Streamable HTTP servers and bearer-token headers. |
| VS Code | Supported | VS Code supports Streamable HTTP servers and bearer-token headers. |
| Claude | Partial | Claude supports bearer-token headers only in limited availability. Request-header authentication is in beta and available to a limited set of organizations. |
| Claude Desktop | Partial | Claude Desktop supports bearer-token headers only in limited availability. Request-header authentication is in beta and available to a limited set of organizations. |
| ChatGPT | Not supported | ChatGPT does not support bearer-token headers. Only the OAuth-issued token is sent; ChatGPT cannot present custom API keys. |
| Windsurf | Supported | Windsurf supports Streamable HTTP servers and bearer-token headers. |
| Gemini CLI | Supported | Gemini CLI supports Streamable HTTP servers and bearer-token headers. |
| MCP SDK | Supported | MCP SDK supports Streamable HTTP servers and bearer-token headers. |
Computed from this server's validated transport, protocol and authentication against documented client support. Checks the catalog has not observed are not counted.
Latest validation evidence
- Validation status
- Online when last tested
- Validation checked at
- Oct 26, 2026 at 11:06 AM
- Validation detail
- Authentication challenge at https://api.dashboard.plaid.com/mcp returned HTTP 401; endpoint was reachable but did not complete an MCP probe; authentication bearer-token
Tool inventory
The catalog validator lists tools only on servers that answer without credentials. Plaid Dashboard asks for a bearer token first, so its tools, resources and prompts were not observed. Connect in the Playground with your own credentials to list them.