meals_plan — SAVORDISH MCP Tool
meals_plan
(meals plan) is one of 31 tools on the
SAVORDISH
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call meals_plan from your client
- Claude Code SAVORDISH meals_plan run in your project directory
- Claude Desktop SAVORDISH meals_plan ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SAVORDISH meals_plan ~/.cursor/mcp.json
- VS Code SAVORDISH meals_plan .vscode/mcp.json
- Zed SAVORDISH meals_plan ~/.config/zed/settings.json
- Windsurf SAVORDISH meals_plan ~/.codeium/windsurf/mcp_config.json
- Cline SAVORDISH meals_plan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SAVORDISH meals_plan ~/.gemini/settings.json
- Grok SAVORDISH meals_plan .mcp.json (in your project root)
- ChatGPT SAVORDISH meals_plan Settings → Connectors → Advanced → Developer mode
- Claude.ai SAVORDISH meals_plan Settings → Connectors → Add custom connector
- LangChain SAVORDISH meals_plan pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http savor-dish https://savordish.com/mcpOther tools on this server
- recipes_search
- recipes_get
- recipes_list_by_cuisine
- recipes_get_trending
- cooking_get_tips
- platform_get_info
- shopping_generate_grocery_list
- shopping_instacart
- recipes_get_nutrition
- recipes_find_by_ingredient
- cooking_get_substitutions
- cuisines_explore
- recipes_get_random
- recipes_compare
- recipes_get_quick
- recipes_get_dietary
- recipes_scale
- nutrition_analyze
- nutrition_compare
- nutrition_find_by_macros
- nutrition_daily_plan
- nutrition_healthier_swap
- nutrition_ingredient_info
- nutrition_meal_score
- recipes_seasonal
- recipes_collections
- cooking_pair_beverages
- cooking_meal_prep_guide
- cooking_convert_units
- account_api_key_status
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.