MCP Connectors for Brokerages, Compared

Last updated October 2026

Short answer

Walnut is the MCP connector to start with if you do not write code: one no-code connection across most US brokers, read-only from Claude or ChatGPT, with trades placed in the Walnut app only when you approve them. The other options split by role. Since 2026 a number of brokers run their own official connectors, among them Interactive Brokers, Robinhood, Webull, Public, tastytrade, Moomoo and TradeStation; each covers its own accounts only. Alpaca has an official open-source server. Aggregators (SnapTrade, Plaid) are the linking layer apps use to reach many brokers. Charles Schwab and Fidelity have no first-party connector and are reached through aggregators. Finnhub is market-data only and cannot touch an account.

Invest with AI

Once Anthropic introduced the Model Context Protocol, a wave of finance connectors shipped, and searching for the “best” one hides an important fact: they are not the same kind of thing. Some are aggregators that link brokers, some are a single broker's own connector, some are brokers with no connector of their own, and one here is pure market data. This page compares sixteen of them side by side on the same fields, then ranks them by what you actually want to do. For the singular explainer, see the best MCP connector for brokerages.

How to read this comparison

An MCP connector for a brokerage is a server that exposes your account to an AI assistant as MCP tools (the plain-language version of what an MCP connector is spells this out). The Model Context Protocol is an open standard, introduced by Anthropic in late 2024, for connecting assistants like Claude or ChatGPT to external tools through a uniform interface. But not every name in this space is a connector you point Claude at directly, which is the whole reason a comparison is useful.

There are four roles here. Aggregators (SnapTrade, Plaid) are regulated linking layers that front many brokers behind one connection, for apps to build on. Broker connectors (the official ones from Interactive Brokers, Robinhood, Webull, Public, tastytrade, Moomoo and TradeStation, plus Alpaca and emerging names like Connect Trade) read one broker's accounts and, depending on the connector, place orders or draft them for you; Schwab and Fidelity sit here too, reached read-only. A consumer connector (Walnut) is a hosted, no-code option that spans many brokers so a non-developer can use it from Claude or ChatGPT. A market-data server (Finnhub) only serves prices and fundamentals and has no account access. Comparing an aggregator, an execution server, and a data feed on one axis is misleading, so we name the role for each.

What to compare across brokerage MCP connectors

Role. Whether it is an aggregator (linking layer), an execution server (reads and trades), a hosted consumer connector, or market data only.
Broker coverage. Every broker's own connector binds to that broker; multi-broker connectors (Walnut) reach many.
Read, draft, or execute. Whether it only reads holdings, drafts orders you submit (IBKR), or places trades, and what controls gate orders, such as Webull's order caps.
Auth and security model. Whether it uses scoped API tokens, a broker session, or a regulated aggregator, defaults to read-only, and never stores your broker password.
Setup effort. A self-hosted server (Alpaca, tastytrade) versus a hosted one (Public, Moomoo, Walnut), plus any requirements such as TradeStation's $10,000 balance.
Official vs community. Whether the broker maintains it (IBKR, Robinhood, Webull, Public, tastytrade, Moomoo, TradeStation, Alpaca) or it is an emerging name (Connect Trade), which affects maintenance and trust.

Aggregators: the linking layer

These are not MCP servers you point Claude at. They are the regulated plumbing a brokerage connector uses to reach many institutions behind one connection. Each is described on the same fields: what it is, read or trade, coverage, auth and security, who it suits, and one honest limitation.

SnapTrade

A regulated brokerage-aggregation API that connects many US brokers behind a single integration for reading positions and, on supported brokers, placing trades. SnapTrade is not itself an MCP server; it is the plumbing that portfolio-aware connectors sit on to reach multiple brokers at once.

Read or trade: Read across most major US brokers; trade on a supported subset.
Coverage: Many brokers behind one link (Schwab, Fidelity, and more for reading; execution on a subset such as E*Trade, Public, tastytrade, Webull and Questrade).
Auth and security: Broker login and credentials stay at the broker; the connecting app authenticates with SnapTrade and access is read-only unless trading is enabled.
Best for: Connectors and apps that need broad multi-broker read (and some trade) coverage without a bespoke integration per broker.
One honest limitation: It is infrastructure, not an assistant: on its own it does not speak MCP, so you use it through a connector rather than pointing Claude at it directly.

