# Plaid Dashboard MCP Server [Official] [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://plaid.com/docs/resources/mcp/  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/plaid-dashboard-mcp

## Description
Plaid's official hosted MCP server for the Plaid Dashboard. Gives agents Production diagnostics and analytics: debugging Items, Link conversion analytics and usage metrics. Needs Production access and an OAuth token with the mcp:dashboard scope.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Plaid Dashboard MCP Server does

Plaid Dashboard MCP Server connects MCP-compatible agents to Plaid Dashboard capabilities. Its focus is operational analysis of Plaid integrations rather than general-purpose financial data access. The supported areas are Production diagnostics, Plaid Item debugging, Link conversion analytics, and usage metrics.

This makes the server relevant for developers and operations teams investigating issues in a live Plaid environment, reviewing how users move through Link, or checking usage-related metrics. It is hosted by Plaid, so the server is intended to be accessed as a remote service rather than deployed as a local MCP process.

## How it works

An MCP client connects to Plaid’s hosted MCP endpoint and uses an OAuth-authenticated connection to request Dashboard information. Access is tied to Plaid Production and to an OAuth token carrying the `mcp:dashboard` scope.

The agent can then work with the server’s Dashboard-focused capabilities, including diagnostic information, Item debugging data, Link conversion analytics, and usage metrics. The available information is therefore governed by the permissions and environment associated with the authorized Plaid account.

## Setup and configuration

Before using the server, obtain access to the Plaid Production environment and authorize the connection with an OAuth token that includes the `mcp:dashboard` scope. The service is hosted by Plaid, so local server installation is not part of the stated setup model.

Authentication is an important part of configuration: an MCP client must be able to use the required OAuth token when connecting. The token’s scope should be checked if Dashboard capabilities are unavailable, and the connection should target the Plaid-hosted service rather than a locally started server.

## Tools and capabilities

The server covers four main Dashboard use cases:

- Inspect Production diagnostics.
- Debug Plaid Items.
- Review Link conversion analytics.
- Examine usage metrics.

These capabilities let an agent help investigate operational behavior and measure Link-related activity from Plaid Dashboard data. The server is suited to analysis and troubleshooting workflows that already have access to Plaid Production.

## Limitations and notes

Access requires Plaid Production access and an OAuth token with the `mcp:dashboard` scope. Without those prerequisites, an agent cannot use the Dashboard capabilities described here. The service is specifically centered on Plaid Dashboard diagnostics and analytics; it should not be treated as a general MCP interface for unrelated Plaid functionality.

Because the server is hosted, deployment and runtime management are handled differently from a locally installed MCP server. The key integration concerns are MCP client connectivity, OAuth authorization, the required scope, and access to the Production environment.

_Full upstream README: https://allmcps.com/mcp/plaid-dashboard-mcp/readme_