The Athaus MCP servers at a glance
Two servers, one for providers and one for searching. Athaus in ChatGPT, Claude, Cursor and any agent that speaks the Model Context Protocol.
Last updated:
Athaus has two MCP servers, one for each side of the market, each with its own address, rights and tools. An assistant such as ChatGPT or Claude reads, searches and drafts in Athaus through them; anything that goes out waits for your click (Rights). The names are German product names: Athaus für Anbieter for brokers, Athaus Immobiliensuche for property search.
| Athaus für Anbieter | Athaus Immobiliensuche | |
|---|---|---|
| For | Brokers and anyone who lists on Athaus | People looking for a flat or a house |
| Address | https://anbieter.mcp.athaus.ai/mcp | https://suche.mcp.athaus.ai/mcp |
| Account | a provider account | a search account |
| Sign-in | OAuth 2.1 or an ath_ key | OAuth 2.1 |
| Rights | lesen, vorschlagen, freigeben | suchen, suchauftraege, anfragen |
| More | Tools, Events, Limits | Tools, Events, Limits |
Which server is for you
- Providers: Athaus für Anbieter sees what your office sees in the app. Your plan must include connections to assistants (Pro or Scale).
- Seekers: Athaus Immobiliensuche only sees your own search, never an office.
- Both: add both addresses and connect each with the account of its side; a token is only valid at its own server.
The market tools (location, value range, demand, purchase costs) are on both. Every call requires sign-in; the cards in the chat appear in ChatGPT and Claude.
Keep reading
Install the MCP servers: Claude, ChatGPT, Cursor, VS Code
The two Athaus MCP servers in Claude, Claude Code, Cursor, VS Code, ChatGPT and your own agent.
Example prompts for the MCP servers
Ready-made sentences for Claude and ChatGPT, with the tool Athaus calls for each and the click you make afterwards.
MCP rights: what an agent may do
Three rights per server, independent of each other, and the rule for when a click is needed. In OAuth the rights are the scopes, under the same names.