Family Grocery MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KROGER_CLIENT_ID | No | Kroger developer application client ID. Required for live Kroger API operations. | |
| KROGER_CLIENT_SECRET | No | Kroger developer application client secret. Required for live Kroger API operations. | |
| KROGER_USER_ZIP_CODE | No | Zip code used for searching Kroger locations. | |
| FAMILY_GROCERY_PROFILE | No | Path to the household profile JSON file. Defaults to 'data/household_profile.json' if not set. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| plan_weekB | Create a starter weekly meal plan using the household profile. |
| preview_shoppingC | Generate shopping list, mock product matches, allergy review flags, and budget. |
| validate_krogerA | Validate local Kroger credentials without exposing secrets. |
| search_kroger_locationsB | Search Kroger/King Soopers locations near a zip code. |
| search_krogerB | Search live Kroger products at a selected location. |
| preview_live_shoppingC | Generate shopping preview using live Kroger product search. |
| start_kroger_cart_authA | Start Kroger OAuth for cart write access and return an authorization URL. |
| complete_kroger_cart_authA | Complete Kroger OAuth using the full redirect URL from the browser. |
| kroger_cart_auth_statusA | Check whether a local user cart token exists. |
| prepare_kroger_cartC | Prepare approved cart items and list skipped allergy-review items. |
| add_approved_items_to_kroger_cartB | Add only approved, non-review items to the real Kroger cart when confirm is true. |
| add_single_item_to_kroger_cartA | Add one explicit UPC to the real Kroger cart when confirm is true. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Several tools have overlapping purposes, particularly preview_shopping vs preview_live_shopping, which both generate shopping previews but differ only in data source. search_kroger and preview_live_shopping also both involve live product search, creating potential misselection. However, the core workflow tools (auth, cart, planning) are distinct.
Tool names mix verb-first patterns (plan_week, search_kroger), gerund forms (preview_shopping), lengthy prepositional phrases (add_approved_items_to_kroger_cart), and one noun-phrase status (kroger_cart_auth_status). No consistent verb_noun convention is followed, making the set feel ad hoc.
12 tools is well within the ideal 3-15 range for a grocery planning and Kroger integration server. Each tool maps to a distinct step in the workflow (plan, preview, search, auth, cart), and none feel redundant or unnecessary.
The tool set covers the full journey from meal planning to adding items to a real Kroger cart, including authentication and preview stages. Minor gaps exist: no tool to view or modify the generated meal plan, and no way to list current cart contents or remove items, but these are likely out of scope.