Migros Mcp

migros-mcp

Lets Claude (and other AI apps) search Migros products, recipes, stores and promotions. Sign in, and it can also manage your basket and look up your orders, receipts and Cumulus points.

Unofficial. Not made or supported by Migros. It uses the same behind-the-scenes addresses as the Migros website, so it can break whenever Migros changes them. Use at your own risk.

Install

This is a fork. herp75/migros-mcp is lewpgs/migros-mcp with security hardening, live tests and more tools (see the CHANGELOG). It comes as a Docker image, ghcr.io/herp75/migros-mcp, and is listed in the MCP Registry as io.github.herp75/migros-mcp. The npm package migros-mcp and the Claude Desktop installer migros-mcp.mcpb are upstream's version, not this one.

It runs on your own computer, so it works in desktop apps that can start a program: Claude Desktop, Claude Code, Cursor and similar. It doesn't work on claude.ai in a browser or in the Claude phone apps. You need Docker or Podman.

Your login, in a file only you can read. Skip this to only search.

install -m 600 /dev/null ~/.config/migros-mcp.env"${EDITOR:-nano}" ~/.config/migros-mcp.env

[email protected]MIGROS_PASSWORD=your-password

One line each, no quotes. $, # and quotes in the password are fine (Docker reads the file as written). For 2FA without being asked for codes, add MIGROS_TOTP_SECRET=... (see Your Migros account).

The saved login lives in the Docker volume migros-mcp, so it survives restarts. That matters: Migros blocks computers that sign in too often.

Claude Code

claude mcp add migros -- docker run -i --rm \  --env-file ~/.config/migros-mcp.env -v migros-mcp:/config \  ghcr.io/herp75/migros-mcp:0.6

Leave out --env-file … to only search. With Podman, write podman instead of docker.

Claude Desktop, Cursor and other apps

Add this to the app's MCP config file, with your home folder in the path:

• Claude Desktop: Settings > Developer > Edit Config
• Cursor: ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project)

{  "mcpServers": {    "migros": {      "command": "docker",      "args": [        "run", "-i", "--rm",        "--env-file", "/home/you/.config/migros-mcp.env",        "-v", "migros-mcp:/config",        "ghcr.io/herp75/migros-mcp:0.6"      ]    }  }}

Other apps (VS Code, Windsurf, Zed and so on) run the same command but lay out their config a little differently. Check your app's MCP instructions.

Checking the image (optional)

Each image is signed with cosign, keyless, by the release workflow of this repository:

cosign verify ghcr.io/herp75/migros-mcp:0.6 \  --certificate-identity-regexp '^https://github.com/herp75/migros-mcp/\.github/workflows/(docker|release)\.yml@' \  --certificate-oidc-issuer https://token.actions.githubusercontent.com

Check that it works

Start a new chat and ask: "Search Migros for oat milk."

Your Migros account

Optional. Without it, product search, product details, stock, stores, promotions and recipes all work.

With it, Claude can also see and change your basket and shopping lists, look up your orders, in-store receipts and Cumulus points, and put Cumulus coupons on your card. It never places an order or pays. It gives you a checkout link, and you finish on migros.ch yourself.

What to enter depends on how you sign in to migros.ch:

Only codes from an authenticator app work. If your account uses a passkey only, or codes by SMS, add an authenticator app in your Migros account settings first.

Settings

All settings are environment variables. With Docker, put them in ~/.config/migros-mcp.env (see Install). None is required.

For development only: MIGROS_TEST_EMAIL, MIGROS_TEST_PASSWORD, MIGROS_TEST_TOTP_SECRET, MIGROS_LIVE_ENV_FILE and MIGROS_LIVE_SESSION_DIR (see Development).

What you can ask

Without an account:

• "Search Migros for protein bars"
• "What's the nutrition info for this product?"
• "Find Migros stores near Zurich"
• "What promotions does Migros have right now?"
• "Find me a risotto recipe"

With your account:

• "What's in my Migros basket?"
• "Add 2 litres of milk to my basket"
• "Add the ingredients for this recipe to my basket"
• "Show me my last 5 Migros orders"
• "How much did I spend at Migros last month?"
• "Which Migros stores did I shop at last month, and for how much?"
• "Which Cumulus coupons do I have? Activate the one for coffee."
• "Make a new shopping list for the weekend"
• "Give me the link to finish my checkout"

Updating

