rohlik

Rohlik MCP Server connects Claude/Claude Desktop to Rohlik Group online grocery services across multiple regions. It exposes tools for core shopping (searching products, adding to cart, viewing cart contents, removing items, retrieving shopping lists), smart shopping (personalized meal suggestions, frequent item analysis, and interactive shopping guidance), and account/order information (delivery details, order history, upcoming orders, delivery slots, and more). To use it, configure the MCP server in your client (for example Claude Desktop) with the provided environment variables and point it at the appropriate Rohlik base URL to select a region. Once running, you can issue natural language prompts to search products, curate carts, and fetch account or delivery information using the available tool commands. The region can be changed by adjusting ROHLIK_BASE_URL to the corresponding region domain (e.g., rohlik.cz for Czech Republic, knuspr.de for Germany, gurkerl.at for Austria, kifli.hu for Hungary, sezamo.ro for Romania).

Prerequisites:

• Node.js and npm installed on your machine
• Access to a shell/terminal

Install the MCP server package (example uses the Rohlik MCP package):

# Install dependencies for the repository (if you are cloning this project)
npm install

# Build if necessary (for development mode, per repository instructions)
npm run build

Configure and run the MCP server via npx (as shown in the config example):

# Run via Claude/Claude Desktop configuration or directly in your environment
# Example: using Claude Desktop configuration as shown in the docs

Notes:

• Ensure you have valid Rohlik credentials and keep them secure
• The ROHLIK_BASE_URL determines the region; set it to the target country domain
• If you encounter authentication issues, you can enable debugging by adding ROHLIK_DEBUG=true in the env block (within your client config when available)

Tips and common issues:

• If Claude Desktop cannot locate the MCP server, double-check the configuration file path for your OS and ensure the server name matches (rohlik).
• For region-specific behavior, always verify ROHLIK_BASE_URL corresponds to the desired country site; leaving it unset defaults to rohlik.cz (Czech Republic).
• In development, you can use rohlik-local configuration (node-based) with your local index.js and still provide ROHLIK_USERNAME, ROHLIK_PASSWORD, and ROHLIK_BASE_URL.
• If API endpoints change, you may need to update environment or re-authenticate; enabling ROHLIK_DEBUG will help diagnose issues.
• Remember to keep credentials out of version control; use environment management or secret vaults where possible.