@luxalgo/broker-mcp
OfficialProvides read-only access to Binance brokerage accounts, enabling queries for account balances, open positions, trade history, and performance statistics.
Provides read-only access to Coinbase accounts via a custom app, enabling queries for balances, positions, trade history, and performance metrics.
Provides read-only access to OKX brokerage accounts, enabling queries for account balances, positions, trade history, and performance statistics.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@luxalgo/broker-mcp How's my portfolio looking this week?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@luxalgo/broker-mcp
Give your AI agent read access to your real brokerage accounts — with keys that never leave your machine.
A local MCP server wrapping @luxalgo/broker-sdk. Connect Claude (or any MCP client) to Alpaca, Binance, Kraken, Bybit, Hyperliquid, Interactive Brokers and more, then just ask:
"How's my portfolio doing?" · "What's my win rate this month?" · "What did I trade last week?"
No hosted service, no telemetry, no per-connection fees. The server runs on your machine, your keys live in your own MCP config, and the underlying SDK has no trading endpoints at all — the agent can look, not touch.
Setup
Add the server to your MCP client config with the credential env vars for the brokers you use. Claude Desktop (claude_desktop_config.json) or Claude Code (.mcp.json):
{
"mcpServers": {
"brokers": {
"command": "npx",
"args": ["-y", "@luxalgo/broker-mcp"],
"env": {
"BROKERS_ALPACA_API_KEY": "…",
"BROKERS_ALPACA_API_SECRET": "…",
"BROKERS_KRAKEN_API_KEY": "…",
"BROKERS_KRAKEN_API_SECRET": "…",
"BROKERS_HYPERLIQUID_WALLET_ADDRESS": "0x…"
}
}
}
}Every broker whose variables are all set is connected automatically. Create every key with read-only scope — that is all this server ever needs; the list_brokers tool includes the one-line read-only setup guide per broker.
Environment variables
Names derive mechanically from each broker's credential fields: BROKERS_<BROKER>_<FIELD>.
Broker | Variables |
Alpaca |
|
Coinbase (BYO app) |
|
Binance |
|
Bybit |
|
Crypto.com |
|
E*TRADE (BYO app) |
|
Hyperliquid |
|
Interactive Brokers (Flex) |
|
Kraken |
|
OKX |
|
Public.com |
|
Questrade |
|
Topstep |
|
Tradier |
|
Trading212 |
|
Webull |
|
Questrade caveat: its refresh tokens are single-use and rotate on every fetch. The server keeps the rotated token in memory while it runs, but after a restart the token in your config is already consumed — you'll need to paste a fresh one. Static env config and rotating tokens are a poor fit; a better answer is on the roadmap.
Related MCP server: @y0exchange/mcp
Tools
Tool | What the agent gets |
| Every supported broker, its env vars (set/unset — never values), configured state, read-only key guide |
| All connected accounts: broker, currency, equity, cash |
| Open positions with market values (negative quantity = short); filter by broker |
| Trade history, newest first; filter by broker/symbol |
| Total equity, equity by broker, top positions, FIFO win rate, avg win/loss, realized PnL per symbol |
| Bypass the 5-minute cache and re-fetch everything now |
Snapshots are cached in memory for 5 minutes; per-broker failures are reported alongside results, never silently dropped.
Security posture
Read-only by construction. The SDK underneath implements no order, transfer, or withdrawal endpoint for any broker.
Keys stay in your MCP config. The server reads them from its environment, reports only whether each variable is set, and never writes secrets anywhere.
Local only. Talks to your brokers directly over HTTPS and to your MCP client over stdio. No LuxAlgo server involved, no telemetry.
Still: scope every key read-only at the broker, and treat your MCP config file like the secret store it is.
Development
pnpm install && pnpm check && pnpm buildThe SDK dependency installs from the public npm registry like any other package.
Disclaimer
This software reports what your broker reports. It is not investment advice. Verify important numbers against your broker's own statements.
License
MIT © LuxAlgo
Available Tools
6 toolsget_positionsA
Open positions across all accounts (symbol, quantity — negative means short — and market value in the account currency when the broker prices it). Optionally filter by broker id.
Inputs: broker.
get_statsA
Computed performance stats across the whole portfolio: total equity, equity by broker, top positions, and FIFO-matched trade stats (win rate, average win/loss, realized PnL, per-symbol breakdown). Amounts are in each account's native currency — mixed-currency totals are approximate.
Inputs: no named parameters.
get_tradesA
Trade history across all accounts (the most recent window each broker exposes). Optionally filter by broker id and/or symbol; newest first.
Inputs: limit, broker, symbol.
list_accountsA
List all connected accounts across every configured broker: id, name, broker, currency, total equity, and cash when reported. Uses a short-lived cache; call refresh for live numbers.
Inputs: no named parameters.
list_brokersA
List every supported broker, the environment variables its credentials go in, and whether it is configured in this server. Values are never shown, only whether each variable is set.
Inputs: no named parameters.
refreshA
Bypass the cache and re-fetch every configured broker right now. Returns per-broker success/failure.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a clearly distinct resource: brokers, accounts, positions, trades, and aggregate stats. The only non-query tool, refresh, is unambiguous and serves as a cache-busting action. There is no overlap or potential for misselection.
Tool names follow a consistent verb_noun pattern (list_brokers, get_positions) with the minor exception of 'refresh', which is a standard imperative verb. The mirroring of list/get for collections versus individual items is predictable and readable.
Six tools is an ideal scope for a broker aggregation server, covering configuration, account status, positions, trade history, and performance analytics. Every tool earns its place without bloat or unnecessary overlap.
The set covers the full read-only lifecycle of a trading portfolio: broker connectivity, account listing, positions, trade history, and aggregated stats. The refresh tool addresses the cache invalidation need, so there are no obvious dead ends or missing functions.
Related MCP Connectors
Trading MCP server for AI agents, with live market data, account reads and controlled execution.
Read-only finance MCP server. Connects your banks, cards, payment apps, books and payroll into one ledger for your AI. Can't move money. Open source (AGPL-3.0), free during beta.
Connect Claude, ChatGPT, Codex, Claude Code or another MCP client to your real multi-broker investment portfolio. Fortunest tracks stocks, ETFs and crypto across brokers and exchanges; its MCP server lets your agent read holdings, returns, allocation, risk, trades and tax lots, calculated by Fortunest rather than guessed by the model. Reads run on their own; every change waits for your approval in the Fortunest app, and no tool places an order or moves money. Sign-in is OAuth 2.1 and needs Fortunest Pro (14-day trial, no card). A free demo that needs no account is listed as Fortunest demo.
Connect brokerage accounts to AI assistants: holdings, orders, asset lookup, and approved trading.
Related MCP Servers
- AlicenseAqualityDmaintenanceA read-only MCP server that provides access to Charles Schwab account data and market information, including portfolio positions, real-time quotes, options chains, price history, and account balances through AI assistants.9MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents real-time access to DeFi across multiple chains, enabling non-custodial crypto trading, portfolio queries, and transaction execution.7MIT
- AlicenseNot gradedqualityAmaintenanceRead-only MCP tools for Interactive Brokers: account, portfolio, market data, risk analysis and position sizing. Requires IBKR Pro and a local TWS or IB Gateway API session. Install the signed Canary binary or Claude Desktop MCPB bundle locally. Other local MCP clients launch the installed canary executable with the argument mcp. Setup: https://osauer.dev/canary/docs/start/install.html11MIT
- AlicenseAqualityBmaintenanceAn MCP server that gives AI assistants read access to real brokerage accounts and market data, with 39 tools for prices, technical analysis, SEC filings, and macro indicators, while order execution requires human approval via a separate dashboard.2879 PyPI3MIT