> 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/mint-your-api-key.md).
# Mint your API key
Create an API key for scripts, automations, or a connection fixed to one workspace. Keys are named, shown once, and a workspace can have up to 10.
An API key connects a client to **one** Dapta workspace without a login. Use it for automations and custom scripts, for clients that cannot sign in, or when you want a connection that is fixed to a single workspace.
{% hint style="info" %}
Using Claude, ChatGPT, Codex or Cursor yourself? You do not need a key. [Sign in with your Dapta account](/dapta-mcp/setup.md) instead.
{% endhint %}
***
**Step 1:** In the Dapta admin panel, click your account email at the bottom of the left sidebar, then choose **MCP Access**.
Open the account menu and choose MCP Access.
***
**Step 2:** Open **Advanced: connect with an API key**. The section is collapsed until you click it.
***
**Step 3:** Use the **Workspace** dropdown to pick the workspace the key is for. Each key belongs to a single workspace.
***
**Step 4:** Click **Create API key** and give it a name that tells you where it is used, for example "Production script" or "Cursor".
{% hint style="warning" %}
Only the workspace owner can create, rename and revoke keys. Other members see **Keys are managed by your workspace owner or admin**. You do not need a key to sign in: ask your owner only if you need one for a script.
{% endhint %}
***
**Step 5:** **Copy the key immediately.** The **Save your new MCP key** dialog shows it only once, together with ready-to-copy snippets:
* The **API key** itself.
* The **connector URL** for claude.ai and Claude Desktop, with the key included.
* The **Claude Code** command, and the **Codex** and **Cursor** config blocks.
Tick **I've saved this key in a safe place** to close the dialog.
{% hint style="danger" %}
Treat the key, and any URL that contains it, like a password. A lost key cannot be shown again: revoke it and create a new one.
{% endhint %}
***
## Use your key
All three forms reach the same server.
| Client | How the key travels |
| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **claude.ai / Claude Desktop** custom connector | Paste the connector URL the admin panel shows: `https://mcp.dapta.ai//mcp` |
| **Claude Code** | `claude mcp add --transport http --scope user dapta-ai https://mcp.dapta.ai/mcp --header "x-api-key: "` |
| **Cursor, Codex, custom scripts** | Header `x-api-key: ` (or `Authorization: Bearer `) on `https://mcp.dapta.ai/mcp` |
***
## Manage your keys
* **Several keys per workspace.** Create one per tool or teammate so you can tell them apart. A workspace can hold up to 10 active keys. When it is full, revoke an unused key to create a new one.
* **Rename** a key at any time. The list also shows when each key was created and last used.
* **Revoke** a key if it is exposed or no longer needed. Any client using it loses access on its next request. Revoking a key does not affect your other keys.
***
## Next step
{% content-ref url="/pages/1TwnKjTxO0UACle3y7By" %}
[Connect Claude Code](/dapta-mcp/setup/connect-claude-code.md)
{% endcontent-ref %}
{% content-ref url="/pages/Trp2EauxJlwTjM0eFK01" %}
[Connect Codex](/dapta-mcp/setup/connect-codex.md)
{% endcontent-ref %}
{% content-ref url="/pages/zPO586EM9ssLz6B5VzVL" %}
[Connect Cursor](/dapta-mcp/setup/connect-cursor.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/mint-your-api-key.md?ask=&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.
