Where it fits
Plaid developers monitoring Link conversion, usage and Item health in production.
- Check Link conversion rates for the last week.
- Diagnose why an Item connection failed.
- Compare usage metrics across integration versions.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with Plaid Developer Tools
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Reads a user's Link financial data, covering transactions, balances, and wallet sources, so an agent can answer questions about spending and about which source capabilities are available. Precomputed insights help with shopping preferences and preferred businesses. Typical requests include checking a balance, reviewing recent purchases, summarizing spending, listing connected accounts, or asking which accounts are linked.
Calculates key financial ratios and metrics from data in financial statements, for use in investment analysis.
Pull GitHub Copilot usage metrics for an organization or enterprise through the CLI and REST API.
No skills found
Try a different search term or clear the filters.
Install it in your client
Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.
- 01
Run this command in your terminal
This adds Plaid Developer Tools as a remote Streamable HTTP server in Claude Code.
Claude Codeclaude mcp add --transport http plaid-developer-tools https://api.dashboard.plaid.com/mcp/ --header "Authorization: Bearer YOUR_ACCESS_TOKEN" --scope project - 02
Send the credential
The provider expects the following header. Replace each placeholder with your own key or token before you connect.
Required headersAuthorization: Bearer YOUR_ACCESS_TOKEN - 03
Verify the connection
Run claude mcp list, or open /mcp in a Claude Code session.
Learn more about MCP in Claude Code
- 01
Run this command in your terminal
This adds Plaid Developer Tools as a remote Streamable HTTP server in Codex.
Codex# Add this to Codex MCP settings: [mcp_servers."plaid-developer-tools"] url = "https://api.dashboard.plaid.com/mcp/" [mcp_servers."plaid-developer-tools".headers] "Authorization" = "Bearer YOUR_ACCESS_TOKEN" - 02
Send the credential
The provider expects the following header. Replace each placeholder with your own key or token before you connect.
Required headersAuthorization: Bearer YOUR_ACCESS_TOKEN - 03
Verify the connection
Run codex mcp list, or open /mcp in a Codex session.
Learn more about MCP in Codex
- 01
Install with one click
This opens Cursor with the server pre-filled. Review the connection before accepting it.
Install in Cursor - 02
Send the credential
The provider expects the following header. Replace each placeholder with your own key or token before you connect.
Required headersAuthorization: Bearer YOUR_ACCESS_TOKEN - 03
Verify the connection
Open Cursor's MCP settings and enable the server if it is not active.
Learn more about MCP in Cursor
- 01
Install with one click
This opens VS Code with the server pre-filled. Review the connection before accepting it.
Install in VS Code - 02
Send the credential
The provider expects the following header. Replace each placeholder with your own key or token before you connect.
Required headersAuthorization: Bearer YOUR_ACCESS_TOKEN - 03
Verify the connection
Run MCP: List Servers from the Command Palette and start the server.
Learn more about MCP in VS Code
More clients, including project and global config files, are in the sidebar.
Endpoint and configuration
The installer uses the server name plaid-developer-tools. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
plaid-developer-toolsappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Check Link conversion rates for the last week. Check the result before you give the server more access.
- 3Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. The provider page was available when we checked.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
- The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider documentation
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
Plaid Developer Tools documentationhttps://plaid.com/docs/resources/mcp/