IKEA MCP server: let your AI agent check store stock and search products

#What your agent gets

Stock checks need the 8-digit IKEA article number. Article numbers differ by country, so take the number from search-products in the same market. For example, 80275887 is KALLAX white 77x147 in Germany. The market parameter covers 20 IKEA markets, and de/de is the default. A German article number in the US market returns no stock data.

In a live check on 7 November 2026, a stock check for the KALLAX article in Germany returned stock for four Berlin stores, between 38 and 59 units each, with aisle and bin. It took two requests and about 1.2 seconds.

#How a request flows

1. You ask your agent: "Is KALLAX white 77x147 (80275887) in stock at an IKEA in Berlin?"
2. The agent calls find_recipe, then run with ikea.com/check-stock, the article number and the city "Berlin".
3. wield-mcp passes the run through the local bridge to the Wield extension.
4. The extension sends the requests from an ikea.com tab, so they carry your own browser session.
5. The stock figures go back to your agent. Nothing passes through wield.run.

#What leaves your computer

The recipes send requests only to IKEA's hosts. Stock checks go to www.ikea.com and api.salesitem.ingka.com, and the product search goes to sik.search.blue.cdtapps.com. A stock check makes two requests, the same ones an IKEA product page makes when someone checks availability. Neither recipe uses an account or a cart.

Wield logs each request on your computer only: method, host, path, status and timing. It never logs bodies or query values. Telemetry is off by default. Wield never reads, copies or sends your cookies or passwords.

#IKEA terms, in plain words

We have not reviewed IKEA's terms as a lawyer would, so this is not legal advice. The recipes make the same requests a product page or the search box makes, one lookup at a time, with no account and no cart. Check IKEA's terms yourself before you automate anything beyond single lookups.

#Limits and what is not working yet

• Read only. The tools check stock and prices. They never add to a cart or order.
• Stock is per market. Use article numbers from the same market as the market parameter.
• Search always returns something. IKEA returns its closest matches, even for queries that match nothing, so check the product names in the result.
• Home delivery needs a postcode. Pass zip to check delivery to an address.
• No benchmark run yet. These recipes have no benchmark row, so we publish no speed comparison for them.
• Run limits apply. A run has at most 12 steps, 40 requests, 5 MB per response and 60 seconds.

#FAQ

#Is there an official IKEA MCP server?

Not that we know of as of 7 November 2026.

#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.

#Does it need an IKEA login?

No. Stock checks and product search work without an account.

#How fast is it compared with a browser agent?

These two recipes have no benchmark row yet, so we do not publish a speed comparison for them. The live check described above took about 1.2 seconds for the stock check. For the overall results across all benchmark tasks, see the benchmark.