mydealz MCP server: let your AI agent search deals

#What your agent gets

The tool takes one required input, query, for example airpods, playstation 5 or lego. The optional input only_active is a boolean. It defaults to false. Set it to true to drop expired deals.

The result gives query and a deals list. Each deal has title, type, price_eur, next_best_price_eur, merchant, temperature, free_shipping, voucher_code, posted_at, expired, comments and url. temperature is the community's votes on the deal, and a hotter deal scores higher. posted_at is in UTC.

#Extension 0.1.12 or newer

The recipe reads each deal from the data the page holds for its card, parsed item by item. That needs Wield extension 0.1.12 or newer. An older extension makes wield-mcp return extension_outdated, so update the Wield extension before you use this tool.

#How a request flows

1. You ask your agent: "Find AirPods deals on mydealz, leave out expired ones, and show the price, the next best price and the voucher code."
2. The agent calls find_recipe, then run with mydealz.de/search-deals, query set to airpods and only_active set to true.
3. wield-mcp passes the run through the local bridge to the Wield extension.
4. The extension sends the search from a mydealz tab in your browser.
5. The deals go back to your agent. Nothing passes through wield.run.

In our check on 7 November 2026, an airpods search passed all 5 checks in one request, in 1.1 s. It returned 30 deals, and 19 of them had expired and were marked as such.

#What leaves your computer

A search makes one request to www.mydealz.de, for one search page. Wield logs the request on your computer only, with method, host, path, status and timing, and it never logs bodies or query values. Telemetry is off by default. Wield never reads, copies or sends your cookies or passwords.

#mydealz's terms, in plain words

mydealz's robots.txt disallows /search for bots, and it disallows filter parameters such as hide_expired and priceFrom. This recipe calls the search page itself, once per request you make, from your own browser, without filter parameters. The robots file has no rules for Claude agents, and the site sends no AI content signals. The recipe makes one request per call. It does not vote, comment or set alerts.

The scope is simple. Wield runs this recipe when you ask for it, for one search per call, from your own browser. It does not run bulk jobs, and it does not buy anything.

Our review of these terms is not finished, and this is not legal advice. Read mydealz's terms and its robots.txt yourself before you use the recipe in any other way.

#Limits and what is not working yet

• Read only. The recipe searches. It does not vote, comment, set alerts or log in.
• Expired deals are kept. They are marked as expired. Set only_active to true to drop them.
• Zero results come back empty. When nothing matches, the site shows its hottest deals of the day instead. The recipe skips those, so the tool returns an empty list.
• Community votes. temperature reflects votes, not a price check.
• Extension version. The tool needs Wield extension 0.1.12 or newer.
• Run limits apply. A run has at most 12 steps, 40 requests, 5 MB per response and 60 seconds.
• No benchmark yet. We have not benchmarked this recipe against a browser agent.

#FAQ

#Can the agent vote on a deal or set an alert?

No. The recipe only searches. It does not vote, comment, set alerts or log in.

#Does the search need a mydealz account?

No. Search works without an account.

#Why does the tool need extension 0.1.12?

Because it parses each deal from its card's data item by item. Older extensions cannot run that step, and wield-mcp returns extension_outdated.

#Which AI apps work with it?

Any MCP client. npx -y wield-mcp init sets up Claude Desktop, Claude Code, Cursor and Codex. Other MCP clients work with the standard stdio config.

#Where do the results go?

To your agent, on your own computer. The results never pass through wield.run.