plaid-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_itemsA | List every Plaid item linked via the plaid CLI. |
| get_itemB | Get one linked Plaid item and the accounts it contains. |
| get_balancesB | Get current balances for one or all linked Plaid items. |
| list_transactionsC | List transactions for a date range (default: last 30 days). |
| sync_transactionsB | Incrementally sync transactions using Plaid's cursor-based sync. |
| check_item_healthA | Check whether one or all linked Plaid items are healthy or need re-authentication. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct resource and action: listing items, retrieving a single item, fetching balances, listing transactions, syncing transactions, and checking health. There is no overlap in their purposes, and the descriptions make the boundaries clear.
All tool names follow a consistent verb_noun pattern: list_items, get_item, get_balances, list_transactions, sync_transactions, check_item_health. No mixed conventions or vague verbs.
Six tools is a well-scoped set for a Plaid MCP server. Each tool covers a core operation needed to interact with linked items, balances, transactions, and health, without unnecessary redundancy.
The set covers listing, retrieving, and updating (via sync) core Plaid data, along with health checks. Minor gaps exist (e.g., no explicit unlink item or transaction detail tool), but the main workflows are fully supported.