convert_ingredient — World Calendars and Ingredient Parser MCP Tool
convert_ingredient
(convert ingredient) is one of 10 tools on the
World Calendars and Ingredient Parser
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call convert_ingredient from your client
- Claude Code World Calendars and Ingredient Parser convert_ingredient run in your project directory
- Claude Desktop World Calendars and Ingredient Parser convert_ingredient ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor World Calendars and Ingredient Parser convert_ingredient ~/.cursor/mcp.json
- VS Code World Calendars and Ingredient Parser convert_ingredient .vscode/mcp.json
- Zed World Calendars and Ingredient Parser convert_ingredient ~/.config/zed/settings.json
- Windsurf World Calendars and Ingredient Parser convert_ingredient ~/.codeium/windsurf/mcp_config.json
- Cline World Calendars and Ingredient Parser convert_ingredient ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI World Calendars and Ingredient Parser convert_ingredient ~/.gemini/settings.json
- Grok World Calendars and Ingredient Parser convert_ingredient .mcp.json (in your project root)
- ChatGPT World Calendars and Ingredient Parser convert_ingredient Settings → Connectors → Advanced → Developer mode
- Claude.ai World Calendars and Ingredient Parser convert_ingredient Settings → Connectors → Add custom connector
- LangChain World Calendars and Ingredient Parser convert_ingredient pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http calendars-ingredients https://mcp.fitztoppicks.com/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.