Plaid
Connect AI agents and workflows to Plaid: link bank accounts, read balances and transactions, identity and statements, with events as new transactions post.
Book a demoPlaid for AI agents and workflows.
engini lets your AI agents and workflows work with Plaid: link bank accounts through Plaid Link, read accounts and live balances, keep transactions in sync, read account holder identity and bank statements, and start a workflow when new transactions post or a connection needs attention. Bank activity reaches the ERP and the people who reconcile it, every day. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log
in engini
What your agent can do in Plaid. Every tool is one you allow or leave out.
The Plaid tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.
Read
Read linked accounts and their current and available balances.
Read posted and pending transactions, with only what changed since the last sync.
Read the account holder's name, address and contact details.
Read bank statements as PDF.
Find a bank and what it supports.
Write
Start Plaid Link so a person can connect a bank account.
Finish the connection and keep the account linked in engini.
Delete
Disconnect a linked bank.
Any endpoint
Call any Plaid API endpoint your account has, with the keys added for you.
Triggers
Plaid has new or changed transactions for a linked account.
A linked bank needs the person to sign in again.
A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.
Connect your AI agent to Plaid. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Plaid connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of Plaid tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects Plaid and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every Plaid tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to Plaid through engini
{
"mcpServers": {
"engini-plaid": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Plaid connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the Plaid tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on Plaid. Agents and workflows, across systems.
Bank transactions reconciled in the ERP
New transactions are matched to open invoices and bills in NetSuite or QuickBooks, and only the ones that do not match go to a person.
Cash position every morning
Balances across banks land in a Google Sheet or Snowflake and post to the finance channel in Slack.
Bank data in the application
An applicant links a bank account. Balances, transactions and identity reach the application in Salesforce for review.
Cash questions answered
An agent in Claude answers balances and what came in or went out. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Plaid and another system engini connects is available.
You decide what each agent may do in Plaid. engini enforces it on every call.
Only the tools you allow
A toolset lists the Plaid tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own Plaid account and engini acts as that person, with their Plaid permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
Connect Plaid in three steps. Then decide what each agent may do.
Sign in to Plaid
Add a Plaid connection with your client ID and secret, sandbox first. Then link bank accounts through Plaid Link, which engini starts for you.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in Plaid from Claude, ChatGPT, Cursor or your own code.
Plaid and engini. Straight answers.
Can an AI agent write to Plaid, or only read?
Both. engini has tools to start Plaid Link, finish a bank connection and remove one. It has no tools that move money or return account numbers. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
Can an agent move money through Plaid?
No. engini's Plaid tools read balances, transactions, identity and statements. Tools that move money or return full account numbers are left out.
Can I test without real bank data?
Yes. Connect your Plaid sandbox keys and use Plaid's test institutions, then add production keys when you are ready.
Does the agent act as me in Plaid?
It acts as your Plaid account, on the bank connections people linked through Plaid Link. Every run is recorded under the person who started it.
Can a change in Plaid start work?
Yes. Plaid notifies engini when new transactions are available and when a connection needs attention. A trigger starts a workflow, and that workflow can include an AI agent step.
What if the tool I need is not listed?
Use Send API Request to call any Plaid API endpoint through the same connection, and give it only to the agents that need it.