Plaid

A regulated financial-data aggregator widely used for read-only account and investment linking across institutions. In an MCP setup it is the linking layer a read-only connector can use to see holdings, not an execution path.

Read or trade: Read-only (account and investment data); no trade execution.
Coverage: Broad institutional coverage for read-only investment and account data.
Auth and security: Credentials stay at the institution; scoped, read-only tokens front the account data, with no order-placement capability.
Best for: Read-only holdings and account linking across many institutions when trade execution is not needed.
One honest limitation: No trading path: it can surface positions to an assistant but cannot place an order, so pair it with an execution route if you want trades.

Connectors that read and trade a real account

These connect to an actual brokerage so an assistant can read positions and, with the right access, place trades. Most are a single broker's own connector, some hosted and some self-hosted; Schwab and Fidelity are reached read-only; and Walnut is the hosted, no-code option across many brokers. Seven brokers launched official connectors in 2026, and newer names (for example Connect Trade) surface in AI answers too; verify their broker support, maintenance, and security before pointing any of them at a live account.

Walnut connector

A portfolio-aware MCP connector for consumers, and one connection across many brokers rather than one. You connect your brokers securely, then read your combined live portfolio and use thematic-portfolio tools from Claude Desktop, ChatGPT, or Cursor. Walnut offers a hosted connector and a small downloadable local MCP shim, so there is no server code to write.

Read or trade: Read by default; trades only with your explicit approval, and only where the broker supports execution.
Coverage: Many brokers through one connection. Trades with your approval at E*Trade, moomoo, Public, Questrade, Stake Australia, tastytrade, Trading212, Wealthsimple, Webull Canada and Webull US; Robinhood, Schwab, Fidelity, Vanguard and Interactive Brokers are read-only; Alpaca and TradeStation are not offered.
Auth and security: Your broker login stays with your broker; the connector authenticates with a per-user Walnut key, access is read-only unless you enable trading, and you approve every trade.
Best for: Non-developers with money at more than one broker, or at a broker with no connector of its own, who want one no-code connection from Claude Desktop, ChatGPT, or Cursor.
One honest limitation: It sits on top of your broker rather than being one, so you need an existing account, and broker feeds rarely pass cost basis (returns are framed as window returns, not realized profit and loss). If all your money is at one broker with its own connector, that connector is a fine choice. Walnut is not an investment adviser.

Alpaca (alpaca-mcp-server)

Alpaca's official, open-source MCP server (alpaca-mcp-server). It exposes Alpaca's trading API to an AI agent as MCP tools: real-time and historical market data, account and position reads, order placement, and a full paper-trading sandbox.

Read or trade: Read + trade + paper trading.
Coverage: Alpaca brokerage accounts only.
Auth and security: You supply your own Alpaca API key and secret as environment variables and self-host the server; credentials live in your config, not with a third party.
Best for: Developers building agent-driven, automated workflows who already use (or will open) an Alpaca account.
One honest limitation: Single-broker: it only touches Alpaca accounts, and you run and secure the server yourself.

Interactive Brokers (official connector)

Interactive Brokers' own AI connector. It had certified Claude and ChatGPT connectors by June 8, 2026, and on July 28, 2026 IBKR opened AI connectivity to any tool built on the MCP standard. The AI can read the account and draft orders, which land in an "AI Instructions" area for you to submit; it does not execute on its own.

Read or trade: Read + draft orders; you submit every order.
Coverage: Interactive Brokers accounts only (broad global markets).
Auth and security: You authorize with IBKR, so your login stays at IBKR, and drafted orders wait for you in "AI Instructions".
Best for: IBKR customers who want Claude, ChatGPT or another MCP client on their account while submitting orders themselves.
One honest limitation: Single-broker, and the AI only drafts, so it is deliberately not a hands-off agent.

TradeStation (official MCP)

