# Your email, in Claude

Connect Claude, ChatGPT, Cursor or any MCP client. It reads and answers your mail, and sets up the rest of AI Inbx when you ask.

[Get started](/signup)
[Documentation](https://docs.aiinbx.com/mcp)

Asked whether anything from Harbourly is waiting and to answer the invoice thread, the assistant finds two threads, reads the invoice one, replies to Tom from your address that it is paid on Friday, and offers to answer the other thread. Asked to add rheinbau.de and say what to set at the DNS host, the assistant creates the domain in eu-central-1, reads its records and lists the five to publish — DKIM, return path, SPF, DMARC and inbound MX — offering to verify once they are in. Asked which emails bounced this week and why, the assistant lists three bounce events: a hard bounce to a mailbox that does not exist, already suppressed, and two soft ones — a full mailbox and a spam filter block.

Pick an example, or let them play. Every step is a real tool call.

Connect

## One URL. Sign in. Done.

No key to paste: your client opens AI Inbx in the browser, you pick the workspaces, and it’s in. Any client that speaks remote MCP works.

Cursor~/.cursor/mcp.json

```
{
  "mcpServers": {
    "aiinbx": {
      "url": "https://mcp.aiinbx.com/mcp"
    }
  }
}
```

A browser opens to sign in and pick the workspaces it may use.

Just ask

## Your inbox and your setup, in plain words

Your mail

What did Harbourly say about the Q4 report?

Tell Tom the invoice goes out Friday.

Forward the Lindmetall quote to Jana.

Which emails bounced this week, and why?

Send the launch note to the beta list tomorrow at 9.

Summarise everything Jana sent in September.

Draft a follow-up to anyone who hasn’t replied.

Your setup

Add rheinbau.de and tell me which DNS records to set.

Never send before 9 or after 6, their time.

Keep cold outreach under 200 emails a day.

Take grace@example.com off the newsletter.

Send every reply to our app’s webhook.

Why isn’t mail from rheinbau.de verified yet?

Give Harbourly a space of their own.

Tools

## The whole API, in 28 tools

Daily work has tools of its own. Everything else — spaces, API keys, mailboxes, OAuth apps, webhooks, events, pacing, members — goes through four that can reach any operation. Small enough for the clients that cap how many tools they load.

Your client asks you first. Every tool is prefixed `aiinbx_`.

[Every tool and operation](https://docs.aiinbx.com/mcp/tools), with its arguments and what your client is told before it runs.

Guardrails

## It works for you, never past you

It signs in as you and stops where your role stops. Admin-only settings stay closed to it wherever they are closed to you.

You pick what it touches

Which workspaces, and whether it may only read, read and send, or run everything — the same three levels an API key has.

It asks before it can’t undo

Deletes and cancels are marked destructive, so your client stops and asks you before each one.

Mail is data, not orders

Bodies, subjects and attachment text are marked as coming from outside, so an instruction inside an email is read as content.

Off in one click

Your account lists every connected app with its workspaces and access. Revoking one stops it at once, everywhere.

## Give your product an inbox. The hard parts are already handled.

[Get started](/signup)