Tradernet MCP Server

Tradernet MCP server exists for a simple reason — assistants are far more useful when they can act on Tradernet directly instead of describing what you should do. MCP server for Tradernet/Freedom24 trading API — portfolio, orders, quotes, and more.

What you get

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

Setting it up

The server ships on npm as tradernet-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Tradernet is connected, these are the calls the assistant has available:

• get_user_data — Account info, portfolio summary, open positions
• get_portfolio — Current positions, balances, P&L
• place_order — Place buy/sell/short/margin orders
• cancel_order — Cancel an active order
• set_stop_loss_take_profit — Set SL/TP for a position
• get_security_info — Ticker details (currency, exchange, min step)
• get_quotes_history — Historical OHLCV candlestick data
• search_tickers — Search securities by name or symbol
• add_price_alert — Set a price alert with notifications
• delete_price_alert — Remove a price alert
• get_security_sessions — List open security sessions
• raw_api_call — Call any Tradernet API command directly

Configuration and credentials

You will need 3 environment variables: TRADERNET_PUBLIC_KEY, TRADERNET_PRIVATE_KEY, TRADERNET_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Tradernet.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the tradernet mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Tradernet's toolset — get_user_data, get_portfolio, place_order and 10 more — is a fair guide to whether it matches your workflow. It is maintained by verbart; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Tradernet's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.