Skip to documentation
FlatHunt MCP

Remote MCP serverStreamable HTTP

Berlin housing search,
ready for any MCP client.

Connect an AI assistant to live furnished-apartment search, comparable listing data, and optional account actions — through one portable Model Context Protocol endpoint.

https://mcp.flat-hunt.com/mcp
Connect your client Looking for the ChatGPT app?
Transport
Streamable HTTP
Tools
11 total
Public access
Search without sign-in
FlatHunt protocol map Production
One endpointFlatHunt MCP
HTTPS
Available immediatelyPublic housing tools
AreasSearchDetailsCompareCards

The widget is progressive enhancement. Clients without MCP Apps still receive complete structured and text results.

The contract

One server. No vendor fork.

FlatHunt is a thin, stateless gateway between MCP hosts and the FlatHunt housing platform.

Every compatible client uses the same endpoint and tool schemas. Host-specific metadata is limited to authentication and UI compatibility at the protocol edge.

No direct database accessBusiness rules stay in the FlatHunt API.
No token storageYour MCP host owns the OAuth session.
Provider hand-offApplications and bookings stay with the original provider.

Connect

Bring the endpoint to your client.

Start with anonymous search. Your client should ask you to sign in only when a favourites or alerts tool needs account access.

  1. Open Claude settings and add a custom connector.
  2. Paste https://mcp.flat-hunt.com/mcp.
  3. For Authentication choose Sign in when needed.
  4. For OAuth client choose Register automatically.

Capabilities

Eleven focused tools.

Public discovery stays frictionless. Personal state is separated behind explicit OAuth scopes.

Public tools

No sign-in
list_areas
Resolve Berlin districts and neighbourhoods to canonical area IDs.
search_listings
Search currently available furnished apartments, studios, and rooms.
get_listing
Retrieve safe, detailed information for one listing.
compare_listings
Compare two to ten listings with consistent fields and trade-offs.
render_listings_widget
Show one to ten listings as an interactive MCP Apps gallery when supported.

Account tools

OAuth required
list_saved_listings
List the signed-in user's favourites.
save_listing
Add a listing to favourites.
remove_saved_listing
Remove a listing from favourites.
list_alerts
List saved searches and their alert IDs.
create_alert
Create a named saved search from the same filters used for discovery.
delete_alert
Delete one or more saved-search alerts.

Authentication

Anonymous first. OAuth only when it adds value.

FlatHunt uses mixed authentication. A missing token is valid for public housing tools; protected actions return a standard authorization challenge that the host handles.

  • Authorization Code with PKCE S256
  • Dynamic Client Registration for public clients
  • Exact redirect URI validation
  • Minimum scopes for alerts and favourites
OAuth responsibility boundaryStandard discovery
  1. 1
    Your MCP host

    Discovers metadata, opens authorization, and stores the resulting tokens.

  2. 2
    FlatHunt authorization server

    Authenticates the user, grants scopes, and issues PKCE-bound tokens.

  3. 3
    FlatHunt MCP gateway

    Verifies the Bearer token and delegates only the requested user action.

Protected-resource metadata Authorization-server metadata

Compatibility

Portable by design. Verified by surface.

Tool discovery is not the same as a complete OAuth test. FlatHunt publishes the distinction so integrators know what has actually been exercised.

ChatGPTProduction verifiedOAuth read/write verified
Claude connectorAvailableDCR/PKCE supported; host smoke in progress
Codex, Cursor, VS CodeStandard remote MCPValidate the exact client callback
Other Streamable HTTP hostsProtocol compatibleHost-specific OAuth validation required

Clients without MCP Apps rendering still receive the same listing data and a model-readable text result. The interactive card gallery is an enhancement, not a dependency.

Public distribution

Discover FlatHunt MCP.

MCP endpoint
mcp.flat-hunt.com/mcp
Documentation
flat-hunt.com/mcp

Security & product boundaries

Useful context in. Minimal authority out.

01

Read-only by default

Search, details, comparison, and card rendering do not change user data.

02

Writes are explicit

Only favourites and saved-search alerts mutate account state, with dedicated scopes and tool annotations.

03

No rental transaction

FlatHunt never accepts rent or deposits. The original provider controls availability, applications, and final terms.

Reference

Common integration questions.

Need help with a review or client-specific callback?

hello@flat-hunt.com
Do users need a FlatHunt account?

No account is needed for area discovery, search, listing details, comparisons, or listing cards. A free account is required only for favourites and saved-search alerts.

Which transport should an integration use?

Use Streamable HTTP at https://mcp.flat-hunt.com/mcp. FlatHunt does not expose a legacy SSE, stdio, WebSocket, or vendor-specific function-calling endpoint.

Can a host connect without OAuth?

Yes. Public housing tools work anonymously. If the host supports lazy authentication, it should connect first and start OAuth only when the user invokes a protected account tool.

Where do listing images and applications come from?

Listing cards use allowlisted HTTPS image URLs from integrated housing providers. Applications and bookings are completed on the original provider's website, where current availability and final terms must be confirmed.

Ready to connect

One endpoint is all you need.

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