prepare_part_hunt_checkout — FindMyPart MCP Tool
prepare_part_hunt_checkout
(prepare part hunt checkout) is one of 4 tools on the
FindMyPart
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call prepare_part_hunt_checkout from your client
- Claude Code FindMyPart prepare_part_hunt_checkout run in your project directory
- Claude Desktop FindMyPart prepare_part_hunt_checkout ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FindMyPart prepare_part_hunt_checkout ~/.cursor/mcp.json
- VS Code FindMyPart prepare_part_hunt_checkout .vscode/mcp.json
- Zed FindMyPart prepare_part_hunt_checkout ~/.config/zed/settings.json
- Windsurf FindMyPart prepare_part_hunt_checkout ~/.codeium/windsurf/mcp_config.json
- Cline FindMyPart prepare_part_hunt_checkout ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FindMyPart prepare_part_hunt_checkout ~/.gemini/settings.json
- Grok FindMyPart prepare_part_hunt_checkout .mcp.json (in your project root)
- ChatGPT FindMyPart prepare_part_hunt_checkout Settings → Connectors → Advanced → Developer mode
- Claude.ai FindMyPart prepare_part_hunt_checkout Settings → Connectors → Add custom connector
- LangChain FindMyPart prepare_part_hunt_checkout pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http findmypart https://findmypart.base44.app/functions/findMyPartMcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.