TradeStation's official MCP, launched in January 2026, connects an assistant to a TradeStation account (the broker covers equities, options and futures). It requires a $10,000 account balance and a paid Claude or ChatGPT plan.

Read or trade: Check TradeStation's documentation for the actions it exposes.
Coverage: TradeStation accounts only.
Auth and security: You authorize with TradeStation, so your login stays at the broker.
Best for: Established TradeStation customers who meet the balance requirement and pay for Claude or ChatGPT.
One honest limitation: The $10,000 balance and paid-plan requirements rule out smaller accounts, and it is single-broker.

Robinhood Agentic Trading MCP (official)

Robinhood's official Agentic Trading MCP, launched May 27, 2026, lets an assistant trade equities, options and crypto on a Robinhood account. On September 30, 2026 Robinhood also announced Robinhood Agents inside its app, which can analyze markets, build strategies and trade, with "Loops" standing instructions.

Read or trade: Read + trade (equities, options, crypto).
Coverage: Robinhood accounts only.
Auth and security: You authorize with Robinhood, so your login stays at Robinhood.
Best for: Robinhood customers who want an outside assistant that can act on their Robinhood account.
One honest limitation: Single-broker: it cannot see money held elsewhere. Confirm the current terms before letting an agent trade.

Webull (official MCP and connectors)

Since August 2026 Webull has offered an official MCP and native connectors for ChatGPT, Claude and Grok, with controls such as order caps and a read-only mode.

Read or trade: Read + trade within your order caps, or read-only mode.
Coverage: Webull accounts only.
Auth and security: You authorize with Webull and can cap order sizes or keep the connection read-only.
Best for: Webull traders who want an assistant on their account with explicit limits.
One honest limitation: Single-broker; set caps or read-only mode before granting trade access.

Public (official hosted MCP)

Public's official hosted MCP for Claude, ChatGPT and Perplexity, part of the "Agentic Brokerage" it launched on March 31, 2026. Public runs the server, so there is nothing for you to host.

Read or trade: Read + trade (Agentic Brokerage).
Coverage: Public accounts only.
Auth and security: You authorize with Public; the connector is hosted by the broker.
Best for: Public customers who want Claude, ChatGPT or Perplexity on their account with no setup.
One honest limitation: Single-broker. Check Public's documentation for which order types an agent can submit.

tastytrade (official MCP server)

tastytrade's official MCP server, released in September 2026. It is self-hosted: you run it and connect it to your tastytrade account.

Read or trade: Check tastytrade's documentation for the actions it exposes.
Coverage: tastytrade accounts only.
Auth and security: You run the server and keep its credentials in your own config.
Best for: Options traders on tastytrade comfortable running a small server.
One honest limitation: Single-broker, and you host and secure it yourself.

Moomoo (official hosted MCP)

Moomoo's official hosted MCP, one of the first-party broker connectors launched in 2026. Moomoo runs it, so there is nothing for you to host.

Read or trade: Check Moomoo's documentation for the actions it exposes.
Coverage: Moomoo accounts only.
Auth and security: You authorize with Moomoo; the connector is hosted by the broker.
Best for: Moomoo customers who want an assistant on their account without hosting anything.
One honest limitation: Single-broker.

Charles Schwab

Schwab has no first-party AI connector that we know of, so the practical route is a multi-broker connector that links a Schwab account for reading. Schwab is not one of the brokers where those connections support trading today.

Read or trade: Read-only through a multi-broker connector; no native Schwab MCP server.
Coverage: Charles Schwab accounts, reached through a multi-broker connection.
Auth and security: Login stays at Schwab; a connector authenticates through its connection layer with read-only access.
Best for: Schwab holders who want an AI assistant to see their real holdings.
One honest limitation: Read-only in practice, and the Schwab link can be less reliable than other brokers'; verify current support.

Fidelity

Fidelity has no first-party AI connector that we know of either. Through a multi-broker connector a Fidelity account can be linked so an assistant can read holdings; trading through those connections is not available today.

