step_run — bottrade MCP Tool

step_run (step run) is one of 19 tools on the bottrade MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call step_run from your client

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

Fastest route

claude mcp add --transport http bottrade https://mcp.bot-trade.org/mcp

Other tools on this server

auth_status
connect_bottrade
list_scenarios
get_scenario
start_run
get_run
get_market
scan_market
inspect_symbols
submit_turn
submit_decision
advance_until_next_session
hold_until_end
liquidate_and_finish
run_sandbox_smoke_test
get_results
get_trades
publish_run

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.

bottrade MCP server