## Plaid integration

Plaid is a financial data network that lets applications connect to users' bank accounts.

Agen.co connects to Plaid through Plaid's own hosted **Dashboard MCP server** as an **Official** connector. This isn't a connector for end-user bank data — it gives agents diagnostics and analytics about your own Plaid integration: debugging Items, reviewing Link conversion, and checking usage.

Prerequisites
- A Plaid Dashboard account, signed in when you authorize the connector.
- Your Plaid team must be approved for Production access with at least one Plaid product. The Dashboard MCP server works with Production data only — it has no Sandbox mode.
- No app needs to be registered with Plaid — the MCP server registers Agen.co as a client automatically, so there is no Client ID or Client Secret to copy.


### Connect Plaid in Agen.co

1. In the Agen.co portal, go to **Connectors** → **My connectors** and click **Add connector**.
2. In the **Select connector** drawer, search for `Plaid` and select it. The **Add Plaid** panel opens.
3. Fill in the field:
| Field | Required | Description |
|  --- | --- | --- |
| **Instance Slug** | Yes | Prefixes each imported tool as `slug__tool`, so several instances of the connector can coexist. Prefilled with `plaid`. Use lowercase kebab-case. You can change it later from the connector's settings. |
4. Click **Connect**. Plaid opens in a new tab, and the panel shows **Waiting for authorization — complete it in the opened tab…**
5. Sign in to the Plaid Dashboard if prompted. On the **MCP OAuth Client is requesting access** screen, which lists viewing teams, Item health and issues, and Link analytics and usage metrics, check the redirect host shown in the details box, then click **Approve**. The button sits at the bottom of the screen — scroll down if you don't see it, and click it again if the first click doesn't register.
6. Back in Agen.co, the panel switches to **Select the tools to import from Plaid.** Every tool is toggled on; turn off any you don't want to import, then click **Add**.


The connector is created and its tools imported only when you click **Add**. If you close the panel before that, nothing is saved, even though the Plaid tab reported **Tools imported successfully**.

### Authorize each user

Adding the connector doesn't authorize anyone's tool calls yet. The first time each user's agent calls a Plaid tool, the call returns an authorization link instead of a result. The user opens the link and signs in to the Plaid Dashboard again. On this screen the requesting client is named `mcp-gateway-source-<uuid>` rather than **MCP OAuth Client**, and the redirect host is the MCP gateway rather than Agen.co — this is expected, so tell users to approve it. After that, the user's tool calls run with their own Plaid Dashboard access.

Once connected, Plaid appears under **My connectors** with these tools:

| Tool | What it does |
|  --- | --- |
| `plaid_list_teams` | Lists the teams the user belongs to, to get a `team_id` for the other tools |
| `plaid_get_link_analytics` | Reads Link's conversion funnel, error rate, and opens for a team over a date range |
| `plaid_get_usages` | Reads usage metrics for Plaid products, such as Auth requests or Transactions calls, over a period |
| `plaid_debug_item` | Diagnoses why a Plaid Item isn't working, from its state |
| `plaid_get_tools_introduction` | Returns a short introduction to the available tools |


Enabling the Plaid connector isn't enough on its own. Tool calls remain denied until you create a [policy](/agen-for-work/policies/overview) that grants access to the specific tools you want to expose.

### Additional resources

- [Plaid Dashboard MCP server](https://plaid.com/docs/resources/mcp/)