submit_trading_key — WakeTrades MCP Tool
submit_trading_key
(submit trading key) is one of 33 tools on the
WakeTrades
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call submit_trading_key from your client
- Claude Code WakeTrades submit_trading_key run in your project directory
- Claude Desktop WakeTrades submit_trading_key ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WakeTrades submit_trading_key ~/.cursor/mcp.json
- VS Code WakeTrades submit_trading_key .vscode/mcp.json
- Zed WakeTrades submit_trading_key ~/.config/zed/settings.json
- Windsurf WakeTrades submit_trading_key ~/.codeium/windsurf/mcp_config.json
- Cline WakeTrades submit_trading_key ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WakeTrades submit_trading_key ~/.gemini/settings.json
- Grok WakeTrades submit_trading_key .mcp.json (in your project root)
- ChatGPT WakeTrades submit_trading_key Settings → Connectors → Advanced → Developer mode
- Claude.ai WakeTrades submit_trading_key Settings → Connectors → Add custom connector
- LangChain WakeTrades submit_trading_key pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://waketrades.com/mcp
Other tools on this server
- hello
- get_started
- get_offer
- get_leader
- start_sign_in
- finish_sign_in
- get_account
- get_levels
- set_copy_settings
- suggest_leader
- get_leader_positions
- backtest_leader
- set_advanced
- link_webhook
- unlink_webhook
- prepare_trading_key
- confirm_trading_key
- switch_to_unified_account
- prepare_payment
- submit_payment
- set_order_mode
- get_positions
- get_orders
- get_journal
- get_report
- pause_copying
- resume_copying
- close_position
- close_losing
- close_all
- emergency_stop
- revoke_all_sessions
This list was read from the server itself, by connecting to it and calling tools/list on 28 October 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.