Skip to main content
Glama
@luxalgo/broker-mcp

@luxalgo/broker-mcp

Official
by LuxAlgo

@luxalgo/broker-mcp

npm CI License: MIT

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

BROKERS_ALPACA_API_KEY, BROKERS_ALPACA_API_SECRET

Coinbase (BYO app)

BROKERS_COINBASE_CLIENT_ID, BROKERS_COINBASE_CLIENT_SECRET, BROKERS_COINBASE_REFRESH_TOKEN

Binance

BROKERS_BINANCE_API_KEY, BROKERS_BINANCE_API_SECRET

Bybit

BROKERS_BYBIT_API_KEY, BROKERS_BYBIT_API_SECRET

Crypto.com

BROKERS_CRYPTO_COM_API_KEY, BROKERS_CRYPTO_COM_API_SECRET

E*TRADE (BYO app)

BROKERS_ETRADE_CONSUMER_KEY, BROKERS_ETRADE_CONSUMER_SECRET, BROKERS_ETRADE_ACCESS_TOKEN, BROKERS_ETRADE_ACCESS_TOKEN_SECRET

Hyperliquid

BROKERS_HYPERLIQUID_WALLET_ADDRESS

Interactive Brokers (Flex)

BROKERS_IBKR_FLEX_FLEX_TOKEN, BROKERS_IBKR_FLEX_FLEX_QUERY_ID

Kraken

BROKERS_KRAKEN_API_KEY, BROKERS_KRAKEN_API_SECRET

OKX

BROKERS_OKX_API_KEY, BROKERS_OKX_API_SECRET, BROKERS_OKX_PASSPHRASE

Public.com

BROKERS_PUBLIC_API_KEY

Questrade

BROKERS_QUESTRADE_REFRESH_TOKEN

Topstep

BROKERS_TOPSTEP_USER_NAME, BROKERS_TOPSTEP_API_KEY

Tradier

BROKERS_TRADIER_ACCESS_TOKEN

Trading212

BROKERS_TRADING212_API_KEY

Webull

BROKERS_WEBULL_API_KEY, BROKERS_WEBULL_API_SECRET

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

list_brokers

Every supported broker, its env vars (set/unset — never values), configured state, read-only key guide

list_accounts

All connected accounts: broker, currency, equity, cash

get_positions

Open positions with market values (negative quantity = short); filter by broker

get_trades

Trade history, newest first; filter by broker/symbol

get_stats

Total equity, equity by broker, top positions, FIFO win rate, avg win/loss, realized PnL per symbol

refresh

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 build

The 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 tools
get_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

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      A 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.
      9
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI agents real-time access to DeFi across multiple chains, enabling non-custodial crypto trading, portfolio queries, and transaction execution.
      7
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Read-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.html
      11
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An 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.
      28
      79 PyPI
      3
      MIT