Hosted MCP server/Finance Official

Official Plaid Developer Tools MCP server

Hosted at api.dashboard.plaid.com·Streamable HTTP

Plaid's remote MCP server gives developers Link conversion insights, usage metrics and Item diagnostics for their Plaid integrations. Authentication uses OAuth client credentials: request a token from /oauth/token with scope mcp:dashboard, send it as a Bearer token, and refresh it with grant_type=refresh_token when a request returns 401 after the 15-minute expiry. There is no browser sign-in or pop-up flow. The Dashboard MCP server works with Production data only, so the team must be approved for Production access and have at least one Plaid product enabled.

api.dashboard.plaid.com Streamable HTTP Client-credentials Bearer token (no browser sign-in) Source checked Oct 31, 2026 Server not checked yet Reviewed 2026-11-16
About

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.

Setup

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.

All client guides
  1. 01

    Run this command in your terminal

    This adds Plaid Developer Tools as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http plaid-developer-tools https://api.dashboard.plaid.com/mcp/ --header "Authorization: Bearer YOUR_ACCESS_TOKEN" --scope project
  2. 02

    Send the credential

    The provider expects the following header. Replace each placeholder with your own key or token before you connect.

    Required headers
    Authorization: Bearer YOUR_ACCESS_TOKEN
  3. 03

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://api.dashboard.plaid.com/mcp/
Host
api.dashboard.plaid.com · /mcp/
Transport
Streamable HTTP
Authentication
Client-credentials Bearer token (no browser sign-in)
Server name
plaid-developer-tools
Listing type
Official provider listing

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.

Verification

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.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that plaid-developer-tools appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Check Link conversion rates for the last week. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

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.

Provider page available on Oct 31, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

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.
Safety

Before you connect

Remote means provider access
  • 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.
Review path

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.

Reference

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/