traderspy-signals-app — TraderSpy MCP Resource

traderspy-signals-app is one of 4 resources on the TraderSpy MCP server. Connect the server and your client can attach it as context.

by client

How to attach traderspy-signals-app from your client

• Claude Code TraderSpy Resource/traderspy-signals-app run in your project directory
• Claude Desktop TraderSpy Resource/traderspy-signals-app ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor TraderSpy Resource/traderspy-signals-app ~/.cursor/mcp.json
• VS Code TraderSpy Resource/traderspy-signals-app .vscode/mcp.json
• Zed TraderSpy Resource/traderspy-signals-app ~/.config/zed/settings.json
• Windsurf TraderSpy Resource/traderspy-signals-app ~/.codeium/windsurf/mcp_config.json
• Cline TraderSpy Resource/traderspy-signals-app ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI TraderSpy Resource/traderspy-signals-app ~/.gemini/settings.json
• Grok TraderSpy Resource/traderspy-signals-app .mcp.json (in your project root)
• ChatGPT TraderSpy Resource/traderspy-signals-app Settings → Connectors → Advanced → Developer mode
• Claude.ai TraderSpy Resource/traderspy-signals-app Settings → Connectors → Add custom connector
• LangChain TraderSpy Resource/traderspy-signals-app pip install langchain-mcp-adapters

Other resources on this server

• traderspy-signal-details-app
• traderspy-account-app
• traderspy-technicals-app

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.