# Give Claude an email address

Connect Claude, ChatGPT, Cursor or any MCP client. When it gets stuck, it emails whoever knows, gets on with the rest and picks the answer up when it lands — over the one protocol everybody already answers.

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

Asked to build an order sync with Lindmetall's API, the assistant reads their docs, finds that cursor expiry is not documented, and on its own emails their support from its own address, agent@northwind.aiinbx.app, then carries on with the rest of the work while it waits. Asked the next morning how far the sync is, the assistant checks its own inbox, finds Lindmetall's reply that cursors expire after 15 minutes, finishes the export step with that, and reports the sync done. Asked whether there is anything to know before logging off, the assistant checks its own inbox, finds Jana from ops asking whether the sync is live, answers her itself, and reports that nothing needs you.

One day of an agent with an inbox. Pick a step, or let them play.

Connect

## Add it. Sign in. Done.

No key to paste: your client opens AI Inbx in the browser, you sign in, and it’s in. An inbox of its own and the run of your workspace are two servers, so it can have one or both. Any client that speaks remote MCP works.

What it gets

An address of its own. It writes from it and reads the replies — nothing else of yours.

Claude Code

Terminal

```
claude mcp add --transport http aiinbx-inbox https://mcp.aiinbx.com/inbox
```

Then run `/mcp` and pick aiinbx-inbox to sign in.

Why email

## The protocol for agents is the one everyone already uses

An agent that hits a wall usually stops and waits for you. With an address it can ask whoever knows — a vendor, a colleague, another agent — and pick the answer up when it lands.

-   Asynchronous by design

    It sends the question and gets on with the rest. The answer waits in its inbox for as long as the other side takes.

-   Everyone already answers it

    Every company, support desk and person has an address. Nobody has to adopt anything for your agent to reach them.

-   Replies find their question

    It writes from an address of its own, and what comes back is threaded onto what it sent, whenever it comes back.

On its own

## It decides when to write

You give it the work, not the emails. It reaches for its inbox the way a colleague would, and comes back to you with the result.

It writes when…

-   The docs don’t cover itasks the vendor’s support
-   It needs a key or accessasks whoever holds it
-   A call isn’t its to makeasks you, and waits
-   A long job is donesends you the summary
-   Nobody answered in two daysfollows up

It acts when…

-   Support repliespicks the task back up
-   You answer from your phonecarries on with your call
-   Someone writes to itanswers what it can
-   A reply carries a PDFreads it, tables and all
-   An address bouncesfinds another way in

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

An inbox of its own that it only reads and sends from, or whole workspaces, where 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)