Read or trade: Read-only through a multi-broker connector.
Coverage: Fidelity accounts, reached read-only through a multi-broker connection.
Auth and security: Login stays at Fidelity; a connector authenticates through its connection layer with read-only access to holdings.
Best for: Fidelity holders who want read-only portfolio visibility from an AI assistant.
One honest limitation: Read-only in practice: an assistant can see Fidelity holdings but cannot place trades there through current connectors.

Connect Trade

A newer name that surfaces in AI answers about MCP-based brokerage trading. It appears as a community or emerging connector aimed at giving an agent brokerage access, rather than an established, broker-official server.

Read or trade: Read + trade, as an emerging connector (confirm before relying on it).
Coverage: Broker support is project-specific and evolving; check its documentation for the current list.
Auth and security: As with other community connectors, expect scoped API tokens or a broker session rather than a hosted, no-code flow.
Best for: Builders tracking newer, emerging MCP brokerage connectors who will vet maintenance and security themselves.
One honest limitation: Newer and less established, so verify who maintains it, which brokers it truly supports, and its security posture before pointing it at a live account. Start with paper or simulated trading.

Market data only

This one does not connect to a brokerage. It feeds an assistant prices, fundamentals, and news so its analysis is grounded in real data rather than stale training data. It cannot read or act on your account. Many people pair a data server like this for research with a brokerage connector for the portfolio itself.

Finnhub MCP server

A market-data MCP server fronting the Finnhub API, which serves real-time quotes, company fundamentals, news, earnings, and alternative datasets so an agent reasons over live numbers instead of stale training data.

Read or trade: Data only (no account, cannot trade).
Coverage: None (market data), not a brokerage.
Auth and security: A free or paid Finnhub API key in your config; no brokerage access at all.
Best for: Grounding an assistant's research in real-time quotes, news, and fundamentals, with a usable free tier.
One honest limitation: Data only: it cannot see or act on any portfolio, and higher-frequency and premium datasets sit behind paid tiers.

MCP brokerage connectors compared at a glance

Provider	Role	Coverage	Auth model	Best for
SnapTrade	Linking layer	Many brokers behind one link (Schwab, Fidelity, and more for reading; execution on a subset such as E*Trade, Public, tastytrade, Webull and Questrade)	Regulated aggregator	Connectors and apps that need broad multi-broker read (and some trade) coverage without a bespoke integration per broker
Plaid	Linking layer	Broad institutional coverage for read-only investment and account data	Regulated aggregator	Read-only holdings and account linking across many institutions when trade execution is not needed
Walnut connector	Read / trade	Many brokers through one connection. Trades with your approval at E*Trade, moomoo, Public, Questrade, Stake Australia, tastytrade, Trading212, Wealthsimple, Webull Canada and Webull US; Robinhood, Schwab, Fidelity, Vanguard and Interactive Brokers are read-only; Alpaca and TradeStation are not offered	Secure connection, read-only default	Non-developers with money at more than one broker, or at a broker with no connector of its own, who want one no-code connection from Claude Desktop, ChatGPT, or Cursor
Alpaca (alpaca-mcp-server)	Read / trade	Alpaca brokerage accounts only	Self-host, Alpaca API key	Developers building agent-driven, automated workflows who already use (or will open) an Alpaca account
Interactive Brokers (official connector)	Read / draft orders	Interactive Brokers accounts only (broad global markets)	Official, broker login at IBKR	IBKR customers who want Claude, ChatGPT or another MCP client on their account while submitting orders themselves
TradeStation (official MCP)	Read / trade	TradeStation accounts only	Official, $10k balance and paid AI plan	Established TradeStation customers who meet the balance requirement and pay for Claude or ChatGPT
Robinhood Agentic Trading MCP (official)	Read / trade	Robinhood accounts only	Official, broker login at Robinhood	Robinhood customers who want an outside assistant that can act on their Robinhood account
Webull (official MCP and connectors)	Read / trade	Webull accounts only	Official, broker login at Webull	Webull traders who want an assistant on their account with explicit limits
Public (official hosted MCP)	Read / trade	Public accounts only	Official and hosted, broker login at Public	Public customers who want Claude, ChatGPT or Perplexity on their account with no setup
tastytrade (official MCP server)	Read / trade	tastytrade accounts only	Official, self-host	Options traders on tastytrade comfortable running a small server
Moomoo (official hosted MCP)	Read / trade	Moomoo accounts only	Official and hosted, broker login at Moomoo	Moomoo customers who want an assistant on their account without hosting anything
Charles Schwab	Read only	Charles Schwab accounts, reached through a multi-broker connection	Multi-broker connector, read-only	Schwab holders who want an AI assistant to see their real holdings
Fidelity	Read only	Fidelity accounts, reached read-only through a multi-broker connection	Multi-broker connector, read-only	Fidelity holders who want read-only portfolio visibility from an AI assistant
Connect Trade	Read / trade	Broker support is project-specific and evolving; check its documentation for the current list	API tokens or broker session	Builders tracking newer, emerging MCP brokerage connectors who will vet maintenance and security themselves
Finnhub MCP server	Data only	None (market data), not a brokerage	Self-host, data API key	Grounding an assistant's research in real-time quotes, news, and fundamentals, with a usable free tier

