OurGroceries MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OURGROCERIES_EMAIL | Yes | Email for OurGroceries account | |
| OURGROCERIES_PASSWORD | Yes | Password for OurGroceries account |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_grocery_listsA | List grocery lists available in the configured OurGroceries account. |
| get_itemsA | Return the items in a grocery list selected by case-insensitive exact name. |
| add_itemB | Immediately add an item to a grocery list, optionally with quantity and note. |
| complete_itemA | Preview or, with confirmation, mark a matching grocery item as complete. |
| remove_itemA | Preview or, with confirmation, permanently remove a matching grocery item. |
| move_itemA | Preview or, with confirmation, move an item between grocery lists. |
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 6 tools
Each tool has a clear, distinct purpose: listing lists, getting items, adding, completing, removing, and moving items. There is no overlap or ambiguity between these actions.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_grocery_lists, add_item, complete_item). The naming is uniform and predictable.
With 6 tools, the server is well-scoped for grocery list management. Each tool addresses a distinct operation, and the count is neither too sparse nor overwhelming.
The tool set covers item-level operations (add, get, complete, remove, move) but lacks list-level create/delete operations and any way to update item details like quantity or note after creation. These are notable gaps for a grocery list management server.