FlatHunt

About

FlatHunt searches furnished apartments, studios, private rooms and shared rooms in Berlin from several providers. You can filter by price, size, rooms, district, availability dates, amenities and rental-policy flags, read listing details, compare listings side by side, and show listing cards in a gallery widget.

The server runs as a hosted streamable HTTP endpoint. Searching, listing details, comparison and the widget need no sign-in or API key. Saving listings and managing search alerts require signing in with OAuth.

What you can do

• Search Berlin furnished listings with price, size, room and date filters
• Filter by district or by coordinates and radius
• Get full details for a single listing
• Compare 2 to 10 listings side by side
• Render listing cards in an interactive gallery
• Save favourite listings and manage them (sign-in required)
• Create and delete search alerts (sign-in required)

Tools 12

• search_listingsRead-only

  Search furnished Berlin listings by price, size, rooms, area, dates, amenities and policy flags.

• get_listingRead-only

  Get full details for one listing by numeric id.

• compare_listingsRead-only

  Return normalized details for 2 to 10 listings for side-by-side comparison.

• list_citiesRead-only

  List FlatHunt cities

• list_areasRead-only

  List Berlin districts and neighbourhoods with canonical ids.

• render_listings_widgetRead-only

  Return UI cards and a gallery for 1 to 10 listings.

• list_alertsRead-only

  List the signed-in user's saved search alerts.

• create_alertWrites

  Create a saved search alert for new matching listings.

• delete_alertCan delete

  Delete one or more saved search alerts by id.

• list_saved_listingsRead-only

  List the signed-in user's favourite listings.

• save_listingWrites

  Save a listing to the user's favourites.

• remove_saved_listingCan delete

  Remove a listing from the user's favourites.

Read from the live server on 12 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.

Example prompts

• Find a furnished studio in Kreuzberg under 1,200 EUR available from December

• Compare listings 1234 and 5678 for me

• Which Berlin districts can I filter by? Show Neukölln ids

• Set up an alert for 2-room apartments in Mitte with Anmeldung

Set up

Every client connects to mcp.flat-hunt.com. Pick yours; the page remembers your choice.

claude mcp add --transport http flathunt https://mcp.flat-hunt.com/mcp

https://mcp.flat-hunt.com/mcp

{
  "mcpServers": {
    "flathunt": {
      "url": "https://mcp.flat-hunt.com/mcp"
    }
  }
}

code --add-mcp '{"name":"flathunt","type":"http","url":"https://mcp.flat-hunt.com/mcp"}'

{
  "servers": {
    "flathunt": {
      "type": "http",
      "url": "https://mcp.flat-hunt.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "flathunt": {
      "serverUrl": "https://mcp.flat-hunt.com/mcp"
    }
  }
}

codex mcp add flathunt --url https://mcp.flat-hunt.com/mcp

[mcp_servers.flathunt]
url = "https://mcp.flat-hunt.com/mcp"

gemini mcp add --transport http flathunt https://mcp.flat-hunt.com/mcp

{
  "mcpServers": {
    "flathunt": {
      "type": "http",
      "url": "https://mcp.flat-hunt.com/mcp"
    }
  }
}

Embed

Show FlatHunt in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge Website card iframe JSON AI prompt

README badge

Markdown

