set_copy_settings — WakeTrades MCP Tool Mutating
set_copy_settings
(set copy settings) 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 set_copy_settings from your client
- Claude Code WakeTrades set_copy_settings run in your project directory
- Claude Desktop WakeTrades set_copy_settings ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WakeTrades set_copy_settings ~/.cursor/mcp.json
- VS Code WakeTrades set_copy_settings .vscode/mcp.json
- Zed WakeTrades set_copy_settings ~/.config/zed/settings.json
- Windsurf WakeTrades set_copy_settings ~/.codeium/windsurf/mcp_config.json
- Cline WakeTrades set_copy_settings ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WakeTrades set_copy_settings ~/.gemini/settings.json
- Grok WakeTrades set_copy_settings .mcp.json (in your project root)
- ChatGPT WakeTrades set_copy_settings Settings → Connectors → Advanced → Developer mode
- Claude.ai WakeTrades set_copy_settings Settings → Connectors → Add custom connector
- LangChain WakeTrades set_copy_settings pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://waketrades.com/mcpOther tools on this server
- hello
- get_started
- get_offer
- get_leader
- start_sign_in
- finish_sign_in
- get_account
- get_levels
- suggest_leader
- get_leader_positions
- backtest_leader
- set_advanced
- link_webhook
- unlink_webhook
- prepare_trading_key
- submit_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.