# How to give Amp its own email address

Amp can have its own email address with Botmail. Amp claims an address like
`ada-amp@botmail.pro` itself, you approve it, and then you connect
`https://botmail.pro/mcp`: with `amp mcp add` for the CLI on your machine, or
as a remote definition on ampcode.com so it also works in orbs. Botmail
supports automatic OAuth client registration, so Amp opens a browser to sign
in and there's no key to paste.

## Why Amp should have its own address

Amp threads keep working after you close your laptop. Email lets that work
reach people and services without going through your inbox:

- **Verify the emails your code sends.** Sign up on a preview deployment with
  Amp's address, wait for the welcome email, and check the links and copy.
- **Get past sign-up walls.** When a task needs an account on a service you
  approve, Amp can register and [read the verification
  code](https://botmail.pro/guides/ai-agent-verification-emails).
- **Close the loop with whoever reported a bug.** Amp drafts the reply once the
  fix is merged, and you approve it from the review link.
- **Keep work mail separate.** Your inbox never enters a thread that someone
  else on your workspace might read.

## Step 1: Let Amp claim a mailbox

Paste this into a thread:

```text
Read https://botmail.pro/skill.md and claim a mailbox for yourself. Send the invite to my email, then wait for me to approve it.
```

Amp reads Botmail's instructions, solves a small proof-of-work challenge in
the shell, and claims a name. Botmail emails you an approval link; sign in
with GitHub or Google and accept. Unapproved mailboxes are deleted after 24
hours.

## Step 2: Connect Botmail

Amp has two places to keep MCP servers. Pick one.

### Option A: Local config (the CLI on your machine)

```sh
amp mcp add botmail https://botmail.pro/mcp
```

This saves a URL entry in your local `amp.mcpServers` config (user settings
live in `~/.config/amp/settings.json`). The next time you start the Amp TUI, Amp starts
the OAuth flow in your browser automatically. Tokens are kept in Amp's secret
storage and refreshed when needed.

### Option B: Remote definition (orbs, web and apps)

Remote definitions are stored by ampcode.com and follow you to every Amp
client, including orbs:

```sh
amp mcp remote --personal add Botmail https://botmail.pro/mcp --auth oauth
amp mcp remote --personal login Botmail
```

`login` prints an ampcode.com OAuth URL to open. You can do the same from
[MCP server settings](https://ampcode.com/settings/mcp-servers) on
ampcode.com: click **Add MCP Server**, enter the URL, and sign in.

Choose this option if Amp works in orbs. An orb doesn't read the settings file
on your computer, and browser-based OAuth flows aren't available inside an
orb, so a local entry can't sign in there.

## Step 3: Approve access

Either option opens a Botmail page. Sign in with GitHub or Google, then
choose:

- **Permissions.** Read mail, Send mail, and Manage. Amp only gets tools for
  what you grant. With Read alone there are no send tools.
- **Mailboxes.** All, or only Amp's. With several mailboxes you can keep one
  per project.

Press **Allow**. Check the connection any time with
`amp mcp remote --personal check Botmail`, or `amp mcp doctor` for local
config.

## Things to ask Amp

```text
Sign up on the preview deployment with your Botmail address, wait for the welcome email, and check that every link in it uses the preview host.
```

```text
Sign up for a Sentry account with your Botmail address, then check your inbox for the confirmation email and finish the setup. Ask me before accepting any paid plan.
```

```text
The CSV export fix is merged. Draft a reply from Botmail to the email from marco@fieldnotes.io that reported it. Don't send it. Give me the review link.
```

The review link opens a page with the email and Send and Discard buttons, so
first emails to new people wait for you, even from an orb.

## Things to know

- **Keep the tool list small.** Amp's docs warn that many tools can reduce
  model performance, and suggest bundling servers in a skill's `mcp.json` so
  their tools load only when the skill does. That suits Botmail if Amp only
  uses email now and then.
- **Workspace config needs approval.** A server in a project's
  `.amp/settings.json` waits for `amp mcp approve botmail` before it runs, and
  `amp mcp doctor` shows it as `awaiting approval`. Don't commit an API key
  there.
- **Headless runners.** On a runner started with `amp --no-tui`, sign-in
  appears as a dialog in the attached thread on ampcode.com. If the browser
  ends on a localhost page that won't load, copy its full URL into the dialog.
- **Resetting sign-in.** For local config, run
  `amp mcp oauth logout botmail` and restart Amp. For a remote definition, run
  `amp mcp remote --personal logout Botmail`, then `login` again.
- **New tools not showing.** Run
  `amp mcp remote --personal tools Botmail --refresh`.

Connecting other agents to the same mailbox? See [Email MCP
server](https://botmail.pro/guides/email-mcp-server), or read [how Botmail works](https://botmail.pro/ai-agent-email).

## Questions

### How do I add a remote MCP server to Amp?

Run amp mcp add <name> <url> for local config, or amp mcp remote --personal add <name> <url> --auth oauth to store it on ampcode.com so it works in every Amp client, including orbs.

### Why doesn't my MCP server sign in inside an Amp orb?

Browser-based OAuth isn't available in orbs, and orbs don't read your local settings file. Add the server as a remote definition on ampcode.com, which handles OAuth for orbs.

### Does Amp support OAuth for MCP servers?

Yes. For servers with automatic client registration, like Botmail, Amp starts the OAuth flow in your browser the next time you start the TUI.

---

Source: https://botmail.pro/guides/amp-email
Agent instructions: https://botmail.pro/skill.md
All guides: https://botmail.pro/llms.txt