[![FlatHunt on mcp.tc](https://mcp.tc/i/flathunt/badge.svg)](https://mcp.tc/i/flathunt)

HTML

<a href="https://mcp.tc/i/flathunt"><img src="https://mcp.tc/i/flathunt/badge.svg" alt="FlatHunt on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML

<script src="https://mcp.tc/w/flathunt.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML

<iframe src="https://mcp.tc/embed/flathunt" title="FlatHunt on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/flathunt.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the FlatHunt card to your site.

Markdown

Add the mcp.tc card for FlatHunt, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/flathunt.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="flathunt"><a href="https://mcp.tc/i/flathunt">FlatHunt on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![FlatHunt on mcp.tc](https://mcp.tc/i/flathunt/badge.svg)](https://mcp.tc/i/flathunt)
```

Reference: https://mcp.tc/embed

Change history

We read this server’s tool list every 3 hours and record what changes. Last read 12 Nov 2026, 11:36 UTC.

1. 11 Nov 2026, 14:53 UTC, Automatic check

   3 tools changed.

   Details, 11 Nov 2026, 14:53 UTC

   Changed 3

   • compare_listingsoutput schema
   • get_listingoutput schema
   • search_listingsoutput schema

2. 9 Nov 2026, 11:52 UTC, Automatic check

   2 tools changed.

   Details, 9 Nov 2026, 11:52 UTC

   Changed 2

   • render_listings_widgetinput schema and output schema
   • search_listingsoutput schema

3. 9 Nov 2026, 02:51 UTC, Automatic check

   1 tool added and 7 tools changed. Server instructions changed.

   New server instructions

   Details, 9 Nov 2026, 02:51 UTC

   Added 1

   • list_citiesRead-only

     List the cities FlatHunt covers (Berlin plus European university cities) with the canonical `city` id to pass to search_listings and create_alert, country, currency, how many listings are live, and whether district polygons (list_areas) exist for it. Berlin is the default city: omit `city` for Berlin. Call this when the user names any other city, or asks where FlatHunt works.

   Changed 7

   • compare_listingstitle, output schema and hints

     title

     Before

     Compare Berlin listings

     After

     Compare listings

   • create_alertdescription and input schema
     Before

     Create a saved search alert so FlatHunt notifies the user about new matching Berlin listings. Accepts housing, price, size, rooms, availability, canonical area ids, amenity and rental-policy filters. Email notifications are enabled by default; Telegram too when the user has linked Telegram on FlatHunt. Requires the alerts.write scope.

     After

     Create a saved search alert so FlatHunt notifies the user about new matching listings in the chosen city (Berlin unless `city` is set). Accepts housing, price, size, rooms, availability, canonical area ids, amenity and rental-policy filters. Email notifications are enabled by default; Telegram too when the user has linked Telegram on FlatHunt. Requires the alerts.write scope.

     • New parameters: city
     • Description of areas
       Before

       Canonical Berlin area IDs from list_areas (e.g. berlin:ortsteil:prenzlauer-berg). Up to 20 IDs; multiple IDs are combined with OR. District / Ortsteil mode — do not mix with lat/lng/radiusKm. When th…

       After

       Canonical area IDs from list_areas (Berlin only, e.g. berlin:ortsteil:prenzlauer-berg). Up to 20 IDs; multiple IDs are combined with OR. District / Ortsteil mode — do not mix with lat/lng/radiusKm. W…

     • Description of postCode
       Before

       Exact Berlin post code (PLZ), e.g. 10115.

       After

       Exact post code in the searched city, e.g. 10115 (Berlin).

   • get_listingdescription, title, output schema and hints
     Before

     Get detailed information about a single FlatHunt listing in Berlin by its numeric id. Returns its description, amenities, rental-policy flags, capacity, stay terms, utilities, nearby distances, media, provider and tracking URLs. Availability and provider terms may change.

     After

     Get detailed information about a single FlatHunt listing by its numeric id (any city). Returns its description, amenities, rental-policy flags, capacity, stay terms, utilities, nearby distances, media, provider and tracking URLs. Availability and provider terms may change.

     title

     Before

     Get Berlin listing details

     After

     Get listing details

   • list_areasdescription, title, input schema, output schema and hints
     Before

     List supported Berlin districts (Bezirke) and neighbourhoods (Ortsteile) with canonical FlatHunt ids. Returns id, name, slug, type and parent area information, with optional name and type filtering. Mitte exists both as a whole Bezirk (berlin:bezirk:mitte) and as a smaller Ortsteil (berlin:ortsteil:mitte). Charlottenburg is an Ortsteil; the parent Bezirk is Charlottenburg-Wilmersdorf.

     After

     List district polygons (Berlin: Bezirke and Ortsteile) with canonical FlatHunt ids for the `areas` filter. District catalogs exist only for cities where list_cities reports hasAreas (today: Berlin, the default). For other cities search by city, post code or lat/lng/radiusKm. Returns id, name, slug, type and parent area information, with optional name and type filtering. Mitte exists both as a whole Bezirk (berlin:bezirk:mitte) and as a smaller Ortsteil (berlin:ortsteil:mitte). Charlottenburg is an Ortsteil; the parent Bezirk is Charlottenburg-Wilmersdorf.

     title

     Before

     List Berlin districts catalog

     After

     List districts catalog

     • New parameters: city
   • list_saved_listingsoutput schema
   • render_listings_widgetoutput schema
   • search_listingsdescription, title, input schema, output schema and hints
     Before

     Search current furnished apartments, studios, private rooms and shared rooms in Berlin through FlatHunt. Supports price, size, rooms, bedrooms, canonical area ids or nearby coordinates, availability dates, capacity, deposit, providers, amenity tags, rental-policy flags, sorting and pagination up to 20 results. Returns normalized listing summaries and pagination metadata. Availability, prices and provider terms may change.

     After

     Search current furnished apartments, studios, private rooms and shared rooms through FlatHunt in Berlin (default) or any city from list_cities via `city`. Supports price, size, rooms, bedrooms, canonical area ids (Berlin) or nearby coordinates, availability dates, capacity, deposit, providers, amenity tags, rental-policy flags, sorting and pagination up to 20 results. Returns normalized listing summaries and pagination metadata. Availability, prices and provider terms may change.

     title

     Before

     Search Berlin furnished listings

     After

     Search furnished listings

     • New parameters: city
     • Description of areas
       Before

       Canonical Berlin area IDs from list_areas (e.g. berlin:ortsteil:prenzlauer-berg). Up to 20 IDs; multiple IDs are combined with OR. District / Ortsteil mode — do not mix with lat/lng/radiusKm. When th…

       After

       Canonical area IDs from list_areas (Berlin only, e.g. berlin:ortsteil:prenzlauer-berg). Up to 20 IDs; multiple IDs are combined with OR. District / Ortsteil mode — do not mix with lat/lng/radiusKm. W…

     • Description of postCode
       Before

       Exact Berlin post code (PLZ), e.g. 10115.

       After

       Exact post code in the searched city, e.g. 10115 (Berlin).

   Server instructions

   Before

   You are FlatHunt's Berlin housing co-pilot: a sharp, warm, decisive friend who helps people actually find and rent furnished apartments, studios, private rooms, and shared rooms in Berlin. Guide the user from a vague need to a verified shortlist and an informed next step. Do not dump listings or let a provider link substitute for explaining a recommendation. Search, get_listing, compare, and the listings widget work without login. Save listing and create_alert require the user to be signed in (OAuth). Tone: expert friend who knows Berlin housing. Be specific, opinionated when helpful, never vague. Match the user's language. Keep replies scannable (short paragraphs, bullets for options). Celebrate good finds briefly; never hype a weak match. Never sound helpless or bureaucratic. Personalization (use conversation history + tools, never invent preferences): - Remember and reuse stated constraints: budget, rooms, move-in date, must-have amenities, commute goals, vibe (quiet / nightlife / family / students), and areas already discussed. - When authenticated, call list_saved_listings and list_alerts early if relevant — use them as taste signals; reference them naturally. - If preferences conflict with inventory, say so and propose the best trade-offs (budget bump, adjacent Ortsteil, later availableFrom). - Ask at most 1–3 clarifying questions when a search would be guesswork. Prefer searching with sensible defaults over interrogation. Filters and soft criteria: - One precise search_listings with backend filters ≫ paging then hand-filtering. Put every hard constraint in that one call (limit max 20). Paginate only when meta.totalPages > 1 and the user asks for more — never page to drop small flats or wrong districts. - Structured filters: priceMin/priceMax, squareMetersMin/squareMetersMax, rooms[] (exact OR) or roomsMin/roomsMax, bedroomsMin, areas (list_areas ids — district polygons) OR lat+lng+radiusKm (nearby; never mix geo modes), availableFrom/availableTo (YYYY-MM-DD)…

   After

   You are FlatHunt's housing co-pilot: a sharp, warm, decisive friend who helps people actually find and rent furnished apartments, studios, private rooms, and shared rooms in Berlin (the default city) and in the other European cities FlatHunt covers (list_cities: Lisbon, Porto, Madrid, Barcelona, Milan, Rome, Paris, Vienna … mostly Uniplaces student housing there). Guide the user from a vague need to a verified shortlist and an informed next step. Do not dump listings or let a provider link substitute for explaining a recommendation. Search, get_listing, compare, and the listings widget work without login. Save listing and create_alert require the user to be signed in (OAuth). Tone: expert friend who knows the local housing market. Be specific, opinionated when helpful, never vague. Match the user's language. Keep replies scannable (short paragraphs, bullets for options). Celebrate good finds briefly; never hype a weak match. Never sound helpless or bureaucratic. Personalization (use conversation history + tools, never invent preferences): - Remember and reuse stated constraints: budget, rooms, move-in date, must-have amenities, commute goals, vibe (quiet / nightlife / family / students), and areas already discussed. - When authenticated, call list_saved_listings and list_alerts early if relevant — use them as taste signals; reference them naturally. - If preferences conflict with inventory, say so and propose the best trade-offs (budget bump, adjacent Ortsteil, later availableFrom). - Ask at most 1–3 clarifying questions when a search would be guesswork. Prefer searching with sensible defaults over interrogation. Filters and soft criteria: - One precise search_listings with backend filters ≫ paging then hand-filtering. Put every hard constraint in that one call (limit max 20). Paginate only when meta.totalPages > 1 and the user asks for more — never page to drop small flats or wrong districts. - Structured filters: priceMin/priceMax, squareMetersMin/squareMetersMax…

4. 8 Nov 2026, 17:53 UTC, Automatic check

   5 tools changed.

   Details, 8 Nov 2026, 17:53 UTC

   Changed 5

   • compare_listingsoutput schema
   • get_listingoutput schema
   • list_saved_listingsoutput schema
   • render_listings_widgetoutput schema
   • search_listingsoutput schema

5. 15 Oct 2026, 16:28 UTC, Automatic check

   Tracking started: 11 tools.

FAQ