materials_used_by_function — materials MCP Tool
materials_used_by_function
(materials used by function) 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 materials_used_by_function from your client
- Claude Code materials materials_used_by_function run in your project directory
- Claude Desktop materials materials_used_by_function ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor materials materials_used_by_function ~/.cursor/mcp.json
- VS Code materials materials_used_by_function .vscode/mcp.json
- Zed materials materials_used_by_function ~/.config/zed/settings.json
- Windsurf materials materials_used_by_function ~/.codeium/windsurf/mcp_config.json
- Cline materials materials_used_by_function ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI materials materials_used_by_function ~/.gemini/settings.json
- Grok materials materials_used_by_function .mcp.json (in your project root)
- ChatGPT materials materials_used_by_function Settings → Connectors → Advanced → Developer mode
- Claude.ai materials materials_used_by_function Settings → Connectors → Add custom connector
- LangChain materials materials_used_by_function 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
- standards_for
- orgs_for
- products_by_maker
- engines_for_vehicle
- vehicles_for_engine
- product_graph
- 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.