io.github.AndrewVG23/grocery-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | No | PostgreSQL connection string. If set, handoffs and OAuth dynamic client registrations are persisted in PostgreSQL. Without it, local development uses process memory. |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_grocery_retailersA | List supported grocery retailers and pickup storefront locations. |
| search_grocery_productsA | Search one retailer's public catalog and return ranked direct product links. Args:
retailer: |
| create_grocery_handoffA | Match a grocery list to direct retailer product links for manual checkout. Args:
retailer: |
| get_grocery_handoffB | Retrieve a previously generated product-link handoff. |
| create_grocery_order_templateA | Save a reusable grocery list without searching or placing an order. |
| list_grocery_order_templatesA | List reusable grocery order templates saved on this service. |
| create_handoff_from_templateA | Run fresh storefront searches for all items in a reusable template. |
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 7 tools
Each tool targets a distinct action: finding retailers, searching products, creating/retrieving handoffs, and managing templates. The purposes are clearly separated even where related, such as create_grocery_handoff vs create_handoff_from_template.
All tools follow a consistent snake_case verb_noun pattern (find, search, create, get, list). The naming is predictable and easy to infer, with no mixed conventions.
Seven tools is well-scoped for a grocery-specific MCP server. Each tool covers a necessary step in the workflow without redundancy or bloat.
Core workflows are covered: retailer discovery, product search, handoff creation/retrieval, and template creation/listing/use. Minor gaps exist such as no template deletion or update, but these are non-critical for the primary use case.