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

# Set up with Claude Code or Codex

> Hand the setup to your coding agent: the connector, the prompt, and the two clicks that stay yours

If you already work with Claude Code or Codex, it can set up your workspace for you. The setup page gives you a connector to add to the agent and a prompt to start it with. The agent then does the same steps you'd do by hand, and the page follows along so you can watch.

## The two clicks that stay yours

An agent can't sign in as you, and it shouldn't. Two steps happen in your browser:

* **Signing in with Google** on [the setup page](https://autonudge.dev/setup). That's how the page knows you're approved, and it's where the connector comes from.
* **Approving Nudge in Convex.** When the agent gets to [Connect Convex](https://docs.autonudge.dev/own-backend/connect-convex.md), it gives you a link. Open it, pick your team, approve, and tell the agent you're done.

Everything else, the agent can do.

## Add the connector

Sign in on the setup page and pick **With Claude Code or Codex**. The page shows three snippets, each with your own key already filled in. Use the one that fits.

**Claude Code, one command.** Paste it into a terminal:

```bash theme={null}
claude mcp add --transport http nudge-setup https://lovable-partridge-890.convex.site/mcp --header "Authorization: Bearer <your key>"
```

**Claude Code, in a project's `.mcp.json`:**

```json theme={null}
{
  "mcpServers": {
    "nudge-setup": {
      "type": "http",
      "url": "https://lovable-partridge-890.convex.site/mcp",
      "headers": { "Authorization": "Bearer <your key>" }
    }
  }
}
```

**Codex, in `~/.codex/config.toml`:**

```toml theme={null}
[mcp_servers.nudge-setup]
url = "https://lovable-partridge-890.convex.site/mcp"
http_headers = { Authorization = "Bearer <your key>" }
```

Copy them from the setup page rather than from here: the page puts your key in for you.

If you'd rather keep the key out of Codex's config file, use `bearer_token_env_var = "NUDGE_SETUP_TOKEN"` in place of the `http_headers` line, and run `export NUDGE_SETUP_TOKEN=<your key>` in the terminal before you start Codex.

> [!WARNING]
>
> The key in the snippet is your sign-in. Anyone holding it can act on your setup, so keep it out of shared repos and chats. It works for seven days from when you signed in. After that, sign in on the setup page again and copy a fresh snippet.

## Start it

Give the agent this prompt:

```text theme={null}
Set up my Nudge workspace: check status, name it, tell me the link to connect Convex, then install and configure Retell
```

It checks where your setup stands, names your workspace (say the name you want in the prompt, or it uses the one suggested from your company), gives you the Convex link, starts the install and reports each step until your workspace is live. It can't skip a step: the name comes before Convex, and Convex before the install, the same order as on the page.

## What the agent can do

The connector gives the agent these tools. It picks them itself; you don't need to name them, but it helps to know what's there.

**Setting up**

| Tool | What it does |
| - | - |
| `status` | Where your setup stands, and the next step in plain words |
| `name_workspace` | Names your workspace, which becomes its address |
| `connect_convex` | Gives you the link to approve Nudge in Convex |
| `reconnect_convex` | Gives you a link to approve again, when Nudge can't reach your backend |
| `install` | Starts the install |
| `install_status` | Follows the install, step by step |
| `docs` | Reads the help page for a step |

**Inside your workspace, once it's live**

| Tool | What it does |
| - | - |
| `set_retell_key` | Saves your Retell API key |
| `list_retell_agents` | Lists your Retell voice agents |
| `list_numbers` | Lists the phone numbers on your Retell account |
| `bind_number` | Sets which numbers an agent calls from |
| `set_email_sender` | Saves your Resend key and the address email goes out from |
| `list_templates`, `upsert_template` | Lists your message templates, and writes new ones or changes their wording |
| `list_triggers`, `upsert_trigger` | Lists your automations, and writes new ones, always switched off |
| `enable_trigger` | Switches an automation on or off |
| `create_contact` | Adds a contact |
| `invite_user` | Invites someone from your team |

None of the tools deletes anything. An automation the agent writes arrives switched off: switching it on is a separate step, and the agent should tell you what it does and who it reaches before it asks to.

> [!NOTE]
>
> Templates and automations belong to a person, so they work after you've signed in to your workspace once. When the install finishes, open your workspace and sign in with Google before you ask the agent for them.

You can stop at any point and finish in the app. The **Getting started** card in your workspace shows what's left.

Next: [Connect email (Resend)](https://docs.autonudge.dev/own-backend/email-resend.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.