Otodom MCP server: let your AI agent search flats and houses in Poland

#What your agent gets

The tool takes city as its one required value. The other filters are optional: transaction (rent or buy), property_type (flat, house or room), a price range in PLN, an area range in square metres, rooms (2, 3 or 4, flats only), sort and page. Each run returns one results page of up to 36 listings.

The 12 cities are a fixed list: warszawa, krakow, wroclaw, lodz, poznan, gdansk, gdynia, szczecin, katowice, lublin, bialystok and bydgoszcz. Each one was checked live on 7 November 2026. The recipe does not look up other places, so a town outside this list is not covered by this tool.

#How a request flows

1. You ask your agent: "Find flats to rent in Warsaw for up to 4,000 PLN with two rooms, cheapest first."
2. The agent calls find_recipe, then run with otodom.pl/search-properties and city: "warszawa", transaction: "rent", max_price: 4000, rooms: 2 and sort: "price_low".
3. wield-mcp passes the run through the local bridge to the Wield extension.
4. The extension sends the requests from an otodom.pl tab, so they run the way your browser would run them.
5. The listings go back to your agent. Nothing passes through wield.run.

In our check on 7 November 2026, the Warsaw rent search with these filters made 1 request and finished in 0.9 seconds.

#What leaves your computer

The only host the recipe calls is www.otodom.pl. A search makes one request for one results page, as a visitor's browser gets it. Requests go out with the session your browser already has. 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.

#Otodom's terms, in plain words

Otodom's robots.txt sets Content-Signal ai-input=no and ai-train=no, which signals that the site does not allow its content to be used for AI input or AI training. Wield runs this recipe only when you ask, in your own browser, one search page per call. The scope is set: you start each search, one search per call, from your own browser, with no bulk collection and no purchases. Terms not reviewed yet for automated access, so we cannot say whether this use is allowed. The recipe makes one request for one results page, the way a visitor gets it. robots.txt allows the /pl/wyniki/ results path. Contacting advertisers stays on otodom.pl. This is not legal advice. Check Otodom's terms yourself before you automate anything else.

#Limits and what is not working yet

• Read only. The tool searches. It does not contact advertisers or save listings.
• Fixed city list. Only the 12 cities above are covered.
• Rooms for flats only. rooms accepts 2, 3 or 4, and it applies to flats.
• Promoted listings are hidden. Paid placements are dropped by default. Set include_promoted to true to keep them, marked. A paid bump of a genuine listing is kept and shown, with its bumped_at time.
• Run limits apply. A run has at most 12 steps, 40 requests, 5 MB per response and 60 seconds.

#FAQ

#Is there an official Otodom MCP server?

The Otodom tool is a Wield recipe, made by Wield and not by Otodom. This page does not say whether Otodom offers an API or allows automated access. Check the site's terms.

#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 Otodom login?

No. The search needs no account.

#Can the agent contact a seller?

No. The recipe only reads search results. Contacting advertisers stays on otodom.pl.

#How does it compare with a browser agent?

Wield's preliminary benchmark, as of 7 November 2026, has no task for this recipe, so we have no speed or success figures to publish for it. The method and the tasks we did measure are on the benchmark page.