Model Context Protocol

Connect your agent to the supplier graph.

Weld indexes thousands of US contract manufacturers — CNC machining, sheet metal, stamping, welding, finishing, PCBA, and adjacent processes — with capability profiles, certifications, and federal contract history. The MCP server lets your agent search that graph directly. Your agent runs the loop; Weld returns the shops.

Endpoint

One stateless Streamable-HTTP endpoint. No API key required to search.

https://weldsourcing.com/api/mcp

Tools

  • search_suppliers(query, limit?, explain?)

    Search the graph with a natural-language sourcing brief — process, materials, certifications, industry, location, volume. Returns a ranked shortlist of US manufacturers with location, certifications, industries, and a profile slug.

  • get_supplier(slug)

    Pull one shop's full capability profile by slug: capabilities, materials, certifications, equipment, industries, contact details, and federal contract history when on record.

Add it to your client

Most MCP clients (Claude, Cursor, and the MCP Inspector) take a server URL directly. Drop this into your client's MCP config:

{
  "mcpServers": {
    "weld": {
      "url": "https://weldsourcing.com/api/mcp"
    }
  }
}

Or call it directly

It's plain JSON-RPC 2.0 over POST — reachable from any HTTP client.

curl -s https://weldsourcing.com/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"search_suppliers",
                 "arguments":{"query":"5-axis CNC, AS9100, titanium, near San Jose"}}}'