MCP server for shufersal automation using Puppeteer
MCP server for shufersal automation using Puppeteer. The shufersal mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.
A Model Context Protocol server that provides automated shopping capabilities for the Shufersal website using Puppeteer. This server enables LLMs to interact with Shufersal's online shopping platform, search for products, create shopping lists, and add items to your cart.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Everything the assistant can do here goes through one of these:
open_shufersal — Open the Shufersal website and prepare for shopping (requires user login)Input — hasCreatedShoppingList (boolean): Whether a shopping list has been created beforehandsearch_shufersal — Search for products on Shufersal website (results sorted by purchase history)add_to_shufersal_cart — Add a product to the shopping cart (must be used after searching)Inputs — - product_id (string): Product ID from search resultsread_webpage_content — Read and convert webpage content to markdown formatcreate_shopping_list_table — Create a shopping list table in markdown format from recipe ingredientsTools — The Tools tool exposed by this serverResources — 1. Console Logs (console://logs) - Browser console output in text format - Includes all console messages from the browser automationBuilding — The Building tool exposed by this serverLinting — The Linting tool exposed by this serverThis sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Shufersal MCP's toolset — open_shufersal, Input, search_shufersal and 8 more — is a fair guide to whether it matches your workflow. It is maintained by matipojo; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| open_shufersal | Open the Shufersal website and prepare for shopping (requires user login) |
| Input | hasCreatedShoppingList (boolean): Whether a shopping list has been created beforehand |
| search_shufersal | Search for products on Shufersal website (results sorted by purchase history) |
| add_to_shufersal_cart | Add a product to the shopping cart (must be used after searching) |
| Inputs | - product_id (string): Product ID from search results |
| read_webpage_content | Read and convert webpage content to markdown format |
| create_shopping_list_table | Create a shopping list table in markdown format from recipe ingredients |
| Tools | The Tools tool exposed by this server. |
| Resources | 1. **Console Logs** (console://logs) - Browser console output in text format - Includes all console messages from the browser automation |
| Building | The Building tool exposed by this server. |
| Linting | The Linting tool exposed by this server. |
{
"mcpServers": {
"shufersal": {
"command": "node",
"args": ["<path/to/shufersal-mcp>/dist/index.js"],
}
}
}Configuration as documented by the project. Restart the client after saving.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.