Claude Plaid Developer Tools connectorWhat Claude can do in your Plaid Developer Tools account.
The Claude Plaid Developer Tools connector exposes 4 tools: 4 read, 0 write. Claude pulls Link conversion figures, usage volumes and Item diagnostics from your Plaid dashboard while it answers. Here is what it sees, what it cannot touch, and the one requirement Plaid sets first.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can read your Plaid dashboard
Instead of opening the Plaid Dashboard, picking a team and clicking through reports, you ask Claude in plain words. It finds the right team, fetches the numbers and explains them in the reply. Everything stays on the reading side: the connector reports on your integration, it does not reconfigure it.
Spot where users drop out of Link. Plaid describes plaid_get_link_analytics as returning Link funnel, conversion and error metrics, so Claude can put those figures in front of you and show where people left the flow.
Explain a broken bank connection. With plaid_debug_item, Claude diagnoses one Item, meaning one linked financial account, from the metadata Plaid keeps around it.
Keep an eye on volume. plaid_get_usages returns product usage metrics and API request volumes, read back in the reply.
What it will not do: none of the 4 tools creates, edits or deletes anything in Plaid, and nothing runs on its own when a metric moves. Claude only acts while it is answering you. Plaid also ships a separate local toolkit for development work (mock data, Sandbox tokens, webhook simulation); those tools are not part of this connector. To schedule reports or alerts, look at an automation platform instead, starting from our Integrations hub.
Five words before you connect
Claude's vocabulary for this connector, in one minute.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work on it while it answers you.
- Tool
- One named thing the connector lets Claude do. Claude picks the ones it needs by itself; the directory lists them by name.
- Authorization
- Plaid's own sign-in screen, where you hand Claude the access it will use. Granted once per person, and it can be withdrawn.
- Approval
- The confirmation Claude waits for before doing something that changes an account, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on, the piece that lets an assistant talk to an outside service like Plaid.
Connect Plaid Developer Tools to Claude in three steps
- 01
Find the connector
Open Claude's settings, go to Customize then Connectors, and look for Plaid Developer Tools in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch it on for the organisation before members can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Plaid in the window Plaid opens itself. If the link breaks later, use Disconnect and connect again. The window belongs to the remote server Plaid hosts for this connector.
- 03
Read the authorization screen
Read Plaid's authorization screen before you accept. It belongs to Plaid, not to Claude, and it sets what the access covers. You can also withdraw that access later from the Plaid side.
The 4 tools, sorted by what they do
Plaid Developer Tools gives Claude 4 tools: 4 that read your account, 0 that change something in it.
All four read from your Plaid dashboard, and Plaid describes each one. Tool names stay exactly as Claude shows them.
- 4 read
What Claude reads (4)
4 toolsFour tools that look at your integration's data without changing it.
plaid_debug_item
Given one Item, meaning one end user's linked financial account, Claude examines the metadata Plaid keeps around it and uses that to diagnose why it misbehaves. Plaid lists Item debugging among the Production diagnostics this server provides.
plaid_get_link_analytics
Fetches Link metrics in three families, as Plaid names them: the funnel, the conversion figures and the errors met along the way. Plaid presents this as reviewing Link conversion data.
plaid_get_usages
Returns product usage metrics together with API request volumes, the two figures Plaid attaches to this tool. Plaid groups it with the usage checks of its Dashboard server.
plaid_list_teams
Lists the Plaid teams available to the access token granted when you connected. The list stops where that access stops: a team outside it does not appear.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. With this connector the question rarely comes up, since every listed tool only reads.
On Team and Enterprise, workspace owners decide whether a member may let some actions through without being asked each time. They can also limit what a connector may do across the whole organisation, for instance keep reading and close writing, and nobody overrides that from their own account. Claude works with the rights of the person who connected and nothing more: a Plaid team you cannot open, it cannot open either. The official tool-by-tool read or write labels only show inside a connected account's settings, never on a public page.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. For this connector, as for the others, that answer is published nowhere.
What is published is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organisation before each member signs in. For the current state of this one, check its sheet in the official directory. Worth knowing: only Plaid documents this connector; no Claude help article covers it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it replies to you; nothing fires when conversion falls or an Item fails.
The tool list is an observed floor rather than a guarantee. The directory's verification badge is not a security audit either, and Anthropic states on every sheet that it does not choose the tools a publisher exposes or vouch that they behave as described. Connect what comes from a publisher you trust, here Plaid itself. Plaid adds its own warnings, summarised below.
Last point: Plaid is the only source for everything on this page about the connector itself, since no Claude help article covers it.
Need help connecting Plaid Developer Tools to Claude?
A person reads every message.
