ourgroceries-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OURGROCERIES_TEAM_ID | No | Your OurGroceries team ID. Required if not using saved config file. | |
| OURGROCERIES_AUTH_COOKIE | No | Your OurGroceries authentication cookie. Required if not using saved config file. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_listsA | Get visible shopping lists without item arrays. Use this first to choose a list ID before reading or mutating items. |
| get_categoriesB | Get the account's OurGroceries item categories from the hidden category list. |
| get_settingsA | Get the top-level OurGroceries settings and list schema version. |
| get_active_itemsA | Get active items on one shopping list. Active items do not have crossedOffAt. |
| get_crossed_off_itemsA | Get crossed-off items for one shopping list with optional search, date filters, sorting, and pagination. |
| resolve_item_to_addB | Resolve ambiguous or natural-language item text using the master catalog and shopping-list history before adding. Follow the recommendedAction. When no listId is provided, inspect suggestedTargets; high-confidence list history can produce a list-specific action. |
| add_itemA | Add a deterministic item value to a grocery list. For ambiguous or natural-language names, call resolve_item_to_add first and then follow its recommendedAction. |
| remove_itemB | Remove an item from a grocery list |
| update_itemB | Update an item's details (name, category, note, or star rating) |
| cross_off_itemC | Mark an item as crossed off. |
| uncross_itemA | Mark an item as active again. Prefer this over add_item when resolve_item_to_add recommends it. |
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 11 tools
Each tool has a clearly distinct purpose: add_item vs resolve_item_to_add handle deterministic vs ambiguous addition; cross_off_item/uncross_item toggle status; get_active_items/get_crossed_off_items filter by completion; get_categories, get_lists, get_settings retrieve distinct metadata; remove_item, update_item perform their respective actions. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_item, get_active_items, resolve_item_to_add). Even the multi-word 'resolve_item_to_add' maintains the pattern with a preposition. No naming style mixing.
11 tools cover the typical lifecycle of grocery list items (CRUD, cross-off/uncross, filtered queries, plus a resolution helper). This is well-scoped for a focused domain—neither too few nor too many.
Core item operations are fully covered (add, remove, update, cross on/off, list, search), along with categories and settings. The only notable gap is the lack of list creation/deletion tools, but get_lists suggests lists are pre-existing, so this is a minor omission.