> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryecco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# AI integrations

> Ask Claude Code or Codex about your Ecco arrivals, bookings, and statistics with a personal, read-only token.

Connect Claude Code or Codex to Ecco and ask about your property in plain language: who arrives today, how last month went, how much of your plan you have used.

> [!NOTE]
>
> The connection is **read-only**. The assistant reads your data and cannot change anything: bookings, guest messages, and settings stay in Ecco.

## What your assistant can read

* Arrivals, departures, and bookings
* Your properties
* Statistics and monthly reports
* Plan usage

Guest conversation text is excluded by default. The assistant sees only what your Ecco account can see.

## Who can connect

You need the **owner** or **admin** role on the property you want to connect. Each token is personal and works for one property.

## Create your token

**1. Open AI integrations**

In the Ecco dashboard, open **Configuration** in the sidebar, select the property, then open the **AI integrations** tab.

**2. Create the token**

Select **Create token** and choose the **Duration**: 7, 30, or 90 days. Leave **Include guest conversations (message text)** off.

**3. Copy it now**

Copy the token and keep it in a password manager. Ecco shows it **only once**. Then select **I have saved the token**.

> [!WARNING]
>
> Never paste your token into an AI chat, email, ticket, or screenshot. If you think someone has seen it, revoke it right away.

## Connect your assistant

**Claude Code**

**1. Add the Ecco marketplace**

In your terminal, run:

```bash theme={null}
claude plugin marketplace add https://github.com/try-ecco/ecco-plugins
```

**2. Install the Ecco plugin**

```bash theme={null}
claude plugin install ecco@ecco
```

When asked for the **Ecco token**, paste your token. Claude Code stores it in your system keychain, not in a file.

**3. Start a new session**

Open a new Claude Code session and ask a first question.

**Codex**

**1. Set the token without saving it in your history**

In your terminal, run the first line, paste your token (it stays hidden), and press **Enter**. Then run the second line.

```bash theme={null}
read -rs ECCO_MCP_TOKEN
export ECCO_MCP_TOKEN
```

**2. Add the Ecco server**

```bash theme={null}
codex mcp add ecco --url https://be.tryecco.com/mcp --bearer-token-env-var ECCO_MCP_TOKEN
```

The command contains the name of the variable, never the token itself.

**3. Add the Ecco workflows**

```bash theme={null}
codex plugin marketplace add https://github.com/try-ecco/ecco-plugins
codex plugin add ecco@ecco
```

The plugin adds ready-made workflows on top of the connection.

**4. Start Codex from the same terminal**

Run `codex` in the terminal where you set the token and ask a first question.

> [!TIP]
>
> The token lasts only as long as that terminal window. Each time you open a new terminal, repeat the first step before starting Codex, or let your password manager supply `ECCO_MCP_TOKEN`.

## Try it

Start by checking the connection:

* “Which Ecco property am I connected to?”

Then ask what you need:

* “Who arrives and who leaves today?”
* “Show me the bookings for next weekend.”
* “How did last month go compared to the month before?”
* “How much of my plan have I used this month?”

Dates follow your property's timezone. Answers are based on the data already in Ecco.

> [!NOTE]
>
> For especially busy days, Ecco returns up to 200 bookings: arrivals first, then departures, then in-house stays. The assistant clearly tells you when the list is partial. In that case, any count shown is a minimum—for example, “at least 200 arrivals.”

## Revoke a token

Open **Configuration → AI integrations** and select **Revoke** next to the token. Access stops immediately. The same page shows when each token expires and when it was last used.

To replace a lost or expired token, create a new one and update your assistant with it. Ecco never shows an existing token again.

## Your data

The answers come from Ecco, and the assistant provider you use (Anthropic for Claude Code, OpenAI for Codex) receives the results it needs to answer. Treat these answers like any booking data: keep them confidential. Do not add passwords, door codes, payment details, or identity documents to your questions.

## Troubleshooting

Your assistant shows the error code Ecco returns. For the full list, see the [error reference](/ops/errors).

> **HTTP 401 or “unauthorized”**
>
> The token is missing, mistyped, expired, or revoked. Check its status in **Configuration → AI integrations**, then create a new token and set it up again. See [unauthenticated](/ops/errors#unauthenticated).

> **Codex worked, then stopped after a restart**
>
> The token was set in a terminal that has since closed. Desktop apps and new terminal windows do not see a variable set in another terminal. Set `ECCO_MCP_TOKEN` again and start Codex from that same terminal.

> **Claude Code did not ask for the token**
>
> Update Claude Code to the latest version and install the plugin again. Do not paste the token into the chat as a workaround.

> **The assistant sees no property**
>
> Check that you are signed in to Ecco as owner or admin of the property, then write to [support@tryecco.com](mailto:support@tryecco.com).

> **“Too many requests” (HTTP 429)**
>
> Each token and each property has a per-minute request limit. Wait a minute and ask again. See [rate\_limited](/ops/errors#rate_limited).

> **I don't see the AI integrations tab**
>
> The tab appears for owners and admins of the selected property. If you have one of these roles and still don't see it, write to [support@tryecco.com](mailto:support@tryecco.com).

Need help? Write to [support@tryecco.com](mailto:support@tryecco.com) with the assistant you use, the error message, and the request ID if shown. Never send your token.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.