> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dapta-mcp/key-concepts.md).

# Key Concepts

Before you connect, it helps to understand a few ideas. They explain how the connection authenticates, how Claude knows what to do, and how it keeps your data safe.

***

## 1. One API key per workspace

A single active key connects Claude to **one specific workspace**. The key is scoped to that workspace, so Claude only ever sees and touches that workspace's data. You never tell Claude which workspace to use: it is resolved from the key automatically.

* **One active key per workspace.** Revoke the existing key before creating a new one.
* **Shown once.** The key appears only at the moment you create it, and it cannot be recovered later. Save it right away.
* **Scoped and isolated.** Because the key is tied to a single workspace, Claude cannot reach other workspaces or accounts.

{% hint style="warning" %}
Treat your key like a password. If it is ever exposed, revoke it and create a new one.
{% endhint %}

***

## 2. You connect, you do not install anything

There is nothing extra to set up beyond connecting. Once Claude is connected, Dapta's workflow guidance is delivered to Claude automatically over the connection, at the moment it is needed. Claude already knows how to do things in Dapta.

That means you do not download folders, copy files, or manage anything on your side. From your point of view it is one thing: connect, and Claude is ready to help.

***

## 3. Preview, then confirm

This is the most important idea for trusting Claude with your workspace.

* **Reads happen directly.** Asking "how many calls did I get this week?" simply returns the answer. Nothing changes, so nothing needs confirming.
* **Changes are previewed first.** When Claude is about to change something (an agent, a prompt, a flow, or a support ticket), it shows you a preview of exactly what it will do and waits for your confirmation. **Nothing is applied until you say yes.**

This preview-then-confirm step prevents accidental or surprising changes to your workspace.

***

## 4. One active key, shown once, revoke to rotate

Your key is created in the Dapta app, on the **MCP Access** tab (titled "Connect Dapta to Claude"). You pick a workspace first, then create the key.

* **Shown once.** A one-time dialog titled "Save your new MCP key" appears when you create the key. Copy it then, because it cannot be recovered afterward.
* **One active key per workspace.** Each workspace has a single active key at a time.
* **Revoke to rotate.** To replace a key, revoke the current one and create a new one. Keys are kept in Dapta's secured systems.

***

## Next step

Ready to connect? The setup section walks you through creating your key and connecting your client.

{% content-ref url="/pages/mgrNs2Jy4B82jjw2FyzU" %}
[Setup & Connection](/dapta-mcp/setup.md)
{% endcontent-ref %}


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.dapta.ai/dapta-mcp/key-concepts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.