search_components — NomyParts open data MCP Tool Read-only
search_components
(search components) is one of 5 tools on the
NomyParts open data
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call search_components from your client
- Claude Code NomyParts open data search_components run in your project directory
- Claude Desktop NomyParts open data search_components ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NomyParts open data search_components ~/.cursor/mcp.json
- VS Code NomyParts open data search_components .vscode/mcp.json
- Zed NomyParts open data search_components ~/.config/zed/settings.json
- Windsurf NomyParts open data search_components ~/.codeium/windsurf/mcp_config.json
- Cline NomyParts open data search_components ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NomyParts open data search_components ~/.gemini/settings.json
- Grok NomyParts open data search_components .mcp.json (in your project root)
- ChatGPT NomyParts open data search_components Settings → Connectors → Advanced → Developer mode
- Claude.ai NomyParts open data search_components Settings → Connectors → Add custom connector
- LangChain NomyParts open data search_components pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http open-data https://nomyparts-open-data.nomyparts.workers.dev/mcp
Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.