get_trader_position_history — TraderSpy MCP Tool Read-only
get_trader_position_history
(get trader position history) is one of 18 tools on the
TraderSpy
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_trader_position_history from your client
- Claude Code TraderSpy get_trader_position_history run in your project directory
- Claude Desktop TraderSpy get_trader_position_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TraderSpy get_trader_position_history ~/.cursor/mcp.json
- VS Code TraderSpy get_trader_position_history .vscode/mcp.json
- Zed TraderSpy get_trader_position_history ~/.config/zed/settings.json
- Windsurf TraderSpy get_trader_position_history ~/.codeium/windsurf/mcp_config.json
- Cline TraderSpy get_trader_position_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TraderSpy get_trader_position_history ~/.gemini/settings.json
- Grok TraderSpy get_trader_position_history .mcp.json (in your project root)
- ChatGPT TraderSpy get_trader_position_history Settings → Connectors → Advanced → Developer mode
- Claude.ai TraderSpy get_trader_position_history Settings → Connectors → Add custom connector
- LangChain TraderSpy get_trader_position_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http traderspy https://mcp.traderspy.app/mcpOther 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.