Ranked by what you want to do

There is no overall number one, because the right choice depends on whether you want a no-code path to your own broker, a self-hosted server you control, or just the plumbing and research. Below the field is ranked inside each use-case, with the stronger fit first. Walnut appears in the consumer group as the no-code, broad-coverage pick, not as an overall winner.

Best for a non-developer who wants AI access to a real account

If you are not going to write code and want an assistant to read your real portfolio (with trades placed only after you approve them), a hosted connector is the fit: your broker's own if it has one, or a multi-broker one.

Walnut connector. One no-code connection across many brokers, read-only from Claude or ChatGPT, with trades placed in the Walnut app only when you approve them. The fit if your money is at several brokers, or at Schwab or Fidelity.
Public (official hosted MCP). If all your money is at Public, its hosted connector works with Claude, ChatGPT or Perplexity and needs nothing to run.
Robinhood Agentic Trading MCP (official). If all your money is at Robinhood, its official MCP trades equities, options and crypto on that account.
Webull (official MCP and connectors). If all your money is at Webull, its connectors add order caps and a read-only mode.

Best for a developer who wants to build and self-host

If you write code and want full control over the tools your agent exposes, the self-hosted servers are the foundation.

Alpaca (alpaca-mcp-server). The official open-source server (alpaca-mcp-server) with data, paper, and live execution, so you can iterate before risking real money.
tastytrade (official MCP server). An official MCP server you host yourself, for tastytrade accounts.
Interactive Brokers (official connector). IBKR's official connector, open to any MCP client, drafts orders into "AI Instructions" for you to submit.

Best for the plumbing and for research

Two of these are not assistants at all. Aggregators are the linking layer a connector uses to reach brokers; a data server grounds analysis in real numbers.

SnapTrade. An aggregation layer that lets an app reach many brokers for read and, on a subset, trade.
Plaid. A regulated aggregator for read-only holdings and account linking across many institutions.
Finnhub MCP server. A market-data MCP server for real-time quotes, news, and fundamentals, with a usable free tier and no account access.

How the connection actually works

Under the hood, a brokerage connector reaches your account one of two ways: directly through the broker's own API or official connector (Interactive Brokers, Robinhood, Webull, Public, tastytrade, Moomoo, TradeStation, Alpaca), or through a multi-broker connection layer that fronts many institutions behind one link. The multi-broker route is how a single connector can reach brokers like Schwab and Fidelity, which have no connector of their own, and it is the difference between an MCP connector and a raw broker API, covered in MCP connector vs API vs plugin. The bridge has three moving parts: the AI client (Claude Desktop, ChatGPT, or Cursor), the MCP server that speaks the protocol, and the broker connection the server authenticates against.

