Point your agent at the catalogue.

One endpoint, Streamable HTTP, no auth, no signup. Your agent gets six tools: search with datasheet-provenance specs, full part records, compatibility checks against real engineering constraints, and priced bills of materials.

The endpoint

https://partsgraph.ai/api/mcp

Claude — web, desktop or mobile

01Open Settings → Connectors (on a paid Claude plan) and choose Add custom connector.
02Name it Partsgraph and paste the endpoint above. No OAuth screen appears — the catalogue is public and read-only.
03In a new chat, enable the connector and ask: “Spec me a two-wheel robot from the Partsgraph catalogue — full BOM with prices.”

Claude Code

claude mcp add --transport http partsgraph https://partsgraph.ai/api/mcp

ChatGPT

01Open Settings → Connectors (developer mode may need enabling under Advanced) and add a custom connector.
02Paste the endpoint above, authentication none.
03Ask for the robot, the weather station or the plant waterer.

Registry-aware clients

The connector is published in the official MCP Registry as ai.partsgraph/catalog — clients that browse the registry can install it by name.

What to try first

“Spec me a two-wheel robot. Show the BOM with prices and explain every compatibility check.”
“Would 4×AA alkaline cells work with the Pico in the robot build? Cite the datasheet figures.”
“Build the solar weather station BOM and tell me which line has no machine-stated price, and why.”

Tool calls are logged anonymously — a salted hash of the network address, never the address itself — to power the public demo dashboard. Details in the privacy policy. Prices are indicative and dated; availability is never claimed.