> 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/setup/verify.md).

# Verify your connection

Confirm the Dapta MCP is connected by asking "Who am I in Dapta?" and checking that Claude answers with your workspace and connection type.

Open a new chat in your AI client (Claude, ChatGPT, Codex or Cursor) and ask:

> **Who am I in Dapta?**

Claude calls `whoami` and answers with the workspace it is connected to and whether the connection is a login or an API key.

Then try a real read:

> **List my voice agents.**

If Claude returns the voice agents from your workspace, you are connected.

{% hint style="info" %}
Signed in with several workspaces? Claude first lists them by name and asks which one to use. Answer with the name and it continues.
{% endhint %}

***

## Try a guided task

> **Create a voice agent in Dapta**

Claude loads the matching guide, walks you through a few questions, and tells you what it is about to create before it does it.

***

## If it does not work

| Symptom                                                        | Likely cause                                                           | Fix                                                                         |
| -------------------------------------------------------------- | ---------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| Claude asks which workspace to use                             | You signed in and your account has several workspaces                  | Answer with the workspace name                                              |
| You signed in but no workspace is listed                       | Signing in reaches only the workspaces where you are an owner or admin | Ask your workspace owner to make you an admin, or to give you an API key    |
| Login page loops, or the connector shows an error in claude.ai | Stale connector session                                                | Remove the Dapta connector and add it again with `https://mcp.dapta.ai/mcp` |
| 401 "Invalid or revoked API key"                               | Wrong or revoked key                                                   | Check the key in **MCP Access**. Create a new one if needed                 |

For anything else, see [Troubleshooting](/dapta-mcp/troubleshooting.md).

***

## You are connected

{% content-ref url="/pages/68GXxevzYgw8Dgv8Kbzv" %}
[What Claude Can Do](/dapta-mcp/skills.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/dapta-mcp/setup/verify.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.