# Set up and use Command Mail. From your first address to a connected agent. You can start free and set everything up yourself. ## Quick start 1. **Account.** Create your account: [Start free](https://commandmail.app/login?signup=1). If you already have an account, [log in](https://commandmail.app/login) as usual. If you’d like help, request [personal setup](https://commandmail.app/en/anfragen?thema=einrichtung). 2. **Connect addresses.** Do it yourself or through your agent. Each address gets its own private inbound address. [Here’s how](https://commandmail.app/en/docs#weiterleiten). 3. **Connect your agent.** Add the MCP URL `https://commandmail.app/mcp` in Claude or ChatGPT, or use the Claude Code command. [Instructions by client](https://commandmail.app/en/docs#agent-verbinden). 4. **Approve permissions.** On the authorization page, you choose what your agent can do. [Scopes](https://commandmail.app/en/docs#scopes) and [Autonomy](https://commandmail.app/en/docs#autonomie) explain the levels. > Signing in with Google shares only your name, email address, profile picture link and account ID. Command Mail gets no access to Gmail, Drive or Calendar. ## Forward your addresses Command Mail is one inbox for multiple addresses and domains you own. Email arrives through forwarding, for example from Gmail or your own domain. Each address gets its own private inbound address. ### Connect an address Use the browser or CLI. Then set up forwarding with your existing provider to that address’s private inbound address. ``` commandmail mailboxes connect mara@beispiel.de ``` ### Your own domain Verify ownership of your domain with a DNS TXT record: first claim it, then verify it. ``` commandmail domains claim studio-beispiel.de # Add the TXT record at your DNS provider commandmail domains verify studio-beispiel.de ``` ### Import existing emails Import MBOX and EML exports or folders of EML files through the CLI. First connect the destination mailbox and log in to the CLI. For example: ``` commandmail import export.mbox --mailbox mara@beispiel.de --state archive ``` Import brings in existing messages. It does not set up continuous sync with your previous provider. ### Let your agent set it up If your agent has the scope `mailboxes`, it can handle these steps. For example, say: “Set up hallo@studio-beispiel.de in Command Mail.” It connects the address, claims the domain if needed, gives you the TXT record, verifies it and tells you where to forward email. > Receiving and sending are set up separately. From Pro, you set up sending for each sender address; you confirm ownership of your own domain via DNS. Changes in Command Mail do not automatically sync back to the original mailbox. ## Connect your agent All agents use the same operations through hosted MCP with OAuth, local MCP, CLI or REST. Every session starts with `capabilities`. This shows the agent the owner, scopes, mailboxes with their autonomy levels and its limits. ### Claude Web and desktop: add a custom connector with the URL `https://commandmail.app/mcp` and confirm access on the authorization page. ### ChatGPT Add `https://commandmail.app/mcp` as a remote MCP connector where your plan supports it. Confirm access on the authorization page. ### Claude Code ``` claude mcp add --transport http \ commandmail https://commandmail.app/mcp ``` ### Codex Local MCP through the CLI: `codex mcp add commandmail -- commandmail mcp`. Or use the hosted URL if your version of Codex supports remote MCP servers. ### Command EVE EVE and your bots connect through the hosted MCP URL and work with the permissions you grant them. ### Grok Through the xAI API: add `https://commandmail.app/mcp` as a remote MCP server. Otherwise, use the CLI or REST. ### Muse Through the MCP URL once Muse supports custom connectors. Until then, use REST. ### Hermes Use the hosted MCP URL if the runtime supports Streamable HTTP MCP. Otherwise, use the CLI or REST. This also applies to other agents. More on permissions, workflow and limits: [For agents](https://commandmail.app/en/agents). ## CLI The CLI is called `commandmail`. It works with scripts and scheduled tasks. Install with one line, then log in. Requires Node.js 18 or later. ``` curl -fsSL https://commandmail.app/install.sh | sh commandmail login ``` | Command | Purpose | | --- | --- | | `commandmail login` | log in | | `commandmail mailboxes connect ` | Connect an address | | `commandmail domains claim ` | Claim your own domain | | `commandmail domains verify ` | Verify a domain with a DNS TXT record | ## Custom views and the agent guide Use the **+** next to the inbox tabs to create a custom view, such as “Customer conversations”. The view uses a shared label and includes archived emails with that label. Creating a view does not move any email. Your agent receives our [guide to organizing and archiving](https://commandmail.app/skills/commandmail-organize/SKILL.md) with the CLI installation. Through MCP, it reads the guide with `get_organization_guide`, or through the CLI with `commandmail skill`. It also explains how to handle your exceptions, false positives, invoices and narrowly defined filters. ``` commandmail skill commandmail labels create --name "Kundenkommunikation" commandmail labels list --json commandmail inbox --label LABEL_ID --json ``` A new view starts with manual assignments. Enable automatic labels in settings. Your agent suggests spam and archive rules based on concrete examples; you enable them under “Automation & rules”. Marking something as spam alone does not activate a rule. In the morning brief, reported payment issues appear under “Review payments”, linked to the original email. A payment confirmation is not treated as an outstanding balance. Check the current balance with the provider; an email or risk score alone does not prove it. ## Scopes Scopes define what a key or connected session can do. Grant only what the agent needs. | Scope | Allowed | | --- | --- | | `mail:read` | Read, search and view without marking as read; overview and morning brief; sort within the autonomy level; view activity and undo its own actions; suggest rules; follow up | | `mail:draft` | Save drafts. Never sends or overwrites your edits | | `mail:send-approved` | Send the exact version you approved | | `mail:send` | Send and reply independently, each email with its own `sendKey`, within the daily limit (50 by default) | | `mailboxes` | Connect addresses, verify domain ownership with a TXT record, import old emails. Sending is set up for each sender address, from Pro | > Only a person in the browser can approve drafts, decide on suggestions, enable rules and change autonomy. Email content never grants permissions. Operator permissions such as `admin` are not available for customer keys. ## Autonomy Set the autonomy level for each mailbox: `read` → `suggest` → `rules` → `auto`. | Level | What the agent can do | | --- | --- | | `read` | Read only. It changes nothing, not even read markers | | `suggest` | Archiving, spam and deletion actions are saved as suggestions (response `{"suggested": true}`) and wait for you | | `rules` | As with `suggest`: agent actions remain suggestions. Only rules you have enabled take effect | | `auto` | Actions run and are logged, with at most 50 conversations per call. Supported sorting actions can be undone; sent emails cannot | ### Activity log Actions taken by agents and rules appear in the activity log and can be undone. Suggestions wait there for your decision. ## Let your agent reply For mailboxes such as customer support, a suitably configured agent can answer questions and send replies independently. It knows your offers, agreements and tone only from the information and sources you make available to it. Regular execution is configured separately in the agent. 1. **Grant permission.** On the authorization page, grant this agent `mail:send`. Agents that only sort email do not need it. 2. **Set a daily limit.** In settings under Automation; the default is 50 emails per day. 3. **Read the log.** Every sent email appears in the activity log. > Each email uses its own `sendKey`. Repeating the same request with the same key refers back to the same send attempt. Detected automated messages (RFC 3834, `Precedence: bulk`) are excluded from automatic replies. ## Morning brief The morning brief summarizes what arrived since yesterday and what is due by tomorrow: - Decisions waiting for you - Deadlines - Pending replies - Follow-ups that are due - What arrived since yesterday Expand it to the week with one button. Agents retrieve it with `morning_brief`. ## Risk assessment Each email receives percentage estimates for spam, fraud and phishing. The assessment reads text only. It never opens links or attachments. > Your account will be suspended in 24 hours > > Account service \ > > - Phishing: 94 % > - Fraud: 71 % > - Spam: 38 % ### Categories and markers Alongside risk assessment, Command Mail sorts email into General, Social, Promotions, Updates and Forums, and adds markers such as Appointment, Invoice, Deadline and Security. ## Frequently asked questions ### Does Command Mail read my Gmail account? No. Signing in with Google shares only your name, email address, profile picture link and account ID. Command Mail sees the emails you forward to your private inbound address. ### Can my agent reply and send independently? Yes, if you grant it `mail:send`. Every email is logged and the daily limit applies (50 by default). Without this permission, it saves drafts and sending follows your approval. [How to set it up](https://commandmail.app/en/docs#selbst-antworten) ### Will reloading send an email twice? Reloading does not create a new send attempt for the same approved draft version. If the outcome is unclear, check the recorded send status before starting a new send. ### Does an agent reply to newsletters? Never automatically: automated emails (RFC 3834, `Precedence: bulk`) receive no automatic replies. ### Is there an app? An installable web app with web push, plus Telegram notifications. Desktop apps for Mac and Windows are planned. ### Which languages does Command Mail support? German, English, Spanish, French and simplified Chinese. ### How much does it cost? You can start free with one address. Pro costs €19 per month as a founder price for the first 100 paying Pro accounts, as long as the subscription runs, and €29 per month for all later accounts; yearly billing gives you two months free. You can try Pro for 7 days for €1. Team costs €39 per person per month; Enterprise is priced on request. All prices include VAT. [See pricing](https://commandmail.app/en#preise) ### Who is behind Command Mail? Command Mail is a product of Fyn Labs LLC. Mathias Heinke answers inquiries and handles personal setup. --- Markdown mirror of https://commandmail.app/en/docs (as of 2026-10-17).