mcp-tastytrade-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASTYTRADE_SANDBOX | No | Set to 'true' to use the certification environment (default: false) | false |
| TASTYTRADE_PASSWORD | Yes | Your TastyTrade login password | |
| TASTYTRADE_USERNAME | Yes | Your TastyTrade login username |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_accountsA | List all TastyTrade accounts for the authenticated customer. |
| get_positionsB | Get current open positions for a TastyTrade account. |
| get_balancesC | Get current balances and buying power for a TastyTrade account. |
| get_ordersC | Get orders for a TastyTrade account, optionally filtered by status. |
| place_orderB | Place a new order on a TastyTrade account. Use dry_run_order first to validate the order and check buying power impact. |
| dry_run_orderA | Validate an order without placing it. Returns buying power effect, fees, and any warnings. |
| cancel_orderC | Cancel a live order on a TastyTrade account. |
| get_option_chainA | Get the option chain for an underlying symbol. Use format='nested' (default) for expirations grouped by date, or format='compact' for a flat list. |
| get_market_metricsB | Get market metrics for one or more symbols: IV rank, IV percentile, 30-day IV, liquidity rating, and more. |
| get_transactionsC | Get transaction history for a TastyTrade account. |
| search_equitiesC | Search for equity instruments by symbol. |
| get_watchlistsA | Get all watchlists for the authenticated customer. |
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 12 tools
Each tool has a distinct purpose clearly described. get_positions and get_balances are separate, place_order and dry_run_order are complementary but distinct, no overlapping functionality.
All tools follow a consistent verb_noun pattern with underscores (e.g., get_accounts, cancel_order, dry_run_order). The verbs vary but are appropriate and predictable.
12 tools cover the essential operations for a trading platform without being excessive. Each tool serves a clear need, and the count is within the ideal range.
Core workflows like account information, order management, and market data are covered. Minor gaps exist, such as no modify order or create watchlist, but agents can work around these with the available tools.