get_trader_profile — TraderSpy MCP Tool Read-only
get_trader_profile
(get trader profile) 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_profile from your client
- Claude Code TraderSpy get_trader_profile run in your project directory
- Claude Desktop TraderSpy get_trader_profile ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TraderSpy get_trader_profile ~/.cursor/mcp.json
- VS Code TraderSpy get_trader_profile .vscode/mcp.json
- Zed TraderSpy get_trader_profile ~/.config/zed/settings.json
- Windsurf TraderSpy get_trader_profile ~/.codeium/windsurf/mcp_config.json
- Cline TraderSpy get_trader_profile ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TraderSpy get_trader_profile ~/.gemini/settings.json
- Grok TraderSpy get_trader_profile .mcp.json (in your project root)
- ChatGPT TraderSpy get_trader_profile Settings → Connectors → Advanced → Developer mode
- Claude.ai TraderSpy get_trader_profile Settings → Connectors → Add custom connector
- LangChain TraderSpy get_trader_profile 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.