The grocery MCP
you run on your own stack.
Give any AI agent real supermarket superpowers. The Pepesto MCP server wraps our grocery API as tools — parse a list, match products, build a priced cart, hand off checkout — across 27 European chains. Self-hosted via npm or Docker, with your own API key.
# run the Pepesto grocery MCP locally $ PEPESTO_API_KEY=pep_sk_… npx -y @pepesto/pepesto-mcp→ pepesto MCP listening over stdio → tools: oneshot · predirect · parse · suggest · products · catalog → 27 chains · 13 countries · 1 schema
Make sure you're on the right one.
Pepesto ships two Model Context Protocol servers. This page is the developer one. If you just want to shop from a chat, you want the other.
Grocery MCP (self-hosted)
Run it yourself with npm or Docker. Exposes the full Pepesto API as tools so your agent can parse, match, price and check out programmatically. Brings your own API key.
Agent to Cart (hosted)
Zero setup. Connect mcp.pepesto.com in any AI chat, ask for groceries, and get a one-tap link that opens a real cart in the Pepesto app. No key, no hosting, no code.
Real grocery tools, not a wrapper around search.
Each tool maps to a Pepesto endpoint. An agent chains them to go from a recipe or a plain-text list to a priced, matched cart with a checkout link. The MCP covers the recipe → matched-cart half; placing the order happens in the app or via the link.
Also includes pepesto_credits (free balance check). Full request/response details live in the API reference →
Up and running in one command.
Self-host the server next to your agent. Pick npm for local dev, Docker for anything you deploy. All it needs is your Pepesto API key.
Get an API key
Start with a pay-as-you-go credit pack on pricing, then mint a key by calling /link with that email. It's returned once — store it immediately. (The free pepesto_predirect tool needs no key at all.)
$ curl -X POST https://s.pepesto.com/api/link \ -H "Content-Type: application/json" \ -d '{"email":"you@example.com"}' # → returns your key, once PEPESTO_API_KEY=pep_sk_…
Start the server
Run it locally with npx, or build the container from the repo. The server speaks MCP over stdio, so any compliant client can talk to it.
# local dev — speaks MCP over stdio $ PEPESTO_API_KEY=pep_sk_… npx -y @pepesto/pepesto-mcp
$ git clone https://github.com/pepesto-solutions/pepesto-mcp $ docker build -t pepesto-mcp pepesto-mcp $ docker run -e PEPESTO_API_KEY=pep_sk_… pepesto-mcp
Connect your MCP client
Point Claude Desktop, Cursor, or your own agent at the server. In Claude Desktop, add it to claude_desktop_config.json:
{
"mcpServers": {
"pepesto": {
"command": "npx",
"args": ["-y", "@pepesto/pepesto-mcp"],
"env": { "PEPESTO_API_KEY": "pep_sk_…" }
}
}
}Or, in Claude Code, one line:
$ claude mcp add pepesto -e PEPESTO_API_KEY=pep_sk_… \ -- npx -y @pepesto/pepesto-mcp
Source, full tool reference and roadmap: github.com/pepesto-solutions/pepesto-mcp →
Which Pepesto MCP fits.
Same grocery network underneath. Different surface, audience and setup.
| Grocery MCP — developers | Agent to Cart — end users | |
|---|---|---|
| Who it's for | Developers & AI agent builders | Individuals shopping from any chat |
| Hosting | Self-hosted — npm / Docker / local | Hosted by Pepesto — mcp.pepesto.com |
| Scope | Core grocery API as tools | One job: hand back a cart link |
| Auth | Your API key (pep_sk_…) | None needed to start |
| Output | Structured data + a checkout link | One-tap link to the Pepesto app |
| Best for | Building grocery into a product | Shopping quickly from anywhere |
Ship grocery into your agent
this afternoon.
Get an API key, run the server, and your agent can build real supermarket carts across Europe.
Just want to shop, not build? Try Agent to Cart →