Comparison · Banking & Account Aggregation

Account aggregation MCP servers compared: who holds the connection

Twenty-one servers in this directory sit in Banking and Account Aggregation. Four of them answer a question a US advisory firm would actually ask. The rest are licensed to banks, built for lenders, or serve consumers directly, and a comparison that treated all twenty-one as alternatives would be misleading.

The four below are compared on the thing that matters most in this category, which is not coverage. Aggregation always means a third party holds the connection to your client's bank. The useful questions are who that third party is, what consent record exists, and whether the connection can write as well as read.

At a glance

ServerStatusAuthHostingCovers
PlaidOfficialOAuthRemoteBank and brokerage account connectivity across thousands of US institutions, returning balances, transactions, holdings and account identity. The most widely deployed aggregation layer in US consumer and advisor fintech, and frequently the mechanism sitting underneath another platform's aggregation feature.
BankSyncVendorAPI keyBothVendor-run remote MCP server over BankSync's aggregation network (15,000+ institutions), exposing accounts, transactions, balances, investments and loans through 28 tools. Vendor documents read-write access. Start with read-only scopes and a least-privilege key.
YodleeCommunityAPI keyLocalUnofficial Gradio-based server exposing Envestnet | Yodlee bank accounts, balances, and transactions to MCP clients.
Narmi / Grasshopper BankVendorOAuthRemoteMCP server letting Grasshopper business banking clients query their own financial information through Claude, account balances, recurring vendor categorisation and similar analysis. Caveats: read-only by design. Launched as a controlled beta to a limited client group. Confirm current availability. Grasshopper business banking clients only; Narmi's broader partner availability is separate. Claude was the only supported assistant at launch. "First MCP server by a U.S. bank" and "first bank in Anthropic's connector directory" are the vendor's claims. Connection details are not publicly published.

Status, auth, hosting and coverage are reproduced from each server's directory listing, which reflects publisher documentation at the last review. Vendor claims are labelled as such and are not independently verified.

Where each one is the better answer

Plaid

Best for

The default answer for US account connectivity and the only official aggregator server here. Balances, transactions, holdings and account identity across thousands of institutions, with an OAuth flow most clients will already recognize from other apps.

Watch for

Coverage of a bank does not mean coverage of every account type or data field at that bank, and connection reliability varies by institution. Plaid also holds the connection, so credential custody and the consent record sit with a third party rather than with your firm.

Listing and connection details →

BankSync

Best for

The widest stated institution coverage on this page at 15,000-plus, with 28 tools spanning accounts, transactions, balances, investments and loans, and a published remote endpoint you can connect today rather than arrange through a sales process.

Watch for

The vendor documents read-write access. That is unusual for an aggregator and it means the connection can do more than read. Start with read-only scopes and a least-privilege key, and confirm which of the 28 tools your key actually enables.

Listing and connection details →

Yodlee

Best for

A route into Yodlee, which sits underneath a great deal of existing advisor infrastructure, for firms that already hold Yodlee credentials and want that data reachable from an agent.

Watch for

Community-built and unofficial. It is a Gradio-based wrapper rather than an Envestnet or Yodlee product, with no vendor support and no commitment to track API changes. Running client banking data through an unsupported wrapper is a different risk decision from using Yodlee directly.

Listing and connection details →

Narmi / Grasshopper Bank

Best for

Read-only by design and published by the bank itself, which is the cleanest security posture in this category. Balances, recurring vendor categorisation and similar analysis for Grasshopper business banking clients.

Watch for

Narrow. It serves Grasshopper business banking clients only, launched as a controlled beta to a limited group, and supported Claude alone at launch. Confirm current availability before planning a workflow around it.

Listing and connection details →

Endpoints and install commands are not repeated here, take them verbatim from each server's listing page, which is the version we keep current.

By advisor task

Connecting a client's outside accounts for a held-away view
Plaid. Broadest US coverage, officially published, and a consent flow clients have seen before, which matters more than it sounds when you are asking someone to connect a bank account.
Needing the widest possible institution coverage
BankSync, at a stated 15,000-plus institutions. Set read-only scopes deliberately, because the vendor documents write access.
Already running on Yodlee
The community wrapper is the only MCP route today, and it is unofficial. Weigh that against calling the Yodlee API directly from your own code.
Business banking clients at Grasshopper
Narmi's server, read-only by design and published by the bank.
Anything outside the United States
Look past this page. Belvo covers Brazil and Mexico, Fi Money covers India, Griffin and Starling are UK, Investec is South African. None of them serve a US advisory practice.

Before you connect any of them

  • Most of this category is not built for advisors. Nymbus, Personetics, Bud Financial, Meniga and Newline are licensed to financial institutions. Blend, nCino and Lendscape are lending origination. YNAB and Monarch Money are personal budgeting tools. They appear in the directory because they are real, not because they are options for a wealth firm.
  • Aggregation always means a third party holds the connection to your client's bank. The question is not whether that is true, it is who, under what consent record, and what happens to cached data when the client disconnects.
  • Write access is the first thing to check. BankSync documents read-write. Nymbus exposes money movement and debit card controls. Meniga supports opening accounts and setting up transfers. An aggregator that can move money is not an aggregator, and should not be scoped like one.
  • Consumer financial data carries permissible-use obligations that do not disappear because an agent is doing the reading. Confirm your basis for accessing and retaining it before you connect anything.
  • Listings in this directory are informational. They are not endorsements, security reviews, or investment advice.