freqtrade-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FREQTRADE_API_URL | No | Base URL of the Freqtrade API server | http://127.0.0.1:8080 |
| FREQTRADE_PASSWORD | Yes | API password — required | |
| FREQTRADE_USERNAME | No | API username from your Freqtrade config | Freqtrader |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profit_statsA | Retrieve current profit and loss statistics: total profit, win/loss ratio, best pair, drawdown, trading volume, and more. |
| get_balanceA | Check the current wallet and account balance across all currencies, including free, used, and total amounts. |
| get_performanceA | Retrieve per-pair trading performance metrics, including profit and trade count for each pair. |
| get_open_tradesA | View all currently active (open) trades, including entry price, current profit, stake amount, and duration. |
| get_tradeA | Retrieve detailed information about a specific trade by its ID, including full history, fees, and profit/loss. |
| get_trade_historyA | Retrieve closed trade history with optional pagination. Returns trades sorted by ID. |
| get_market_dataA | Fetch live OHLCV (Open/High/Low/Close/Volume) candlestick market data for a specific trading pair and timeframe. |
| get_whitelistA | View the current trading pair whitelist — the set of pairs the bot is allowed to trade. |
| get_blacklistA | View the current trading pair blacklist — pairs that are explicitly excluded from trading. |
| add_to_blacklistB | Add a trading pair to the blacklist to prevent the bot from opening new trades on it. |
| remove_from_blacklistB | Remove a trading pair from the blacklist, allowing the bot to trade it again. |
| execute_tradeA | Manually enter (force-enter) a trade on a specific pair. The bot bypasses strategy signals and opens the position immediately. Natural language examples: • "buy 100 USDT of BTC/USDT" → pair=BTC/USDT, side=long, stake_amount=100 • "short 0.5 ETH/USDT at 2000" → pair=ETH/USDT, side=short, price=2000 The position will be managed by the active strategy after entry. |
| force_exit_tradeA | Manually exit (force-sell) an open trade, bypassing the strategy exit signals. Supports full and partial exits. Examples: • Close trade 42 immediately: trade_id=42 • Partial exit 50% of trade 7: trade_id=7, amount= |
| start_botA | Start the Freqtrade bot. The bot will begin trading according to its configured strategy. Has no effect if already running. |
| stop_botA | Stop the Freqtrade bot. Existing open trades will remain open and will not be closed automatically. Use force_exit_trade to close positions manually. |
| reload_configA | Reload the bot configuration from disk. Useful after editing config.json without restarting the process. The bot will briefly pause trading during the reload. |
| get_bot_infoA | Get general information about the bot: software version and the timestamp of the last strategy run cycle. |
| get_locksA | Retrieve all active trade locks. Locks prevent the bot from opening new trades on specific pairs for a defined period. |
| delete_lockA | Remove a specific trade lock by its ID. Use get_locks to list current locks and their IDs. |
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 19 tools
Each tool targets a distinct action or resource. Blacklist, lock, trade execution, and bot control tools are clearly separated. Even similar tools like get_performance and get_profit_stats are differentiated by per-pair vs global perspective.
All tools follow a consistent verb_noun pattern (e.g., get_balance, add_to_blacklist, force_exit_trade). No mixing of conventions like camelCase or inconsistent verb forms.
19 tools is slightly above the ideal range but still reasonable for a comprehensive trading bot server. Each tool covers a necessary function without redundancy.
Core CRUD operations for trades, blacklist, locks, and bot control are present. Minor gaps exist, such as the inability to modify active trade parameters (e.g., stop loss) or cancel pending orders, but the essential workflow is covered.