get_trade_plan — Fexr MCP Tool Read-only
get_trade_plan
(get trade plan) is one of 32 tools on the
Fexr
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_trade_plan from your client
- Claude Code Fexr get_trade_plan run in your project directory
- Claude Desktop Fexr get_trade_plan ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Fexr get_trade_plan ~/.cursor/mcp.json
- VS Code Fexr get_trade_plan .vscode/mcp.json
- Zed Fexr get_trade_plan ~/.config/zed/settings.json
- Windsurf Fexr get_trade_plan ~/.codeium/windsurf/mcp_config.json
- Cline Fexr get_trade_plan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Fexr get_trade_plan ~/.gemini/settings.json
- Grok Fexr get_trade_plan .mcp.json (in your project root)
- ChatGPT Fexr get_trade_plan Settings → Connectors → Advanced → Developer mode
- Claude.ai Fexr get_trade_plan Settings → Connectors → Add custom connector
- LangChain Fexr get_trade_plan pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://api.fexr.io/v1/mcp
Other tools on this server
- get_asset_metrics
- get_historical_timeseries
- get_derivatives
- get_exchange_market_data
- get_stablecoins
- get_protocol_financials
- get_network_activity
- get_staking_yields
- get_token_unlocks
- get_fundraising
- get_treasury
- get_catalysts
- get_market_signals
- get_predictive_signals
- get_smart_money_flow
- get_whale_alerts
- get_market_pulse
- get_sentiment_mindshare
- get_proposal_tracking
- run_screener
- get_news_trending
- get_whale_board
- review_address
- get_trader
- get_asset_snapshot
- list_proven_strategies
- read_ask_thread
- get_weekly_review
- run_token_dossier
- get_my_account
- ask_ai_copilot
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.