# Curcuma — Claude setup

## Claude Code (recommended)

Two transparent steps — no remote install script required.

1. Mint a free token (or use one you already have):

```bash
curl -fsS -X POST https://curcuma.sud.fyi/api/mcp/install-token
```

2. Connect the MCP with Claude Code's native command (paste your token):

```bash
claude mcp add --transport http --scope user curcuma \
  https://curcuma.sud.fyi/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"
```

3. Persist the routing rule into `~/.claude/CLAUDE.md` so Claude routes email work automatically.
   Append the marker-delimited block (skip if a CURCUMA:ROUTER block is already present):

```bash
file="$HOME/.claude/CLAUDE.md"
grep -q CURCUMA:ROUTER:BEGIN "$file" 2>/dev/null || {
  printf '\n\n' >> "$file"
  curl -fsSL https://curcuma.sud.fyi/.well-known/agent-skills/curcuma/ROUTER.md >> "$file"
}
```

Optional — full skill pack + config via installer (only if the user approves a remote script):

```bash
curl -fsSL https://curcuma.sud.fyi/install.sh | bash
```

## Verify in Claude Code

1. `/mcp` — confirm Curcuma is connected.
2. List tools — confirm `search_emails` and `get_email_summary`.
3. First-win: *Design a welcome email for my product. Use Curcuma: search welcome, study 2–3 with get_email_summary, give me Resend-ready HTML.*

## Hosted Claude (Desktop / claude.ai / Cowork)

Local shell installers do not configure hosted Claude connectors. Prefer Claude Code for bearer-token HTTP MCP today.

If your hosted surface supports custom remote MCP with headers:

- URL: `https://curcuma.sud.fyi/mcp`
- Header: `Authorization: Bearer <token>`

Curcuma does **not** currently ship a separate OAuth Cowork connector URL (Lazyweb-style OAuth is out of scope for this release).

## Agent handoff page

After minting, open or paste:

`https://curcuma.sud.fyi/agent/<token>`

That page is a hand-to-agent recipe with the token embedded.