TradeStation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRADESTATION_ENV | No | Environment: 'simulation' or 'production' | simulation |
| TRADESTATION_CLIENT_ID | Yes | Your TradeStation API client ID | |
| TRADESTATION_ACCOUNT_ID | No | Default account ID for operations | |
| TRADESTATION_REDIRECT_URI | Yes | OAuth redirect URI (must match app config) | |
| TRADESTATION_CLIENT_SECRET | Yes | Your TradeStation API client secret | |
| TRADESTATION_REFRESH_TOKEN | Yes | OAuth refresh token for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| marketDataC | Get quotes for symbols |
| barChartC | Get historical price bars/candles |
| searchSymbolsA | Search for symbols (Note: Symbol search not available in TradeStation v3 API - use getSymbolDetails instead with known symbols) |
| getOptionExpirationsC | Get available expiration dates for options on an underlying symbol |
| getOptionStrikesC | Get available strike prices for options on an underlying symbol |
| getAccountsB | Get list of brokerage accounts |
| getBalancesC | Get account balances and buying power |
| getPositionsC | Get current positions with P&L |
| getOrdersB | Get order history with optional status filter |
| getOrderDetailsC | Get detailed information for a specific order |
| getExecutionsC | Get fills/executions for a specific order |
| getSymbolDetailsC | Get detailed symbol information |
| confirmOrderA | Preview order costs and requirements (READ-ONLY - does not execute trades) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools have distinct purposes, such as getAccounts for account lists and getBalances for balances, but there is some overlap between getOrders and getOrderDetails, and between marketData and barChart for price data, which could cause minor confusion.
The naming follows a consistent verb_noun pattern with minor deviations, as most tools start with 'get' or descriptive verbs like 'confirm' and 'search', but 'barChart' and 'marketData' break this pattern slightly by using noun-based names.
With 13 tools, the count is well-scoped for a brokerage and trading server, covering key areas like accounts, orders, market data, and options without being overwhelming or insufficient.
The toolset provides comprehensive coverage for querying accounts, orders, positions, and market data, but lacks tools for executing trades or modifying orders, which are notable gaps in a trading context.