:0.6 follows the newest 0.6.x release (fixes only). To get it, pull the image and restart the app:

docker pull ghcr.io/herp75/migros-mcp:0.6

New features come with a new minor version (:0.7): change the tag in your config. Releases are listed on the releases page and in the CHANGELOG. The image doesn't check for updates itself (MIGROS_MCP_UPDATE_CHECK is off in it).

Privacy and safety

• Your email, password and setup key are only ever sent to Migros' own login page (login.migros.ch). A 6-digit code you give Claude is used for that one sign-in and never stored or logged.
• Your password and setup key sit in ~/.config/migros-mcp.env, readable only by you, not in the app's config file.
• Once you're signed in, the saved login (cookies and an access token) stays on your computer, in session.json in the Docker volume migros-mcp. docker volume rm migros-mcp signs you out. Inside the volume, only the server's user can read it. (Run without Docker, it's in ~/.config/migros-mcp/ on Linux, ~/Library/Application Support/migros-mcp/ on a Mac, %APPDATA%\migros-mcp\ on Windows.)
• Your email, password, setup key, cookies and access token are masked in error messages.
• Tools that change your basket are marked as such, so your app can ask you before running them. Leave that approval on.
• Give Claude the 6-digit code yourself. Don't let an AI that can act on your account also read your codes (for example from a password manager): then a text it reads could get it to sign in, and the second factor protects nothing.
• Product texts, recipes and order data come from Migros and other people. migros-mcp tells the AI to treat them as information, not as instructions.
• It never places orders or pays. get_checkout_link gives you a link, and you finish on migros.ch.
• Found a security problem? See SECURITY.md.

Troubleshooting

• "Too many requests" or other sign-in errors. Migros blocks computers that sign in too often. When that happens, migros-mcp stops trying for a while on its own (30 seconds at first, longer if it keeps happening) and keeps using your current login while it's still valid. The error says until when. Wait until then before trying again. Restarting the app over and over, or a wrong password, makes it worse.
• Something that used to work fails. Migros may have changed its website. Update to the newest version (see Updating), and if it still fails, open an issue.

Tools

These are what Claude calls behind the scenes. You don't need them to use it.

The Kind column says what a tool does to your account: reads, changes (nothing is lost) or deletes (removes or overwrites something). Your app uses this to decide when to ask you first. Keep that approval on for anything that isn't reads.

Without an account (all reads)

With your account

Development

How the code is laid out, and how a tool is added: docs/architecture.md. How to contribute: CONTRIBUTING.md.

git clone https://github.com/herp75/migros-mcp.gitcd migros-mcpnpm installnpm run buildnpm test

Before a pull request, run the same checks as CI:

npm run typecheck      # TypeScript, including the testsnpm run lint           # ESLintnpm run format:check   # Prettier (npm run format fixes it)npm run test:coverage  # tests, failing below 80 % line coverage of src/

git config blame.ignoreRevsFile .git-blame-ignore-revs hides the one big formatting commit from git blame.

Check the tools that need no account against the live Migros website. GitHub also runs this every Monday, so a change on Migros' side shows up early:

npm run live-check

Check the tools that need an account, with a dedicated test account (never your own). Put its login in .env.live (git-ignored, chmod 600) as MIGROS_TEST_EMAIL, MIGROS_TEST_PASSWORD and, for 2FA, MIGROS_TEST_TOTP_SECRET. --write also adds a product to the basket, changes its quantity and removes it again, checking that the basket ends up as before. The test login is kept in .live-session/, so repeated runs don't sign in again each time.

Migros answers logins from GitHub's servers with a bot check, so this runs weekly on a computer instead: scripts/migros-live-check.sh pulls the published image (edge, built from main), checks its cosign signature, and runs the check with --write inside that image with rootless podman, so it tests what people install and nothing from the repo runs outside a container. It needs podman, skopeo and cosign; the saved test login is kept in ~/.local/state/migros-live-check/. To schedule it, copy scripts/systemd/migros-live-check.service and .timer to ~/.config/systemd/user/ and run systemctl --user enable --now migros-live-check.timer; results are in journalctl --user -u migros-live-check. The live workflow on GitHub can still be started by hand, to see whether GitHub's servers get through again.

npm run live-account              # read-onlynpm run live-account -- --write   # with the basket round trip

Try it with the MCP Inspector:

npx -y @modelcontextprotocol/inspector node dist/index.js

License

MIT, see LICENSE.