# MCP sign-in: OAuth, consent and keys

Adresse: https://docs.athaus.ai/en/mcp/anmeldung

> OAuth 2.1 for apps such as Claude and ChatGPT, a key for your own agents. Every call requires a sign-in, and consent applies per server.

Type: Reference
Last updated: 2026-11-10

Each of the [two servers](/en/mcp) needs an Athaus account, even for `initialize` and `tools/list`. When an app acts for you (Claude, ChatGPT, Cursor, VS Code) it uses **OAuth 2.1**; your own agent without a browser takes an [`ath_` key](/en/api/schluessel), which only works with Athaus für Anbieter. If something does not work, see [Troubleshooting](/en/mcp/fehlerbehebung).

## How sign-in works [#how-sign-in-works]

1. The app calls the server and gets `401` with the `WWW-Authenticate` header, naming the rights and the description of the sign-in.
2. You sign in to Athaus, for example with a code by email.
3. On [app.athaus.ai/verbinden](https://app.athaus.ai/verbinden) you see which app wants to connect to which server (the server follows from the address) and only its rights. The base right ([`lesen`](/en/mcp/rechte#lesen) or [`suchen`](/en/mcp/rechte#suchen)) is always on. [`vorschlagen`](/en/mcp/rechte#vorschlagen) and [`suchauftraege`](/en/mcp/rechte#suchauftraege) are on if the app asks for them. The boundary right ([`freigeben`](/en/mcp/rechte#freigeben) or [`anfragen`](/en/mcp/rechte#anfragen)) is off until you switch it on, unless you already gave it to this app at this server.
4. The app gets a token, valid for an hour, renewable and only at this server. Athaus checks the consent on every call: disconnecting blocks the app at once.

If an app registered itself, the page says its name is not verified: connect it only if you have just set it up yourself.

## Disconnecting [#disconnecting]

In [Settings, MCP](https://app.athaus.ai/einstellungen/mcp) under **Connected apps** you disconnect each connection on its own; that also ends its events.

## For client developers [#for-client-developers]

|          | Athaus für Anbieter                                                       | Athaus Immobiliensuche                                                 |
| -------- | ------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| Resource | `https://anbieter.mcp.athaus.ai/mcp`                                      | `https://suche.mcp.athaus.ai/mcp`                                      |
| Metadata | `https://anbieter.mcp.athaus.ai/.well-known/oauth-protected-resource/mcp` | `https://suche.mcp.athaus.ai/.well-known/oauth-protected-resource/mcp` |
| Scopes   | `lesen`, `vorschlagen`, `freigeben`                                       | `suchen`, `suchauftraege`, `anfragen`                                  |

For both: authorization server `https://www.athaus.ai/api/auth`, Authorization Code with PKCE and refresh token, registration by Client ID Metadata Document or Dynamic Client Registration. `resource` (RFC 8707) is required; the JWT carries it as `aud` and is valid only there, for an hour; DPoP is supported.

If a right is missing, the server answers `403` with `insufficient_scope` (the `scope` lists the existing and the missing right). An invalid, expired, revoked token, or one issued for the other server, gets `401` with `invalid_token`.
