get_planning_status — Bryti MCP Tool Read-only
get_planning_status
(get planning status) is one of 59 tools on the
Bryti
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_planning_status from your client
- Claude Code Bryti get_planning_status run in your project directory
- Claude Desktop Bryti get_planning_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Bryti get_planning_status ~/.cursor/mcp.json
- VS Code Bryti get_planning_status .vscode/mcp.json
- Zed Bryti get_planning_status ~/.config/zed/settings.json
- Windsurf Bryti get_planning_status ~/.codeium/windsurf/mcp_config.json
- Cline Bryti get_planning_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Bryti get_planning_status ~/.gemini/settings.json
- Grok Bryti get_planning_status .mcp.json (in your project root)
- ChatGPT Bryti get_planning_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Bryti get_planning_status Settings → Connectors → Add custom connector
- LangChain Bryti get_planning_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http bryti https://api.bryti.app/mcp
Other tools on this server
- get_household_overview
- get_rules
- get_week_plan
- get_inventory
- get_shopping_list
- get_stores
- get_recipes
- get_recipe
- get_day
- get_planned_dinner
- get_meal_events
- search_help
- search_tips
- get_calendar_events
- get_shopping_guide
- add_shopping_item
- check_shopping_item
- remove_shopping_item
- add_inventory_observation
- add_guests_for_date
- mark_eating_out
- mark_away
- set_dinner_time
- set_prep_days
- replace_dinner
- set_dinner_lock
- set_recipe_favorite
- import_recipe_from_url
- save_recipe
- record_outcome
- plan_week
- replan_open_days
- clear_week
- set_category_for_date
- set_max_cooking_time_for_date
- delete_rule
- set_leftover_dinners
- set_lunchbox_portions
- edit_recipe
- delete_recipe
- wish_dish
- adapt_dinner_ingredient
- mark_member_absent
- delete_meal_event
- add_food_preference
- delete_food_preference
- merge_pantry_foods
- upsert_category_frequency_rule
- upsert_category_excluded_days_rule
- upsert_category_on_day_rule
- upsert_max_cooking_time_rule
- upsert_max_total_time_rule
- upsert_price_class_rule
- upsert_repeat_after_days_rule
- update_household_settings
- set_household_language
- select_stores
- activate_plan
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.