Plaid Developer Tools
Read your own Plaid developer dashboard from an AI agent: Link conversion funnels, API usage, team lists and Item diagnostics. Not consumer bank data — Plaid says Claude has no access to it. Production only, one scope, mcp:dashboard.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Plaid Developer Tools via MCP
https://api.dashboard.plaid.com/mcp/sseWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Plaid Developer Tools Tools & Capabilities (4)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Production data only. Plaid documents no Sandbox mode. Your team must be approved for Production access with at least one product before the server works at all.
plaid_debug_item's response fields are undocumented. Plaid gives one sentence and no schema. We are not guessing at the field list; the Dashboard equivalent is the closest published proxy.- Item diagnostics concern real people. No balances or transactions, but institution, connection health, freshness and error state for a named end user's bank link — and lookup by your own
client_user_id. - Plaid calls it under active development. Its documentation warns that breaking changes may occur and that support is currently limited.
- Tokens expire in fifteen minutes. Long-running agents need refresh logic, or calls start failing with 401 mid-session.
- No RFC 9728 descriptor is published. Clients that discover scopes from the protected-resource document will find nothing; the RFC 8414 document at the host root is the only machine-readable declaration.
- The 401 carries no
www-authenticateheader, so a client relying on the challenge for discovery gets no hint about where to authenticate. - The directory transport and the documented transport differ. Anthropic lists SSE at
/mcp/sse; Plaid's docs name Streamable HTTP at/mcp/. SSE is the older MCP transport and some clients handle the two differently — if one path fails in your client, try the other. - We could not verify tool behaviour ourselves. The endpoint is gated, so no schemas and no safety annotations were readable. The read-only classification here is Plaid's documentation plus the single-scope evidence, not our observation of annotations.
- Prompts are unconfirmed. Anthropic's snapshot lists no prompt names, and the gated endpoint blocked our own
prompts/list. - Analytics are visible to every team member. Plaid documents Usage and Analytics as accessible regardless of permission level, so the Dashboard roles do not gate three of the four data tools.
Frequently asked questions
Can the Plaid MCP server read my end users' bank transactions?
No. Plaid's launch announcement states plainly that Claude does not have access to consumer financial data through this server. The four listed tools read your developer dashboard — Link conversion analytics, billable API usage, your team list, and Item diagnostics. Balances, transactions and account numbers are served by Plaid's separate product API, which this connector does not reach.
What does plaid_debug_item actually return?
Plaid documents it as diagnosing an Item using related metadata, without enumerating the fields. An Item is one end user's login at a financial institution, so the Dashboard equivalent shows institution identity, historical status, last update time, error codes and suggested fixes. That is metadata about an identifiable person's bank connection, even though no balances or transactions appear.
Does the Plaid MCP server work in the Sandbox environment?
No. Plaid's documentation states the Dashboard MCP server works with Production data only, and that your team must be approved for Production access with at least one Plaid product before you can use it. There is no Sandbox mode and no environment switch, so every answer an agent returns describes live production traffic and real linked Items.
Who on my Plaid team can use the MCP server?
Anyone the token represents, bounded by Plaid Dashboard permissions. Plaid states the integration limits a user to what they can already access in Plaid. The Overview, Status, Logs, Usage and Analytics pages are open to all team members regardless of permission level, so the analytics tools sit inside the least restricted part of the Dashboard.
Why does my Plaid MCP connection fail after fifteen minutes?
The access token expired. Plaid documents a fifteen-minute lifetime for Dashboard MCP access tokens, after which requests return HTTP 401 or a provider-specific authentication error. Call the token endpoint again with your refresh token to mint a replacement. Agents holding a long-running session need refresh logic rather than a single token fetched at startup.
Is the Plaid MCP server SSE or Streamable HTTP?
Both answers are current, for different URLs. Anthropic's directory lists the SSE endpoint from the May 2025 launch. Plaid's documentation now publishes a trailing-slash URL and tells you to choose Streamable HTTP if your client asks. Both paths answered our anonymous probe with HTTP 401 on 2026-08-19, so both are live.
Sources
- Plaid Dashboard MCP server documentation — https://plaid.com/docs/resources/mcp/ (fetched 2026-08-19 as Markdown via
https://plaid.com/docs/resources/mcp/index.html.md, the path named in Plaid's own docs index) · retrieved 2026-08-19 - Plaid OAuth API reference — https://plaid.com/docs/api/oauth/index.html.md (fetched 2026-08-19) · retrieved 2026-08-19
- Plaid teams and Dashboard permissions — https://plaid.com/docs/account/teams/index.html.md (fetched 2026-08-19) · retrieved 2026-08-19
- Plaid activity, logs and status, including the Item Debugger — https://plaid.com/docs/account/activity/index.html.md (fetched 2026-08-19) · retrieved 2026-08-19
- Plaid glossary, definition of an Item — https://plaid.com/docs/quickstart/glossary/index.html.md (fetched 2026-08-19) · retrieved 2026-08-19
- Plaid MCP launch announcement, source of the consumer-data statement — https://plaid.com/blog/plaid-mcp-ai-assistant-claude/index.html.md (fetched 2026-08-19) · retrieved 2026-08-19
- Plaid and Anthropic API announcement — https://plaid.com/blog/anthropic-api-mcp/index.html.md (fetched 2026-08-19) · retrieved 2026-08-19
- Plaid Item Debugger launch post — https://plaid.com/blog/item-debugger-institution-status/index.html.md (fetched 2026-08-19) · retrieved 2026-08-19
- Plaid docs machine index — https://plaid.com/docs/llms.txt and site index https://plaid.com/llms.txt (fetched 2026-08-19) · retrieved 2026-08-19
plaid.com/robots.txtallows/docs/and carries noContent-Signaldirective;/legacy-docs/,/docs-beta/and/new-plaid-docs/are disallowed and were not fetched (fetched 2026-08-19) · retrieved 2026-08-19- Live anonymous probe — 2026-08-19:
POSTandGETtohttps://api.dashboard.plaid.com/mcp/sseboth return HTTP 401{"error":"Unauthorized"}with nowww-authenticateheader · retrieved 2026-08-19 - Live RFC 9728 check — 2026-08-19: root and path-insert forms return
text/plain404s, the path-append form returns the same 401 as the endpoint; no descriptor is published · retrieved 2026-08-19 - Live RFC 8414 authorization-server metadata — https://api.dashboard.plaid.com/.well-known/oauth-authorization-server (fetched 2026-08-19;
scopes_supportedis["mcp:dashboard"]) · retrieved 2026-08-19 - Anthropic connector directory — https://claude.ai/directory/bacac1ad-ccb1-401e-a5d7-915da9742dce (snapshot 2026-08-16) · retrieved 2026-08-16
- Plaid support — https://support-my.plaid.com/hc/ · Legal and privacy — https://plaid.com/legal/
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Finance
- Developer
- Plaid Developer Tools
- Tools
- 4
- Domain
- api.dashboard.plaid.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.