submit_sourcing_request — SupplySlate MCP Tool
submit_sourcing_request
(submit sourcing request) is one of 55 tools on the
SupplySlate
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call submit_sourcing_request from your client
- Claude Code SupplySlate submit_sourcing_request run in your project directory
- Claude Desktop SupplySlate submit_sourcing_request ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SupplySlate submit_sourcing_request ~/.cursor/mcp.json
- VS Code SupplySlate submit_sourcing_request .vscode/mcp.json
- Zed SupplySlate submit_sourcing_request ~/.config/zed/settings.json
- Windsurf SupplySlate submit_sourcing_request ~/.codeium/windsurf/mcp_config.json
- Cline SupplySlate submit_sourcing_request ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SupplySlate submit_sourcing_request ~/.gemini/settings.json
- Grok SupplySlate submit_sourcing_request .mcp.json (in your project root)
- ChatGPT SupplySlate submit_sourcing_request Settings → Connectors → Advanced → Developer mode
- Claude.ai SupplySlate submit_sourcing_request Settings → Connectors → Add custom connector
- LangChain SupplySlate submit_sourcing_request pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http sourcing https://mcp.supplyslate.com/mcpOther tools on this server
- describe_supplyslate
- list_sourcing_categories
- get_connection_guide
- list_fabrication_processes
- get_live_fabrication_capabilities
- search_live_components
- get_requirement_schema
- search_products
- get_product
- get_compatibility
- list_supplier_taxonomy
- search_suppliers
- get_supplier
- create_project
- get_project
- update_project_requirements
- create_artifact_upload
- attach_artifact_reference
- upsert_bom
- get_bom
- validate_project
- list_project_validations
- source_project
- create_purchase_plan
- get_purchase_plan
- request_purchase_approval
- get_checkout_handoffs
- create_provider_checkout_handoff
- list_orders
- get_order
- report_order_issue
- request_order_cancellation
- request_order_return
- open_warranty_claim
- get_supplier_profile
- upsert_supplier_catalog
- create_catalog_import
- update_supplier_capabilities
- update_availability
- list_supplier_rfqs
- get_supplier_rfq
- submit_supplier_quote
- ask_rfq_clarification
- revise_supplier_quote
- decline_supplier_rfq
- list_supplier_orders
- update_supplier_order
- update_supplier_order_issue
- decide_supplier_order_cancellation
- update_supplier_order_return
- update_supplier_warranty_claim
- list_sourcing_requests
- get_sourcing_request
- get_supplier_offers
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.