The safer connectors keep read access as the default and gate any trade behind explicit approval, never store your broker password, and scope what the agent may do through API tokens, the broker's own login, or a secure multi-broker link. The risks worth naming: a broad or mis-scoped API key can grant more than you intend; a self-hosted server you do not secure becomes a new attack surface; and community or emerging connectors vary in maintenance, so vet the code before pointing one at a live account. Paper or simulated trading first is the simplest guardrail. For the full walkthrough, see how to connect your brokerage to an AI assistant.

How we evaluated these

We named each provider's role first (aggregator, execution server, consumer connector, or market data), because comparing them on one axis is misleading. Within the connectors that touch an account we weighed broker coverage, whether the server can execute or only read, the auth and security model, and setup effort. We treat read-only defaults and credential safety as table stakes, not bonus features: a connector that can trade but mishandles access is not better than a careful read-only one. We did not crown a single overall winner; the right choice depends on your broker and whether you want execution. Facts here are qualitative and point-in-time, so verify current capabilities on each project's documentation.

Where Walnut fits

To be upfront, since this is our site: Walnut is the AI investing assistant that talks to the broker you already have and places the trades you approve. Among these options it is the portfolio-aware, read-only-by-default consumer connector, rather than an aggregator, a raw developer server, or a data feed, and it leads in that niche rather than overall. Walnut lets Claude Desktop, ChatGPT, or Cursor read your real connected brokerage portfolio across many brokers through one secure connection; trades are placed in the Walnut app, at the brokers that support it, and only when you approve them. A broker's own connector covers that one broker; Walnut covers the set. You can use either Walnut's hosted connector or a small downloadable local MCP shim, whichever your AI client supports. To connect the hosted version for Claude, ChatGPT, or Codex (and any MCP client), add its MCP server URL, https://walnutinvest.com/api/connector/mcp, as a custom connector, then sign in with a free Walnut account and approve read-only access; it never places trades. Full per-client setup lives on the Walnut MCP connector page. Because broker feeds rarely pass cost basis, Walnut frames returns as window returns rather than realized profit and loss, and says so.

If all your money is at one broker that has its own connector, that connector is a fine choice. If you are a developer who lives in Alpaca and wants full execution control, the Alpaca official server (alpaca-mcp-server) will fit better. For pure research, pair either approach with a data MCP like Finnhub. From a connected account you can ask an assistant about a specific stock, ETF, or theme against your real holdings. Walnut is not an investment adviser.

The bottom line

The names people compare here are not one kind of thing. SnapTrade and Plaid are aggregators, the plumbing an app builds on. Interactive Brokers, Robinhood, Webull, Public, tastytrade, Moomoo and TradeStation now run official connectors, each for its own accounts, and IBKR's drafts orders rather than placing them. Alpaca's official server is self-hosted. Charles Schwab and Fidelity have no first-party connector and are reached read-only. Connect Trade is an emerging name to verify before use. Finnhub is market data only. Walnut is the no-code connector across many brokers, working from Claude or ChatGPT, read-only by default. There is no single best one: pick by your broker, whether you want execution, and how much you want to build.

Get a recommendation for your situation

Walnut is the AI that knows your portfolio: ask anything in plain English, research any fund, and get an honest second opinion. On the broker you already use, read-only, and you approve every trade. Walnut is not a registered investment adviser.

Invest with AI

FAQ

What are the top MCP connector providers for a brokerage?

If you do not write code, start with Walnut, the no-code connector across most US brokers. Beyond that the field splits by role. Aggregators (SnapTrade, Plaid) are the linking layer connectors use to reach brokers. Brokers' own official connectors (Interactive Brokers, Robinhood, Webull, Public, tastytrade, Moomoo, TradeStation) and Alpaca's official alpaca-mcp-server each cover a single broker. Schwab and Fidelity have no first-party connector and are reached read-only through multi-broker connectors such as Walnut. Finnhub is market-data only and cannot touch an account.

How do these MCP brokerage connectors compare at a glance?

Compare them on four things: whether they read, trade, only link, or only serve data; which brokers they cover; their auth and security model; and whether you self-host or use a hosted, no-code flow. Each broker's official connector (IBKR, Robinhood, Webull, Public, tastytrade, Moomoo, TradeStation) and Alpaca's server covers one broker, some hosted and some self-hosted; SnapTrade and Plaid are aggregators; Finnhub is data only; and Walnut is a hosted connector that reaches many brokers, read-only by default.

