Affinity
Search your CRM, prep for meetings and update deal records from your AI assistant.
Read your own Plaid developer dashboard: Link funnels, API usage, team lists, Item diagnostics.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Plaid Developer Tools MCP server connects your Plaid developer dashboard to Claude, ChatGPT or any MCP-compatible agent. It reads Link conversion funnels, billable API usage, your team list and diagnostics for a single Item. It is not a route to consumer bank data — Plaid says Claude cannot reach that through this server.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
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.client_user_id.www-authenticate header, so a client relying on the challenge for discovery gets no hint about where to authenticate./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.prompts/list.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.
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.
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.
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.
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.
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.
https://plaid.com/docs/resources/mcp/index.html.md, the path named in Plaid's own docs index) · retrieved 2026-08-19plaid.com/robots.txt allows /docs/ and carries no Content-Signal directive; /legacy-docs/, /docs-beta/ and /new-plaid-docs/ are disallowed and were not fetched (fetched 2026-08-19) · retrieved 2026-08-19POST and GET to https://api.dashboard.plaid.com/mcp/sse both return HTTP 401 {"error":"Unauthorized"} with no www-authenticate header · retrieved 2026-08-19text/plain 404s, the path-append form returns the same 401 as the endpoint; no descriptor is published · retrieved 2026-08-19scopes_supported is ["mcp:dashboard"]) · retrieved 2026-08-19Connect Plaid Developer Tools once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.