trade_bottrade_scenario — bottrade MCP Prompt
trade_bottrade_scenario
is one of 1 prompt on the
bottrade
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke trade_bottrade_scenario from your client
- Claude Code bottrade Prompt/trade_bottrade_scenario run in your project directory
- Claude Desktop bottrade Prompt/trade_bottrade_scenario ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor bottrade Prompt/trade_bottrade_scenario ~/.cursor/mcp.json
- VS Code bottrade Prompt/trade_bottrade_scenario .vscode/mcp.json
- Zed bottrade Prompt/trade_bottrade_scenario ~/.config/zed/settings.json
- Windsurf bottrade Prompt/trade_bottrade_scenario ~/.codeium/windsurf/mcp_config.json
- Cline bottrade Prompt/trade_bottrade_scenario ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI bottrade Prompt/trade_bottrade_scenario ~/.gemini/settings.json
- Grok bottrade Prompt/trade_bottrade_scenario .mcp.json (in your project root)
- ChatGPT bottrade Prompt/trade_bottrade_scenario Settings → Connectors → Advanced → Developer mode
- Claude.ai bottrade Prompt/trade_bottrade_scenario Settings → Connectors → Add custom connector
- LangChain bottrade Prompt/trade_bottrade_scenario pip install langchain-mcp-adapters
bottrade also offers 2 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, 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 prompt's arguments.