get_trades_for_strategy — MangroveAI MCP Tool Read-only
get_trades_for_strategy
(get trades for strategy) is one of 76 tools on the
MangroveAI
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_trades_for_strategy from your client
- Claude Code MangroveAI get_trades_for_strategy run in your project directory
- Claude Desktop MangroveAI get_trades_for_strategy ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MangroveAI get_trades_for_strategy ~/.cursor/mcp.json
- VS Code MangroveAI get_trades_for_strategy .vscode/mcp.json
- Zed MangroveAI get_trades_for_strategy ~/.config/zed/settings.json
- Windsurf MangroveAI get_trades_for_strategy ~/.codeium/windsurf/mcp_config.json
- Cline MangroveAI get_trades_for_strategy ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MangroveAI get_trades_for_strategy ~/.gemini/settings.json
- Grok MangroveAI get_trades_for_strategy .mcp.json (in your project root)
- ChatGPT MangroveAI get_trades_for_strategy Settings → Connectors → Advanced → Developer mode
- Claude.ai MangroveAI get_trades_for_strategy Settings → Connectors → Add custom connector
- LangChain MangroveAI get_trades_for_strategy pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mangroveai https://api.mangrovedeveloper.ai/mcp/Other tools on this server
- delete_strategy
- update_strategy_status
- list_positions
- evaluate_strategy
- list_evaluations
- build_strategy_for_regime
- classify_market_segment
- evaluate_multiple_signals_series
- evaluate_signal
- find_sweep_runs
- get_asset
- get_backtest
- get_backtest_trades
- get_benchmark
- get_chain_tvl
- get_etf_flows
- get_execution_config_schema
- get_global_market
- get_influence_score
- get_lending_rates
- get_market_data
- get_market_regime
- get_marketplace_strategy
- get_ohlcv
- get_onchain_series
- get_perp_funding_rates
- get_playground_data
- get_protocol_tvl
- get_signal
- get_smart_money_dex_trades
- get_smart_money_flows
- get_smart_money_historical_holdings
- get_smart_money_holdings
- get_smart_money_netflows
- get_smart_money_perp_trades
- get_smart_money_sentiment
- get_social_mentions
- get_social_sentiment
- get_stablecoin_metrics
- get_strategy
- get_symbol_exchanges
- get_token_dex_trades
- get_token_flows
- get_token_holders
- get_token_unlocks
- get_treasuries
- get_trending
- kb_get_document
- kb_get_signal_quick_reference
- kb_glossary_get
- kb_list_documents
- kb_search
- list_approved_assets
- list_backtest_markets
- list_backtests
- list_exchanges
- list_playground_datasets
- list_signal_labels
- list_signals
- list_strategies
- list_trades
- load_skill
- match_signals
- query_knowledge
- query_signal_behavior
- run_backtest
- save_strategy
- screen_candidates
- screen_smart_money
- search_marketplace
- search_signals
- update_strategy
- validate_signal_params
- verify_strategy
- discover_tools
This list was read from the server itself, by connecting to it and calling tools/list on 22 October 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.