> ## Documentation Index
> Fetch the complete documentation index at: https://help.heydenada.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting your agent

> Point any MCP-capable agent at Denada's server with your personal API token

Any agent that supports MCP over HTTP can connect to Denada. You need two things: the server URL and a personal API token.

## The server

Denada's MCP server lives at:

```
https://cloud.heydenada.com/api/mcp/denada
```

It uses MCP's streamable HTTP transport with plain JSON responses — stateless, with no SSE or session affinity — so it works with every mainstream MCP client. Authentication is a standard bearer token on each request:

```
Authorization: Bearer <your-token>
```

## Get an API token

Your agent authenticates with a personal API token that lets it act as you:

1. Click your account avatar in Denada and choose **Manage API token**.
2. Click **Generate token**, then copy it.

You can regenerate or delete the token from the same dialog at any time — any agent using the old token immediately stops working.

<Note>
  This personal token is different from the team [API tokens](/team/api-tokens) in team settings, which are used by integrations like the Figma plugin. Agents connect with your personal token only.
</Note>

<img className="screenshot" src="https://mintcdn.com/denada/xjX7XM-d7P3k40as/images/generated/personal-api-token.png?fit=max&auto=format&n=xjX7XM-d7P3k40as&q=85&s=fd077854353b8fb527b70b1426d7642f" alt="API token dialog showing a generated personal token with a copy control and Delete, Regenerate, and OK buttons" width="2048" height="1536" data-path="images/generated/personal-api-token.png" />

<Warning>
  Treat the token like a password: it grants everything your account can do. Don't commit it to source control or share it.
</Warning>

<Tip>
  The **Edit with external tools** option in the chat sidebar of the library and project editors does all of this for you — it generates your token and shows connect commands with the token already filled in.
</Tip>

## Claude Code

```bash theme={null}
claude mcp add --transport http denada "https://cloud.heydenada.com/api/mcp/denada" --header "Authorization: Bearer <your-token>"
```

## Codex

Add to `~/.codex/config.toml`:

```toml theme={null}
[mcp_servers.denada]
url = "https://cloud.heydenada.com/api/mcp/denada"
http_headers = { "Authorization" = "Bearer <your-token>" }
```

## Gemini CLI

```bash theme={null}
gemini mcp add --transport http denada "https://cloud.heydenada.com/api/mcp/denada" --header "Authorization: Bearer <your-token>"
```

## Cursor and other MCP clients

Most other clients accept a JSON MCP configuration along these lines (Cursor: `.cursor/mcp.json`):

```json theme={null}
{
  "mcpServers": {
    "denada": {
      "url": "https://cloud.heydenada.com/api/mcp/denada",
      "headers": {
        "Authorization": "Bearer <your-token>"
      }
    }
  }
}
```

## Try it out

Once connected, give your agent a first task to confirm everything works:

> Check out my Denada library and give me an overview of its blocks.

The agent will discover Denada's tools and built-in guides on its own from there. See [What agents can do](/agents/capabilities) for everything it has access to.