About Kroger
Kroger is an MCP server for querying Kroger-family grocery stores and product data. It serves shoppers and price researchers with store-specific prices, promotions, stock, and aisle details, alongside store lookup.
Key features
- 01Locate stores by US ZIP code
- 02Search products and shelf prices
- 03Check promotions and stock
- 04View product and aisle details
Use cases
- 01Find nearby Kroger-family stores
- 02Compare grocery prices by location
- 03Check whether an item is in stock
MCP support
Exposes store locator, product search, and product detail tools to MCP clients. It can run as a local stdio server or connect through the Pipeworx gateway.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://gateway.pipeworx.io/kroger/mcpclaude mcp add --transport http pipeworx-io-kroger https://gateway.pipeworx.io/kroger/mcp{"mcpServers":{"pipeworx-io-kroger":{"type":"http","url":"https://gateway.pipeworx.io/kroger/mcp"}}}Open in Cursor{"servers":{"pipeworx-io-kroger":{"type":"http","url":"https://gateway.pipeworx.io/kroger/mcp"}}}Open in VS Code{"mcpServers":{"pipeworx-io-kroger":{"type":"http","url":"https://gateway.pipeworx.io/kroger/mcp"}}}{"mcpServers":{"pipeworx-io-kroger":{"serverUrl":"https://gateway.pipeworx.io/kroger/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEmcp-kroger
Kroger MCP — grocery products, prices, and store locations (developer.kroger.com)
Part of Pipeworx — an MCP gateway connecting AI agents to 1882+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
| Tool | Description |
|---|---|
kroger_store_locator | Find Kroger-family grocery stores and supermarkets near a US ZIP code — covers Kroger, Ralphs, Fred Meyer, King Soopers, Fry's, Harris Teeter, QFC, Smith's, Dillons, Food 4 Less, Mariano's and more. Returns store names, addresses, phone, hours, and the location_id needed for price lookups. Example: kroger_store_locator({ zip_code: "45202" }) |
kroger_product_search | Search grocery products at Kroger-family supermarkets with real shelf prices, promo/sale prices, stock level, and aisle. Answers "how much does milk cost", "is X in stock", grocery price comparison. Give a zip_code (or location_id) to get store-specific prices; without one, only the national product catalog is returned (no prices). Example: kroger_product_search({ term: "whole milk", zip_code: "45202" }) |
kroger_product_details | Get full detail for one grocery product by its product_id — price, promo price, stock level, size, categories, aisle location, images. Pass zip_code or location_id for store-specific price/stock. Example: kroger_product_details({ product_id: "0001111041700", zip_code: "45202" }) |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"kroger": {
"url": "https://gateway.pipeworx.io/kroger/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/kroger/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1882+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/kroger_store_locator \
-H 'Content-Type: application/json' \
-d '{"zip_code":"45202"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/kroger_store_locator. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"kroger": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-kroger"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-kroger
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Kroger data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.