product_graph — materials MCP Tool
product_graph
(product graph) is one of 24 tools on the
materials
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call product_graph from your client
- Claude Code materials product_graph run in your project directory
- Claude Desktop materials product_graph ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor materials product_graph ~/.cursor/mcp.json
- VS Code materials product_graph .vscode/mcp.json
- Zed materials product_graph ~/.config/zed/settings.json
- Windsurf materials product_graph ~/.codeium/windsurf/mcp_config.json
- Cline materials product_graph ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI materials product_graph ~/.gemini/settings.json
- Grok materials product_graph .mcp.json (in your project root)
- ChatGPT materials product_graph Settings → Connectors → Advanced → Developer mode
- Claude.ai materials product_graph Settings → Connectors → Add custom connector
- LangChain materials product_graph pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http materials https://spacemushroom.com/mcpOther tools on this server
- search_materials
- get_material
- compare
- list_properties
- get_term
- find_materials
- list_claims
- prove_claim
- what_is_missing
- resolve_designation
- search_sources
- find_products
- search_products
- get_product
- product_parts
- products_using_material
- materials_used_by_function
- standards_for
- orgs_for
- products_by_maker
- engines_for_vehicle
- vehicles_for_engine
- compare_products
This list was read from the server itself, by connecting to it and calling tools/list on 11 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.