daski_submit_order_input — Daski MCP Tool
daski_submit_order_input
(daski submit order input) is one of 22 tools on the
Daski
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call daski_submit_order_input from your client
- Claude Code Daski daski_submit_order_input run in your project directory
- Claude Desktop Daski daski_submit_order_input ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Daski daski_submit_order_input ~/.cursor/mcp.json
- VS Code Daski daski_submit_order_input .vscode/mcp.json
- Zed Daski daski_submit_order_input ~/.config/zed/settings.json
- Windsurf Daski daski_submit_order_input ~/.codeium/windsurf/mcp_config.json
- Cline Daski daski_submit_order_input ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Daski daski_submit_order_input ~/.gemini/settings.json
- Grok Daski daski_submit_order_input .mcp.json (in your project root)
- ChatGPT Daski daski_submit_order_input Settings → Connectors → Advanced → Developer mode
- Claude.ai Daski daski_submit_order_input Settings → Connectors → Add custom connector
- LangChain Daski daski_submit_order_input pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http daski https://daski.io/mcp
Other tools on this server
- daski_buy_outcome
- daski_get_setup_guide
- daski_get_outcome_requirements
- daski_get_payment_challenge
- daski_list_outcomes
- daski_get_outcome
- daski_get_order_status
- daski_cancel_order
- daski_get_order_artifact
- daski_contact_order_support
- daski_get_order_access
- daski_confirm_delivery
- daski_revoke_delivery_confirmation
- daski_list_my_orders
- daski_get_my_reputation
- daski_list_assets
- daski_use_asset
- daski_list_providers
- daski_get_provider
- daski_get_service
- daski_resolve_agent
This list was read from the server itself, by connecting to it and calling tools/list on 1 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.