How to set up the Plaid MCP server

Plaid's Dashboard MCP server provides diagnostics and analytics for a Plaid integration, including Item debugging, Link analytics, and usage metrics. It works with Production data only. It is not a way to expose customer bank data or to use Sandbox test credentials.

This guide covers the credential setup and connection options described in Plaid's Dashboard MCP server documentation. Treat every client secret, access token, and refresh token as a secret.

Prerequisites

Before connecting an MCP client, make sure that:

• Your Plaid team has Production access and at least one Plaid product approved.
• You have a Production client ID and Production secret for the intended Plaid team.
• The credential is stored in a secret manager or other secure location; do not include it in chat prompts, source control, or support tickets.

Plaid's Dashboard MCP server documentation is authoritative on current availability and requirements.

Recommended: Create an MCP access token

Create an OAuth access token using the client-credentials grant and the mcp:dashboard scope. Use Production credentials; Sandbox and Development credentials do not work with the Dashboard MCP server.

curl -X POST https://production.plaid.com/oauth/token \  -H 'Content-Type: application/json' \  -d '{    "client_id": "YOUR_PRODUCTION_CLIENT_ID",    "client_secret": "YOUR_PRODUCTION_SECRET",    "grant_type": "client_credentials",    "scope": "mcp:dashboard"  }'

The response contains an access_token for MCP requests and a refresh_token that can renew it. Store both securely.

Alternative: Connect from an MCP client

Use this approach when your MCP client can connect directly to a remote Streamable HTTP server. Configure the connection with:

• Server URL: https://api.dashboard.plaid.com/mcp/
• Transport: Streamable HTTP
• Authorization header: Bearer <access_token>

The bearer token expires after 15 minutes. Refresh it through Plaid's /oauth/token endpoint before it expires, using the returned refresh token. A static token is appropriate only for a short-lived test.

Alternative: Connect through a model-provider API

Use this approach when your backend calls a model provider API and supplies Plaid's MCP server as a remote tool. Your backend is responsible for creating or refreshing the Plaid MCP token and passing it to the provider for each request.

• OpenAI Responses API: pass the token in the remote MCP tool's authorization field.
• Anthropic Messages API: pass the token in the MCP connector's authorization_token field.

See Plaid's remote MCP integration examples for current provider-specific request shapes.

Verify Plaid MCP

Use this checklist to confirm the MCP server has the intended Production access.

• Generate a fresh token and connect to the server.
• Confirm that Plaid MCP tools are discovered.
• Run plaid_list_teams or another approved read-only diagnostic.
• Confirm that the returned teams, Item diagnostics, analytics, and usage data are within the approved Plaid team boundary.
• Confirm that the connection does not expose customer access tokens, account numbers, or other secrets in logs or prompts.

Troubleshooting

Client ID, Production secret, MCP access token, refresh token, and Plaid Item ID are distinct values. Do not substitute one for another.

• Access is denied or the server is unavailable: confirm that the Plaid team has Production access and at least one approved product.
• Authentication fails immediately: confirm that the token was created by https://production.plaid.com/oauth/token with grant_type: client_credentials and scope: mcp:dashboard.
• Authentication starts failing after a working test: the 15-minute access token has expired. Generate or refresh a token, then reconnect.
• The expected data is missing: the MCP server is intended for Dashboard diagnostics and analytics, not direct access to customer financial data or Sandbox items.

For the current server URL, token lifecycle, and available tools, refer back to Plaid's Dashboard MCP server documentation.