FINN MCP server: let your AI agent search second-hand listings on FINN Torget

#What your agent gets

Wield's recipes use the same requests the FINN search page makes. In your agent, they show up as one tool through wield-mcp:

The tool takes query, which is required. Examples are sykkel (bicycle) and sofa. Optional inputs are min_price and max_price in NOK, condition, seller, type, sort and page. Each page holds up to 53 listings. The result also gives total and last_page, so your agent knows whether more pages exist.

The options are:

• condition: new (unopened), like_new, good, used (visibly used) or needs_repair.
• seller: any (the default), private or business.
• type: for_sale (the default), giveaway (free) or wanted (people looking to buy).
• sort: relevance (the default), newest, oldest, price_low or price_high.

#How a request flows

1. You ask your agent: "Find used bicycles on FINN under 2000 NOK, newest first."
2. The agent calls find_recipe, then run with finn.no/search-marketplace, query: "sykkel", max_price: 2000 and sort: "newest".
3. wield-mcp passes the run through a local bridge to the Wield extension in your browser.
4. The extension sends the search from a finn.no tab, so it runs the way your browser would run the search.
5. The listings go back to your agent. Nothing passes through wield.run.

Your agent can then open the url of any listing you choose. Contacting the seller stays on FINN, in your hands.

#What leaves your computer

The only host is www.finn.no. A search makes one request, and it goes out from your browser. Nothing passes through wield.run. 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. The design keeps your session and browsing data on your device. See the security notes for the full list.

The search needs no FINN login. Your agent does not sign in as you, and no account is involved.

#FINN's terms, in plain words

We have not reviewed FINN's terms as a lawyer would, so this is not legal advice. The recipe makes one request per search, the same request FINN's search page makes. FINN's robots.txt disallows URLs with sort= for bots. So the recipe sends sort only when you ask for an order other than relevance. The recipe does not send messages, make offers or save favourites. Check FINN's terms yourself before you automate anything else.

#Limits and what is not included

• Read only. The tool searches listings. It does not message sellers, make offers or save favourites.
• Prices are in NOK. min_price and max_price use Norwegian kroner, and each listing carries its own currency field.
• Sorting is optional. The default is relevance. Other orders are sent only when you ask for them.
• Run limits apply. A run has at most 12 steps, 40 requests, 5 MB per response and 60 seconds. This search uses one step.
• Results are website content. Your agent is told not to follow instructions found in listing text.

#FAQ

#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 a FINN login?

No. Search works without an account.

#Can the agent message sellers or make offers?

No. The recipe only searches. Open the url from a result to contact the seller on FINN yourself.

#What does the status mean?

On 7 November 2026 the recipe passed 6 of 6 checks in one request, in about 0.5 seconds. The status can change, so the live recipe card on this page shows the current state.