Is SnapTrade or Plaid an MCP connector?

Neither is an MCP server on its own. SnapTrade and Plaid are regulated aggregators that connect many brokers or institutions behind one link, and an app or connector builds on top of them to expose accounts to an assistant. SnapTrade supports reading and, on a subset of brokers, trading; Plaid is read-only account and investment data (it is also how ChatGPT's US Finances feature links accounts, which can show holdings but cannot trade).

Which connector reaches Schwab or Fidelity?

Neither Schwab nor Fidelity has a first-party connector we know of, so the practical route is a multi-broker connector. Walnut reaches both, read-only, so a Schwab or Fidelity account can be read from Claude or ChatGPT next to your other brokers. Single-broker connectors such as Alpaca's, Robinhood's or TradeStation's do not touch Schwab or Fidelity at all.

Is there an official MCP server for a brokerage?

Yes, several. In 2026 Interactive Brokers, Robinhood, Webull, Public, tastytrade, Moomoo and TradeStation each launched a first-party connector, and Alpaca publishes an official open-source server (alpaca-mcp-server). Each covers only its own broker. Schwab and Fidelity have none we know of and are reached read-only through multi-broker connectors. Walnut is a hosted connector that covers many brokers instead of one.

What is the difference between a brokerage connector and a market-data MCP like Finnhub?

A brokerage connector (Walnut, the official broker connectors, Alpaca) connects to your actual account so an assistant can read holdings and possibly trade. A market-data MCP like Finnhub only serves prices, fundamentals, and news, with no account access. Many setups pair a data server such as Finnhub for research with a brokerage connector for the portfolio itself.

Can Claude or ChatGPT trade my brokerage through these connectors?

Yes, if you use a connector that supports execution and grant trade access. Robinhood's, Webull's and Public's official connectors and Alpaca's server can place orders on their own accounts; IBKR's connector drafts orders that you submit. The safer pattern keeps access read-only by default and requires your explicit approval before any order. Walnut works this way: read-only unless you enable trading, and every trade at a supported broker needs your confirmation.

Which connector works with the most brokers?

For a no-code consumer, Walnut, because it is one connection across many brokers. Every broker's own connector (IBKR, Robinhood, Webull, Public, tastytrade, Moomoo, TradeStation, Alpaca) is single-broker by design; if all your money is at one of them, that connector is a fine choice. Aggregators such as SnapTrade and Plaid span many institutions but are infrastructure for apps, not assistants, and Plaid is read-only.

Is Connect Trade a good MCP connector for brokerages?

Connect Trade is a newer name that appears in AI answers about MCP brokerage trading, rather than an established broker-official server. Because it is emerging, verify who maintains it, which brokers it truly supports, and its security posture before pointing it at a live account, and start with paper or simulated trading. For a hosted, no-code alternative, Walnut connects many brokers through one connection, read-only by default.

Are these brokerage MCP connectors safe?

The safer ones default to read-only access, never store your broker password, and scope what the agent can do through API tokens or a regulated aggregator. Before connecting, confirm whether the connector can place trades and what approval controls exist. Walnut is read-only by default, keeps your broker login with your broker, and requires approval for every order. Community and emerging connectors vary in maintenance, so vet the code first.

Which one should a non-developer pick?

A hosted, no-code connector. Self-hosted servers like Alpaca's or tastytrade's require running and securing a server, and aggregators like SnapTrade and Plaid are plumbing, not assistants. If all your money is at Public or Moomoo, their hosted connectors are a no-code path for that broker. Walnut is the no-code path across several brokers: you connect them securely and use them from Claude or ChatGPT, read-only by default and with trades you approve.

Walnut is informational and is not an investment adviser. MCP connectors, aggregators, broker support, and auth models change quickly; verify current capabilities on each project's documentation before connecting an account. Nothing on this page is a recommendation to buy, sell, or hold any security or to use any particular product.

ETFs and stocks in this guide

Stocks: IBKR