trader_get_trade_history — MangroveTrader MCP Tool
trader_get_trade_history
(trader get trade history) is one of 10 tools on the
MangroveTrader
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call trader_get_trade_history from your client
- Claude Code MangroveTrader trader_get_trade_history run in your project directory
- Claude Desktop MangroveTrader trader_get_trade_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MangroveTrader trader_get_trade_history ~/.cursor/mcp.json
- VS Code MangroveTrader trader_get_trade_history .vscode/mcp.json
- Zed MangroveTrader trader_get_trade_history ~/.config/zed/settings.json
- Windsurf MangroveTrader trader_get_trade_history ~/.codeium/windsurf/mcp_config.json
- Cline MangroveTrader trader_get_trade_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MangroveTrader trader_get_trade_history ~/.gemini/settings.json
- Grok MangroveTrader trader_get_trade_history .mcp.json (in your project root)
- ChatGPT MangroveTrader trader_get_trade_history Settings → Connectors → Advanced → Developer mode
- Claude.ai MangroveTrader trader_get_trade_history Settings → Connectors → Add custom connector
- LangChain MangroveTrader trader_get_trade_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mangrove-trader https://api.mangrovetraders.com/mcp/Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.