Cloudflare-native inbox infra for OpenClaw and local agents

Catch-all inbox for AI agents.

MailClaw receives every email sent to your domain, stores it in D1, and gives agents a clean way to search, filter, triage, and operate inbox workflows in natural language through a REST API, Rust CLI, and local skill.

Read README Deploy to Cloudflare

Email Routing D1 REST API Rust CLI

MailClaw Edge inbox with a claw.

Secure token auth

mailclaw.example.com

Inbox

billing@yourdomain.com Invoice for March infrastructure usage

08:12

support@yourdomain.com Refund requested for order #4013

08:41

alerts@yourdomain.com Latency crossed threshold for 3 minutes

07:58

Query

mailclaw list --q invoice --json

{
  "success": true,
  "data": {
    "emails": [
      {
        "from_address": "billing@service.io",
        "subject": "Invoice for March infrastructure usage",
        "to_address": "billing@yourdomain.com"
      }
    ]
  }
}

Catch everything

Route *@yourdomain.com into one Worker instead of managing inbox sprawl.

Query like data

Search by sender, recipient, date, and keyword. Export full content only when you need it.

Fits OpenClaw

Made for local agents, markdown skills, and CLI-driven workflows without extra glue code.

Features

Built for real email operations, not just passive storage.

Natural language control

Ask your agent to check recent receipts, summarize support mail, find invoices, or review partnership emails.

Fast filtering and search

Filter by sender, recipient, date range, and keyword so an inbox full of noise becomes queryable data.

Automation-ready flows

Let workflows watch for confirmation emails, magic links, OTP codes, invoices, or webhook-style alerts.

Register accounts automatically

Use MailClaw in signup flows so an agent can create accounts, wait for verification mail, and continue the task.

Use aliases as workflow inputs

Split traffic across addresses like billing@, alerts@, or signup@ without new inbox setup.

Keep humans and agents aligned

Read the same inbox through API, CLI, and skill so debugging, review, and automation all see the same source of truth.

Future

When sending lands, MailClaw becomes AgentMail.

Once outbound email is connected, the inbox stops being read-only. You will be able to use natural language to read, draft, reply, send, triage, and organize email through one agent-native layer.

Ask

Reply to the latest invoice and ask for a corrected receipt.

Delegate

Draft follow-ups for unread partnership emails and send them after approval.

Operate

Use natural language to manage your email instead of jumping between inbox views and filters.

How it works

One straight path from email to agent.

01 Email Routing

Catch-all mail lands on the Worker.

02 MailClaw

Parse the message and persist it in D1.

03 Access layer

Read via API, CLI, or local skill.

Access

Small surface area. Multiple entry points.

Predictable HTTP for apps and scripts.

Bearer token auth with simple JSON responses for search, export, read, and delete.

Local binary access with no raw curl.

The Rust CLI stores credentials locally and mirrors the same inbox operations as the API.

Natural fit for local AI workflows.

Install the built-in skill, then let your agent use the local CLI for inbox access instead of hand-written curl commands.

curl -H "Authorization: Bearer $TOKEN" \
  "https://mailclaw.example.com/api/emails?q=invoice&limit=20"

{
  "success": true,
  "data": {
    "emails": [
      {
        "subject": "Invoice for March infrastructure usage",
        "from_address": "billing@service.io"
      }
    ]
  }
}

mailclaw config set \
  --host "https://mailclaw.example.com" \
  --api-token "your-api-token"

mailclaw list --q invoice --json
mailclaw get clx123abc --json

npx skills add missuo/mailclaw

First use:
  Configure MailClaw Host and API Token

Then ask:
  "Check recent invoices in MailClaw"
  "Read the latest partnership email"