> For the complete documentation index, see [llms.txt](https://docs.kula.digital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kula.digital/connect-claude-and-access/claude.md).

# Connect Claude

Kula controls access by **rules and roles** — so you never point Claude at Kula directly. Instead you get a **personal connect link** from **app.kula.digital** that already carries exactly what you're allowed to see, and you add that link to Claude. There is no open, direct address to connect to; the connect link is your controlled door in.

## Step 1 — Get your connect link

1. Sign in to **app.kula.digital**.
2. Open **Connectors → New connector** and create one for the assistant you want to connect (for yourself, or for a team member). The **role/level** you choose decides what it can access — see [Permission levels](/connect-claude-and-access/scopes.md).
3. Copy the **connect link**. It looks like:

   ```
   https://mcp.kula.digital/connect/XXXXXXXX/mcp
   ```

   Treat it like a password — it's scoped to a role, but it's still a credential.

> Why a link and not an open address? Because access is the whole point. Every connection runs through a role-scoped link, so what each person can see stays under your control. We don't allow direct access to the data.

## Step 2 — Add it to Claude

1. In **Claude Desktop** or **claude.ai**, open **Settings → Connectors → Add custom connector**.
2. Fill in two fields:
   * **Name:** `Kula Intelligence`
   * **Remote MCP server URL:** your **connect link** from Step 1 (`https://mcp.kula.digital/connect/…/mcp`).
3. **Leave the Advanced settings (OAuth Client ID / Secret) blank** — Claude registers itself automatically; filling those in breaks the connection.
4. Click **Add**, then **Connect**. A browser window opens.
5. **Sign in to Kula and approve** the connection on the consent screen — it shows the studio's name and the access being granted.

You're returned to Claude and the connector shows as connected.

## Check it worked

Start a new chat and ask:

> *"List the tools you can use from Kula Intelligence."*

Claude should return the full list of tools. If it does, you're connected — and only seeing what your role allows.

## Set up by a consultant?

A consultant helping your studio can create the connect link for you and either hand it over or set it up on your behalf — the access is still yours, scoped to your rules. See [Set up on their behalf](/for-consultants/set-up-on-their-behalf.md).

## Using another assistant?

Claude's custom connector uses the OAuth connect link above. **Other AI clients** — ChatGPT, Cursor, Lovable, the Claude API, custom agents — connect with a **role-scoped access token** instead: you create one in app.kula.digital and it generates the ready-to-paste config for your platform. Same access control, different mechanism. See [Connect — API, Code, Cursor, Lovable](/for-developers/connect.md).

## Trouble connecting?

* **"401" / "invalid token"** → your connect link is expired or has already been used. Get a fresh one from **app.kula.digital → Connectors**.
* **"403" / "scope … cannot …"** → the action needs more access than your role allows. See [Permission levels](/connect-claude-and-access/scopes.md).
* More in [Troubleshooting](/connect-claude-and-access/troubleshooting.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kula.digital/connect-claude-and-access/claude.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.