# Mimeo and Claude Code

Connect Claude Code to Mimeo through its MCP server and the manager repo, so your agent can build flows, write emails and push changes through a diff.

**The short version:** Claude Code works on your Mimeo two ways: through the MCP server your Mimeo runs at /mcp, and in the Mimeo Manager repo, where your flows, emails and segments are files it can pull, change, diff and push.

## What Claude Code can do in Mimeo

- **Build and change flows.** Read the schema, save a draft flow, validate it, dry-run it on a real subscriber, and make it live only when you say so.
- **Write emails and segments.** Draft an email, preview it as a real person, send yourself a test, and define segments as rules.
- **Answer questions from live data.** Look people up, read their email activity and pull reports for any email, sequence, flow or broadcast.
- **Work on files you review.** In the manager repo, `./bin/mimeo pull`, edit, `./bin/mimeo diff`, then `./bin/mimeo push`, which validates and rehearses the change on your Mimeo before it applies.

The [MCP docs](https://mimeohq.com/docs/mcp#what-it-can-do) list every tool.

## Setting it up

The manager repo is already wired for Claude Code: it ships a `.mcp.json` that points at your Mimeo's MCP server, a `CLAUDE.md` with the operating rules, and skills for recurring jobs such as building a flow from a brief or importing a CSV.

1. Download the Mimeo Manager ZIP from the License page of your [Mimeo account](https://account.mimeohq.com/login), extract it and run `git init`.
2. On your Mimeo, open **Settings → Agents & API → Manager repo** and create a token.
3. Run `./bin/mimeo init --host https://mimeo.example.com` with your own address, then `export MIMEO_TOKEN="$(cat .mimeo/token)"`.
4. Open Claude Code in the repo and approve the project's MCP server when it asks.

To use Mimeo from another project, create a token under **Settings → Agents & API** and add the server directly:

```
claude mcp add --transport http mimeo https://your-mimeo.com/mcp \
  --header "Authorization: Bearer mm_your_token"
```

Don't do both in the same repo. Full steps: [your manager repo](https://mimeohq.com/docs/manager-repo) and [MCP server](https://mimeohq.com/docs/mcp).

## Questions

### Does Claude Code drive a remote account, or my own Mimeo?

Your own. The MCP server runs on your Mimeo, at /mcp, so the tools always match the version you run, and your data never leaves your server.

### Can Claude Code send email by mistake?

MCP needs a full-access token, and full access includes sending. Ask it to rehearse a flow and test-send before anything goes live; [let an AI agent run your email without accidental sends](/guides/agent-safe-email) shows the checks.

### Does it work with other agents?

Yes. Any MCP client works, and [Codex](/integrations/codex) connects the same way.

## Sources

1. [MCP](https://mimeohq.com/docs/mcp), checked 2026-11-10
2. [Your manager repo](https://mimeohq.com/docs/manager-repo), checked 2026-11-09
3. [CLI](https://mimeohq.com/docs/cli), checked 2026-11-02
4. [Connect Claude Code to tools via MCP](https://code.claude.com/docs/en/mcp), checked 2026-11-09

---

This is the Markdown copy of https://mimeohq.com/integrations/claude-code.