send_order_to_provider — Koppar MCP Tool Mutating
send_order_to_provider
(send order to provider) is one of 67 tools on the
Koppar
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call send_order_to_provider from your client
- Claude Code Koppar send_order_to_provider run in your project directory
- Claude Desktop Koppar send_order_to_provider ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Koppar send_order_to_provider ~/.cursor/mcp.json
- VS Code Koppar send_order_to_provider .vscode/mcp.json
- Zed Koppar send_order_to_provider ~/.config/zed/settings.json
- Windsurf Koppar send_order_to_provider ~/.codeium/windsurf/mcp_config.json
- Cline Koppar send_order_to_provider ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Koppar send_order_to_provider ~/.gemini/settings.json
- Grok Koppar send_order_to_provider .mcp.json (in your project root)
- ChatGPT Koppar send_order_to_provider Settings → Connectors → Advanced → Developer mode
- Claude.ai Koppar send_order_to_provider Settings → Connectors → Add custom connector
- LangChain Koppar send_order_to_provider pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http koppar https://app.koppar.ai/mcpOther tools on this server
- get_workflow_guide
- create_design
- leave_feedback
- list_designs
- delete_design
- restore_design
- get_design
- search_kicad_symbol
- get_kicad_symbol
- search_kicad_footprint
- create_custom_symbol
- add_custom_footprint
- save_dossier
- submit_circuit
- edit_circuit
- read_design_file
- get_review_packet
- get_board_context
- start_board
- get_board_status
- get_bom
- choose_bom_part
- consolidate_bom_basic
- get_fab_status
- list_order_providers
- get_order_price
- upload_board
- get_downloads
- import_kicad_project
- get_board_info
- place_footprints
- auto_place
- anneal_place
- set_board_outline
- set_design_rules
- set_keepouts
- check_net_rules
- check_physics
- set_zones
- add_copper
- prune_vias
- set_silkscreen
- route_board
- update_board_from_netlist
- repair_board
- ripup_routing
- cleanup_board
- add_project_files
- swap_footprint
- fill_zones
- stamp_silkscreen
- tie_rail_pads
- widen_nets
- finish_board
- bridge_islands
- tidy_copper
- polish_vias
- couple_pairs
- diagnose_open_nets
- run_drc
- render_board
- export_step
- list_board_revisions
- restore_board_revision
- get_board_job
- stop_board_job
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.