The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Grocery MCP listing page.
A dedicated MCP and REST service that searches grocery retailers directly and returns reviewable product links. It starts with:
This service does not add products to carts, place orders, store retailer
credentials, or handle payment. Every response explicitly reports
cart_prefilled: false; the user opens the links, adds products, and checks out
on the retailer's own site.
HTTP endpoints:
http://localhost:8080/mcphttp://localhost:8080/healthhttp://localhost:8080/docshttp://localhost:8080/v1/retailershttp://localhost:8080/v1/products/searchPOST http://localhost:8080/v1/handoffsWhen DATABASE_URL is configured, handoffs and OAuth dynamic client
registrations are persisted in PostgreSQL. Without it, local development uses
process memory.
find_grocery_retailerssearch_grocery_productscreate_grocery_handoffget_grocery_handoffcreate_grocery_order_templatelist_grocery_order_templatescreate_handoff_from_templateExample handoff input:
Product names, prices, availability, and links come from each retailer's public customer storefront at request time. These storefront interfaces are not formal partner APIs and can change without notice. Responses include match confidence, alternatives, and observation timestamps so clients can make this uncertainty visible.
Matching requires strong token overlap, rejects obvious cross-category substitutions, and prefers available products. If no safe result exists, the item is explicitly unmatched rather than replaced with a loosely related item.
Reusable templates persist the retailer, location, and normalized grocery items. Running a template always performs fresh catalog searches and creates a new review-only handoff.