Pepesto MCP logo

Pepesto MCP

Turns recipe URLs, text, or images into supermarket product carts with prices across European grocery markets.

Install Pepesto MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "pepesto-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pepesto/pepesto-mcp"
      ],
      "env": {
        "PEPESTO_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 7 tools correctly (10d ago).

Overview

The pepesto-mcp MCP server connects agents to Pepesto's grocery-shopping API for turning recipes and shopping lists into matched supermarket products. It can parse recipes, search Pepesto's recipe graph, map ingredients to SKUs with prices, inspect catalogs, and return checkout or app handoff links. Most operations require a Pepesto API key and credits, while deferred shopping-list links are free and keyless. Reach for it when an agent needs recipe-based grocery planning across supported European supermarkets, but not order placement.

Use cases

  • Build a supermarket cart from a recipe URL
  • Compare recipe prices across supermarkets
  • Create a weekly merged shopping list
  • Hand off a shopping list to the Pepesto app
  • Search recipes before selecting ingredients

Key features

  • Recipe parsing from URLs, text, and images
  • Recipe-to-cart matching with live product prices
  • Search across Pepesto's recipe graph
  • Deferred shopping-list deep links
  • Supermarket catalog retrieval
  • Credit balance checks

Tools7

What Pepesto MCP lets your agent do. Expand a tool for its parameters.

Verified live~1.9k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 47d

What it can do

From the 7 tools this server returned when we ran it.

Handles credentials · 2Makes network requests · 2Read-only tools · 7
Network at startup3 connections
Files written at startupNone
Install scriptsprepare
npm provenanceSigned build
Package age168 days
Maintainers1

Observed 2026-10-14 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @pepesto/pepesto-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars7Stargazers on the source repository.
npm downloads183Package downloads in the last 30 days.
Last commit4mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed7Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Pepesto MCP works

What the pepesto-mcp MCP server does

The pepesto-mcp MCP server gives an MCP-compatible agent access to Pepesto's recipe-to-cart workflow. It accepts recipe URLs, plain text, and images, then helps identify ingredients and match them to real supermarket products with prices. Pepesto supports 26 European supermarkets, selected through a supermarket domain or identifier.

The workflow can begin with a known recipe, a search across Pepesto's recipe graph, or a shopping list. The result may be a matched cart and a redirect_url, or a deferred link that opens the list in the Pepesto app. The MCP covers preparation and product matching; it does not submit the grocery order.

How it works

For a known recipe, call pepesto_parse to obtain structured ingredients and a KgToken, then pass that token to pepesto_products with a supermarket. Multiple recipe tokens can be supplied together so shared ingredients are merged into one shopping list. Agents can also call pepesto_oneshot for a combined recipe-to-cart operation.

When the user wants suggestions first, pepesto_suggest searches Pepesto's recipe graph. The selected recipe can then be sent to pepesto_products. Running that tool against different supermarket domains allows an agent to compare resulting carts and totals.

pepesto_predirect follows a different model: it accepts a shopping list and returns a deferred deep link without performing matching immediately. The user completes the process in the Pepesto app and pays at checkout. pepesto_catalog returns a supermarket's full SKU set and should be used only when explicitly requested, with results cached. pepesto_credits reports remaining API credits.

Setup and configuration

Run the server through the published npm package with npx -y @pepesto/pepesto-mcp. Claude Desktop can start it through an MCP configuration using the PEPESTO_API_KEY environment variable. Claude Code can add the same command with claude mcp add and the key passed through its environment options.

Most tools require a Pepesto API key. The key is obtained by purchasing a pay-as-you-go credit pack and calling Pepesto's /link endpoint with the checkout email; the returned key is shown only once and should be stored immediately. Set it as PEPESTO_API_KEY before starting the process. pepesto_predirect is free and works without a key, and pepesto_credits is also free.

Tools and capabilities

The pepesto-mcp MCP server exposes these operations:

  • pepesto_oneshot: Builds a matched cart from a recipe and returns a checkout link.
  • pepesto_predirect: Creates a free, deferred app link from a shopping list.
  • pepesto_parse: Extracts ingredients and a KgToken from recipe URLs, text, or images.
  • pepesto_suggest: Searches Pepesto's recipe graph.
  • pepesto_products: Matches recipe tokens to supermarket products and prices.
  • pepesto_catalog: Retrieves a complete supermarket SKU dump.
  • pepesto_credits: Checks available credits.

Limitations and notes

Checkout is outside the MCP workflow. The tools stop at a matched cart with prices, or at a handoff link for the Pepesto app; /session, /checkout, and /link are not wrapped. A returned redirect_url therefore does not mean that an order has been placed.

pepesto_predirect is intended for a user-facing handoff: matching happens after the recipient opens the link, and the end user pays in the Pepesto app. For a developer integration that needs the basket matched before handoff, pepesto_oneshot is the relevant operation, with API usage charged to the client.

Full catalog retrieval is the most expensive catalog-related operation described in the documentation. Call it only after an explicit request and cache the response, preferably for at least a day. Supermarket availability and domain values must match Pepesto's supported markets.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Pepesto MCP

pepesto-mcp is an MCP server that connects AI agents to the Pepesto grocery-shopping API. Its main tools parse recipes, search recipes, map ingredients to supermarket products and prices, create matched carts, generate deferred app links, retrieve catalogs, and check credits across supported European supermarkets.

Install it by running `npx -y @pepesto/pepesto-mcp` from an MCP client configuration.

Most tools require `PEPESTO_API_KEY`, but `pepesto_predirect` works without a key and is free. `pepesto_credits` is also free. API keys come from Pepesto after purchasing a pay-as-you-go credit pack and linking the purchase email.

No, pepesto-mcp does not place orders. It stops at a matched cart with prices or returns a link for the user to continue in the Pepesto app; `/session`, `/checkout`, and `/link` are not wrapped.

Call `pepesto_predirect` with the shopping list. It returns a deferred deep link immediately, while parsing and product matching occur when the user opens it in the Pepesto app. The user pays at checkout.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPepesto MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/pepesto-mcp?style=directory)](https://allmcps.com/mcp/pepesto-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/pepesto-mcp"><img src="https://allmcps.com/api/badge/pepesto-mcp?style=directory" alt="Pepesto MCP on AllMCPs" /></a>