okx_place_order — Trend0x MCP Tool
okx_place_order
(okx place order) is one of 115 tools on the
Trend0x
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call okx_place_order from your client
- Claude Code Trend0x okx_place_order run in your project directory
- Claude Desktop Trend0x okx_place_order ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Trend0x okx_place_order ~/.cursor/mcp.json
- VS Code Trend0x okx_place_order .vscode/mcp.json
- Zed Trend0x okx_place_order ~/.config/zed/settings.json
- Windsurf Trend0x okx_place_order ~/.codeium/windsurf/mcp_config.json
- Cline Trend0x okx_place_order ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Trend0x okx_place_order ~/.gemini/settings.json
- Grok Trend0x okx_place_order .mcp.json (in your project root)
- ChatGPT Trend0x okx_place_order Settings → Connectors → Advanced → Developer mode
- Claude.ai Trend0x okx_place_order Settings → Connectors → Add custom connector
- LangChain Trend0x okx_place_order pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http trend0x https://app.trend0x.com/api/mcpOther tools on this server
- get_market_data
- execute_trade
- get_balance
- paper_profit_policy
- assistant_operation
- pause_saved_strategy
- set_strategy_execution_selection
- get_bitpanda_portfolio
- get_bitpanda_trade_history
- get_bitpanda_tickers
- get_alpaca_account
- get_alpaca_positions
- execute_alpaca_trade
- get_alpaca_news
- get_bitunix_balance
- get_bitunix_positions
- execute_bitunix_trade
- list_tasks
- create_task
- create_scanner_task
- update_task_status
- calculate_position_size
- emergency_close_all
- set_max_daily_loss
- risk_reward_check
- get_risk_metrics
- position_sizing_policy
- circuit_breaker
- get_portfolio_summary
- get_pnl_report
- get_performance_metrics
- trade_confirm
- fetch_terminal_state
- get_whitebit_portfolio
- get_exchange_positions
- manage_strategies
- select_strategy_exchange
- run_saved_strategy
- start_paper_strategy
- update_strategy_exchange
- update_strategy_rules
- account_risk_settings
- implement_strategy
- strategy_hub
- scanner_config
- scanner_control
- enable_scanner
- disable_scanner
- scanner_status
- terminal_modules
- terminal_config
- portfolio_history
- portfolio_performance
- run_backtest
- backtest_results
- history_query
- agent_reports
- send_markdown_to_telegram
- terminal_news
- perplexity_market_news
- perplexity_social_buzz
- perplexity_ticker_research
- perplexity_viral_updates
- perplexity_earnings_recap
- perplexity_watchlist_digest
- perplexity_sentiment_signal
- market_news
- social_buzz
- ticker_research
- viral_updates
- earnings_recap
- watchlist_digest
- sentiment_signal
- financial_instruments
- cognitive_control
- bybit_market_tickers
- bybit_market_kline
- bybit_orderbook
- bybit_instruments_info
- bybit_wallet_balance
- bybit_positions
- bybit_open_orders
- bybit_order_history
- bybit_trade_history
- bybit_internal_transfer
- bybit_place_order
- bybit_cancel_order
- bybit_set_trading_stop
- bybit_set_leverage
- okx_agent_skills
- okx_market_tickers
- okx_market_candles
- okx_orderbook
- okx_instruments
- okx_account_balance
- okx_positions
- okx_open_orders
- okx_order_history
- okx_trade_history
- okx_cancel_order
- okx_set_leverage
- binance_agent_skills
- binance_market_ticker
- binance_market_klines
- binance_orderbook
- binance_exchange_info
- binance_funding_rate
- binance_open_interest
- binance_account_balance
- binance_positions
- binance_open_orders
- binance_order_history
- binance_trade_history
- binance_income_history
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.