atomicmail

Files (58)

• changelog.data.ts · .vitepress/
• config.mts · .vitepress/
• releases.json · .vitepress/
• Layout.vue · .vitepress/theme/
• ChangelogTimeline.vue · .vitepress/theme/components/
• CopyPageButtons.vue · .vitepress/theme/components/
• DocFooter.vue · .vitepress/theme/components/
• HeaderLinks.vue · .vitepress/theme/components/
• LinkRows.vue · .vitepress/theme/components/
• PathTabs.vue · .vitepress/theme/components/
• ReleaseNav.vue · .vitepress/theme/components/
• TabGroup.vue · .vitepress/theme/components/
• ThemeMenu.vue · .vitepress/theme/components/
• custom.css · .vitepress/theme/
• index.ts · .vitepress/theme/
• SKILL.md
• authentication.md
• changelog.md
• [version].md · changelog/
• [version].paths.ts · changelog/
• core.md
• custom-domains.md
• dify.md
• examples.md
• getting-started.md
• index.md
• jmap-using.md
• jmap.md
• langchain.md
• make.md
• mcp-remote.md
• mcp.md
• n8n.md
• oauth.md
• overview.md
• CNAME · public/
• apple-touch-icon.png · public/
• logo-outline-dark.svg · public/brand/
• logo-outline-light.svg · public/brand/
• mark-outline.svg · public/brand/
• favicon-32.png · public/
• favicon-96x96.png · public/
• favicon.ico · public/
• UncutSans-Variable.woff2 · public/fonts/
• logo-dark.svg · public/
• logo-light.svg · public/
• og.png · public/
• robots.txt · public/
• site.webmanifest · public/
• web-app-manifest-192x192.png · public/
• web-app-manifest-512x512.png · public/
• pydantic-ai.md
• rest-auth.md
• sync-releases.mjs · scripts/
• skill-install.md
• support.md
• use-cases.md
• zapier.md

SKILL.md (first lines)

# Atomic Mail

Atomic Mail exposes a programmable inbox over JMAP with PoW signup and JWT
rotation. This skill ships a single CLI entrypoint with three commands:
**`register`**, **`jmap_request`**, and **`help`** — matching the MCP server.

## When to use this skill

- Register a new inbox or log in with an existing API key.
- Send JMAP batches (inline JSON or preset files).
- Read built-in documentation (JMAP cheatsheet, presets, troubleshooting).
  In this skill runtime, `atomicmail help --topic readme` intentionally returns
  a short stub.

**Call `atomicmail help` early and often** — before guessing
placeholders, `using` URNs, or cron setup. Start with `help --topic overview`,
then `presets` before custom `jmap_request` calls and `cron` after `register`.
If installed behavior disagrees with docs elsewhere, trust help from the running
package.

## Commands

```bash
npx --package=@atomicmail/agent-skill atomicmail register --username "myagent" --watch scheduled

npx --package=@atomicmail/agent-skill atomicmail jmap_request --ops-file list_inbox.json
```

Run **`atomicmail --help`** or **`atomicmail <command> --help`** for flags.

## Defaults

- `authUrl`: `https://auth.atomicmail.ai`
- `apiUrl`: `https://api.atomicmail.ai`
- credentials directory: `~/.atomicmail`

## Workflow

### 1. Register (new account)

```bash
npx --package=@atomicmail/agent-skill atomicmail register \
  --username "alice" \
  --watch scheduled
```

`--watch` is **required** — it is your operator's decision, not yours; ask them.
Run `register` with no `--watch` to see the accepted values (each is a real
choice about how the operator works, so neither is a safe default to guess). On
the scheduling value, `register` prints the per-host schedule setup command.

Writes `credentials.json`, `session.jwt`, `capability.jwt`. Prints JSON
including `inbox` and `accountId`.

**Required next step:** the `watch` value decides who reads the inbox (see
[Inbox checks](#inbox-checks-after-register)). On `scheduled`, schedule a daily
**agent** turn with `list_inbox.json` on your runtime's own scheduler — never at
the OS level, and never cron `atomicmail jmap_request` alone.

Usernames must be 5–21 characters (local-part of your `@atomicmail.ai`
address).

If credentials already exist for a different username, register refuses to run,
which protects the old account. To add another inbox without replacing the
current one, pass a separate `--credentials-dir` (MCP: `credentials_dir` on
`register` / `jmap_request`) — that is the supported path, and the only one you
should reach for. Replacing the credentials in a directory permanently destroys
access to that inbox; there is no normal flag for it, and the refusal error is
where the operator-authorised escape hatch is spelled out.

### 2. Register (existing API key, in case losing the credentials file)

```bash
npx --package=@atomicmail/agent-skill atomicmail register \
  --api-key "..."
```

### 3. JMAP request

```bash
npx --package=@atomicmail/agent-skill atomicmail jmap_request \
  --ops '[["Mailbox/get", {"accountId": "$ACCOUNT_ID"}, "m0"]]'
```

`$ACCOUNT_ID`, `$INBOX`, `$INBOX_MAILBOX_ID`, `$SENT_MAILBOX_ID`, `$UPLOAD_URL`, and `$DOWNLOAD_URL`
resolve from the session/credentials. Other placeholders such as `$TO` or
`$SUBJECT` require `--vars` with a JSON object of strings (same substitution
applies to `--ops` and `--ops-file`).

Preset file:

```bash
npx --package=@atomicmail/agent-skill atomicmail jmap_request \
  --ops-file list_inbox.json
```

With custom placeholders:

```bash
npx --package=@atomicmail/agent-skill atomicmail jmap_request \
  --ops-file send_mail.json \
  --vars '{"TO":"alice@example.com","SUBJECT":"Hello","BODY":"Hi there"}'
```

Bundled presets (no local file creation required):

- `send_mail.json` (`$TO`, `$SUBJECT`, `$BODY`)
- `send_mail_attachment.json` (`$TO`, `$SUBJECT`, `$BODY`, `$ATTACHMENT_BASE64`,
  `$ATTACHMENT_TYPE`, `$ATTACHMENT_NAME`)
- `send_mail_blob_attachment.json` (`$TO`, `$SUBJECT`, `$BODY`; pair with
  repeatable **`--attachment PATH`** for RFC 8620 upload →
  `$ATTACHMENT_0_BLOB_ID`, …)
- `list_inbox.json` (latest 50; uses `$INBOX_MAILBOX_ID`) — **used for the scheduled inbox check**
- `list_sent.json` (latest 50 the agent sent; uses `$SENT_MAILBOX_ID`) — send presets
  file their copy in Sent with `$draft` cleared, so it never shows in the inbox
- `reply.json` (`$MAIL_ID`, `$BODY`)

## Inbox checks (after register)

From Atomic-Mail/atomic-mail-agentic, MIT.

More from Atomic-Mail/atomic-mail-agentic