> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.basement.chat/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.basement.chat/_mcp/server.

# Connect Claude

The Gateway is an MCP connector. You add the address in your assistant, sign in with your e-mail and approve the connection. After that, the assistant reads the documents, the tasks and the services of the organization that you selected, inside the access level that you selected.

|                       |                                                                         |
| --------------------- | ----------------------------------------------------------------------- |
| **Connector address** | `https://mcp.basement.chat/mcp` (the address without `/mcp` also works) |
| **Sign-in**           | Your e-mail and the code (or the passkey), as on the site               |
| **Approval**          | The organization, the access level and a name for the connection        |

#### Claude (web and desktop)

1. Open **Settings › Connectors** and click **Add custom connector**.
2. Enter the address `https://mcp.basement.chat/mcp` and click **Add**.
3. Click **Connect**, then sign in with your e-mail and the code.
4. On the approval screen, select the **Organization to connect**, the **Access level** and a **Connection name**. Click **Approve**.
5. In a conversation, enable the connector and ask your question.

#### ChatGPT

Open **Settings › Connectors**. Add an MCP connector with the address `https://mcp.basement.chat/mcp`. Sign in and approve in the same way.

#### Claude Code

Claude Code signs in with a key, not with the sign-in of the site. Create the key in **Agents › Connect agent**: keep **AI agent**, give a name, select the access level and click **Create key**. Copy the key. Then, in the terminal:

```bash
claude mcp add --transport http basement https://mcp.basement.chat/mcp \
  --header "Authorization: Bearer bsmt_your_key"
```

## The access level

The approval screen lists the access levels of the organization, with what each one gives in **Basement** and in the **Connected services**. The level **Analyst** is selected from the start.

The box **With this level, the agent reaches** shows Basement and each service that you connected in this organization. Each one shows **read**, **read and write** or **not in this level**. If a service of yours is connected in another organization, the box says which one: change the organization before you approve. Select the level and click **Approve**.

Every organization has four ready levels:

* **Researcher**: reads documents, files, skills and tasks. Writes nothing. Uses no services.
* **Analyst**: reads Basement and every connected service (SAP, Jira, GLPI, MultiDados, another MCP server). Writes nothing.
* **Operator**: reads and writes documents, skills, files and tasks. Uses no services.
* **Full access**: reads and writes Basement and every connected service.

An admin can create other levels, for example a level that reads only SAP. See [Sign in and get to know the organization](/start/sign-in) for the levels, and [Services](/services/overview) for what each service gives.

The assistant always sees the same tools. The level decides which calls are accepted. When a call is refused, the assistant says why, and what to do.

## To change the level

On the site, open **Agents › Connected**. Open the connection and select a different level in **Role**. Then remove the connector in the assistant and connect again: the assistant loads the change only when it connects.

You change the level of your own connections. An admin changes the level of any connection and creates new levels.

> **Note**
>
> A connection made before October 5, 2026 has no access level, and the calls to services are refused. Remove the connector in the assistant, connect again and approve with a level. Or set the level in **Agents › Connected** and reconnect the assistant.

## To change the organization or to stop

* To change the organization, remove the connector in the assistant and connect again.
* To stop an agent, open **Agents › Connected** on the site and click **Revoke**. The agent stops immediately. The past calls stay in the activity log.

## Example questions

* "Which tasks are stuck this week?"
* "Summarize the customer onboarding document."
* "Which GLPI tickets are open in my name?"
* "Which dumps occurred today in SBX?"