Alza MCP

What alza-mcp MCP server does

The alza-mcp MCP server gives an MCP-aware agent access to Alza.cz shopping workflows. It can search the live catalog, retrieve product information, read reviews, compare products, inspect categories, and locate AlzaBox or showroom pickup points. The catalog workflow can be used without an account, as shown by the project’s catalog-only example.

Account-related capabilities include authentication, account status, profile and address operations, order history, payment methods, claims, documents, reviews, subscriptions, and other grouped functions. The server also includes cart operations, delivery and pickup selection, checkout preview, cancellation, and order placement. Order submission is guarded by an explicit one-time confirmation token.

This project belongs to the E-Commerce category and is not affiliated with, endorsed by, or supported by Alza.cz a.s. It is intended for personal or research use according to the project’s disclaimer.

How it works

The alza-mcp MCP server uses standard MCP over stdio, so an MCP client starts it as a local process. Internally, catalog access combines browser-based scraping with reverse-engineered Alza mobile and web APIs. Browser-backed calls use Playwright and may require its headless Chromium download.

Tools are organized into toolsets rather than exposed all at once. The catalog and authentication groups are enabled by default. Other groups, including basket and checkout, account management, orders and payments, reviews and subscriptions, watchdogs, chat, PC building, and advanced raw access, can be enabled with the toolset controls. This progressive disclosure reduces the number of tools shown to an agent until they are needed.

Setup and configuration

The standard installation runs the package with npx:

npx -y alza-mcp-community

Claude Code can add it with claude mcp add alza --scope user -- npx -y alza-mcp-community. Claude Desktop uses the same command and arguments in its MCP configuration. Cursor, Continue, VS Code, and other MCP clients use the same stdio command shape.

No environment variables or secrets are required for the basic installation. A normal npm or npx install runs a postinstall step that downloads Playwright’s headless Chromium, approximately 92 MB, and prepares the optional curl_cffi virtual environment. If postinstall scripts are skipped, Chromium downloads on the first browser-backed call instead. The project also provides a release .mcpb bundle for Claude Desktop.

Tools and capabilities

The default catalog toolset includes capabilities for:

• Searching products with keyword, price, stock, screen-size, brand, and attribute criteria.
• Retrieving full product details such as price, availability, brand, image, and URL.
• Comparing products, reading reviews, browsing categories, and finding pickup points.
• Using authentication tools and obtaining the mutation token required for guarded changes.

Enable basket_and_checkout before using cart, delivery, pickup, checkout, or order tools. Additional toolsets cover account data, orders and payments, reviews and subscriptions, price-drop and back-in-stock watchdogs, Alza’s chat, PC compatibility checks, and a raw mobile API access tool. report_issue remains available and produces a redacted issue draft when an unexpected tool failure or incorrect result should be reported.

Limitations and notes

The alza-mcp MCP server is unofficial and depends on Alza behavior that may change. Some functions use reverse-engineered APIs or browser automation, so they may require updates when the storefront changes. The package was renamed from alza-mcp to alza-mcp-community; existing saved login data under ~/.alza-mcp/ remains usable according to the README.

Checkout and account actions should be treated as consequential operations. Order placement requires the explicit one-time confirmation token, and the issue-reporting flow does not file GitHub issues automatically: an agent must show the redacted draft and obtain agreement before submitting one.