# Fixing problems with the MCP connection

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

> What an error means when you connect to or call Athaus für Anbieter and Athaus Immobiliensuche, and what to do about it.

Type: Guide
Last updated: 2026-11-10

Find the sign you see. The connection belongs to one of the [two MCP servers](/en/mcp).

## Sign-in and access [#sign-in-and-access]

### The sign-in does not open or keeps restarting [#anmeldung]

Without a valid token the server answers `401` with `WWW-Authenticate`; that is the normal start. Sign in to Athaus, consent on [app.athaus.ai/verbinden](https://app.athaus.ai/verbinden) and check the address: `https://anbieter.mcp.athaus.ai/mcp` for providers, `https://suche.mcp.athaus.ai/mcp` for search.

### An existing connection returns 401 with `invalid_token` [#invalid-token]

The token is no longer valid: expired (one hour), from the other server, the connection was disconnected or lost its base right, the `ath_` key is unknown or revoked, or a key was used at Athaus Immobiliensuche (which only takes OAuth). The description in the error (in German) names the reason. Remove the connection in your app and connect again; for a key, create a new one in [Settings, API keys](https://app.athaus.ai/einstellungen/api-keys).

### The account has no access to the server [#produkt]

Athaus für Anbieter needs a provider account with an active membership in an office, Athaus Immobiliensuche a search account. Otherwise you get `401` with "Dieses Konto hat keinen Zugang zum Produkt dieses Servers ..."; on the API routes the code is `seite_fehlt` (`403`, [Error codes](/en/api/fehlercodes)). Sign in with the account of the right side and finish its setup; if you use both, connect each server with the account of its side.

### The plan has no connections to assistants [#plan]

Basic includes neither connections to assistants nor API keys, Pro and Scale as many as you like; older contracts keep them. Otherwise Athaus für Anbieter answers `401` with "Verbindungen zu Assistenten und API-Schluessel gehoeren zum Tarif Pro oder Scale ..."; a key on another API route gets `403` with `tarif_zu_klein`. Change the plan under [Billing](https://app.athaus.ai/abrechnung) ([How to change your plan and pay](/en/anleitungen/plan-und-bezahlung)).

## Rights and cards [#rights-and-cards]

### A tool says a right is missing [#recht]

With OAuth you get `403` with `insufficient_scope`; ChatGPT shows a tool error "Dafür fehlt der Verbindung das Recht ...". Connect again and switch the right on on the consent page; the boundary right (`freigeben`, `anfragen`) is off there until you switch it on. A key cannot ask for a right afterwards: create one with the right ([Keys](/en/api/schluessel)). Which right applies to what: [MCP rights](/en/mcp/rechte).

### The card is waiting but nothing went out [#klick]

Whatever goes out, replaces or deletes waits for your click; a card is valid for 15 minutes. Click while it is valid, or ask the assistant to prepare it again. If it shows **In Athaus freigeben**, the connection lacks the boundary right: approve in the app. If the kind is set to **Aus** there, the assistant prepares nothing ([Approval levels](/en/anleitungen/freigabe-stufen)).

### ChatGPT does not run a tool that writes [#chatgpt]

According to OpenAI, full MCP with write actions only exists in Business, Enterprise and Edu ([Installation](/en/mcp/installation#chatgpt)). Use Claude or do the step in the app.

## Rate and size [#rate-and-size]

### The server answers 429 [#drossel]

More than 30 calls at once, then more than one per second, per account; `send_inquiry` has further limits ([Limits](/en/mcp/grenzen#anfragen-an-anbieter)). Wait as long as `Retry-After` says, and poll every 30 to 60 seconds in a sync.

### The server answers 413 or 403 without a hint about rights [#groesse]

* **`413` with `payload_too_large`:** The body was larger than 512 KB ([Limits](/en/mcp/grenzen)).
* **`403` on a call from a browser:** A call with the `Origin` header of a foreign site is rejected; assistants call without this header.

## A subscription to events does not work [#events]

`events/subscribe` needs an OAuth connection with the event's right, an `https` address with a public IP and no redirect, and the confirmation within 10 seconds; the codes `-32012` to `-32015` name the reason ([Errors](/en/mcp/ereignisse#fehler)). Answer the confirmation with the `challenge` and subscribe through OAuth instead of a key.

## Next [#next]

The general [troubleshooting](/en/hilfe/fehlerbehebung) and the [error codes](/en/api/fehlercodes).
