For one person

Everything your AI can do with your email, and exactly how much you let it.

Connect the mailbox you already own, and Claude, ChatGPT or any AI that speaks MCP can read it, answer it, file it and read the files on it. You set a level for each AI connection, and a limit on the mailbox that no client can pass. With a routine, it works through your inbox every morning without being asked. Putting a team on shared mail? See what a team gets.

  • Tools 37 email tools
  • Levels 3, per connection
  • Calls a day 5 free, 1,000 on Pro

New: routines

Email routines: your AI works your inbox on a schedule

Every connected mailbox has a Routines tab. Pick one of 5 routines (one of them is built from your own words), shape it in plain words and press Add. Claude or ChatGPT opens with it written out, and you confirm the task there. From then on it runs by itself, at the time you chose. The free plan's 5 calls a day are enough to try one, and Pro's 1,000 are plenty for one every morning.

Email routines: the robot holding a fan of envelopes over a tray of sorted stacks, beside an open mailbox full of post and a round clock on a stand, joined by a glowing blue fibre.
A Monday morning with all 5 added Starting times. Each is yours to change.
  1. Weekdays

    A morning brief of your email, an AI email routine: the robot holding up a clipboard with a short 3-item summary while a twin-bell alarm clock rings beside a stack of envelopes linked to the clipboard by a glowing blue fibre.

    Morning brief

    What came in since the last brief, who needs you first, and what can wait.

    Each run
    2 to 5 calls
    Needs
    Read only
  2. Weekdays

    Replies waiting, an AI email routine that drafts replies: the robot kneeling to lay a written reply in an open filing tray beside the letters it answers, with a white mailbox behind him closed and its flag down.

    Replies waiting

    Drafts a reply to each person still waiting on you, ready for you to check and send.

    Each run
    2 to 12 calls
    Needs
    Draft and file
  3. Weekdays

    Bills and invoices, an AI email routine that reads the totals: the robot holding up a bill with a total line and pointing a glowing stylus at a desk calendar with one day ringed in blue, a stack of papers beside him.

    Bills and invoices

    The bills and invoices that arrived, with the totals and due dates read from the attachments.

    Each run
    2 to 12 calls
    Needs
    Read only
  4. Mondays

    Waiting on, an AI email routine for sent mail with no reply: the robot holding up a sealed envelope and resting a hand on an hourglass of blue sand, beside a rack of 3 sent envelopes each marked with a blue tab.

    Waiting on

    The emails you sent that nobody has answered, oldest first, with how long each has waited.

    Each run
    2 calls
    Needs
    Read only
  5. Weekdays

    Your own AI email routine, built from parts: the robot kneeling to click a fourth module onto a row of white and blue modules, one holding envelopes and one with a funnel that letters drop into.

    Your own routine

    Your own job for your AI: the mail it looks at, what it does with it, and anything else in your own words.

    Each run
    2 to 5 calls
    Needs
    Read only
  • It runs in your own Claude or ChatGPT

    Each routine is a scheduled task in the AI you already use, under your account and at the permission level you set. In Claude that needs a paid plan. On ChatGPT's free plan a task runs once a day, within a time window such as morning.

  • Its card says whether it ran

    Every run checks in with us first. So its card on the Routines tab shows when it ran and how many calls it made, or "Did not run" when a due run hasn't come. What each run found, your AI reports, as it does for any task.

  • It never sends

    With their starting choices, 4 of the 5 only read. Replies waiting saves its drafts in your own Drafts folder for you to check and send, and the options that draft or flag on the others need Draft and file as well. With your AI connected at Draft and file, a send is refused by us, rather than merely left out of the instructions.

What it does

What the AI does with your email

Everything an ordinary mail client does, done by the assistant you already pay for, on the mailbox you already have. That's Claude once it's connected to your email, and ChatGPT, Cursor or any other AI that speaks MCP just the same. Each section says what it does, why that matters to you, and the limit where there is one.

Reading

Reads your email the way you would, and marks nothing read

Reading never marks anything read. Marking a message read is something you ask for, never a side effect of the AI looking at it. So your unread count still means what it meant this morning, and you open Outlook to the inbox you left.

That's one of 5 promises, listed below. Each was checked by opening the mailbox in a mail client afterwards, rather than by trusting what our own code reported, on a live mailbox of 26,930 messages.

Reading email without marking it read: the robot carefully replacing a letter in a mailbox and resetting its flag, leaving everything as he found it.
Put back exactly as it was found
  • "What came in overnight?"

    It lists the folder with the first line or 2 of every message, the quoted history and the signature stripped off. The shortlist is built without opening anything.

  • "Find the invoice from the plumber."

    It searches the mailbox itself, as many as 25 folders in one call, matching the words you gave it.

  • "Catch me up with the surveyor."

    It reads the whole conversation in one call, oldest first.

  • Unread flags when reading unchanged
  • Reply threading In-Reply-To + References
  • Sent Items after a send 1 copy, ID matched
  • Attachment bytes SHA-256 identical
  • Folders it invents none

Attachments

Reads what is inside an attachment: PDFs, spreadsheets, photos

The AI reads email attachments, not only the message around them. Ask what the invoice Hollis attached actually comes to, and the server fetches the PDF from your mailbox and hands the AI its text, page by page.

That's the difference from Claude's own Gmail connector, which reads attachment metadata only, per the Anthropic help centre page under Sources. It can tell you there's a PDF on the message, and not what it says.

An attachment identified by its bytes rather than its name: the robot holding up a see-through envelope with chrome cogs and a spring inside it instead of a letter, pointing at them.
What a file is comes from its bytes, not its name
  • Documents come back as text.

    A PDF arrives page by page, and a Word document keeps its tables. A slide deck comes slide by slide.

  • Spreadsheets come back as rows.

    The formulas are already worked out, and every sheet can be reached by name.

  • Photos and scans come back as pictures.

    A photo is a picture the AI can look at, and a scanned letter is pictures of its pages, so it's read the way a person reads it.

  • A file is named by its bytes, not its label.

    What a file is comes from its first bytes rather than its name, so a program calling itself invoice.pdf is named as a program before anybody opens it.

  • Tried on real mail.

    On , through the live service: a 5-page invoice, a 16-sheet spreadsheet and an 8-page scanned letter, from files real correspondents had sent.

  • Nothing marked, nothing kept.

    Reading a file never marks the message read, and nothing is kept afterwards.

Sending a file: 4 ways in

Files go the other way just as cheaply, and only one route costs the AI anything.

A file reaches a message from 4 places. It's already in your mailbox, at a web address, off your own computer through a one-off upload link that needs no sign-in, or written by the AI itself.

The first 3 never pass through the AI at all. The bytes go from wherever they live into the message while it's being built. So a 6 MB PDF costs the AI about as much as a sentence, and arrives in seconds. Only a file the AI writes itself has to fit in its own output, and only that one is small.

The 4 ways a file can be attached to an email: from the mailbox itself, from a web address, from your own computer, and one the assistant writes, all arriving at a single message.
The 4 routes every AI has into one message, and only the last costs it anything

In ChatGPT there's a fifth way, which removes even that. An image ChatGPT has just generated, or a file in the chat, is handed over as a link and attached like any other, with nothing downloaded first.

Attachments are capped at 20 MB per message in total across every file attached, which is our limit rather than a provider's.

So a file you want sent on goes without you doing the attaching, and without the AI ever having to spell it out. Sending, reading and saving files, and how every other connector compares, are on AI email attachments.

Sending

Sends, replies and forwards in the thread, from any of your addresses

What your AI sends looks, threads and files exactly like what you send. The person at the other end can't tell the difference.

If your mailbox can send as more than one address, so can this. Each alias carries its own display name and signature, set in your account rather than by the AI.

An email reply sent in the thread with In-Reply-To and References: the robot clipping a reply card directly beneath the original message it belongs to.
The reply clipped to the message it answers
  • Replies stay in the thread.

    A reply carries the 2 headers a mail client reads to decide where it belongs, In-Reply-To and References. So it nests under the original in Outlook and Gmail as if you'd written it.

  • The original shows the reply arrow.

    The message being answered is marked answered, so your own mail client shows the arrow.

  • Forwards carry everything.

    A forward brings the original's attachments and inline images, under the forwarded-message block a real mail client produces.

  • You're never copied in on your own thread.

    A reply-all leaves out every address on your mailbox.

  • Exactly one copy in Sent Items.

    It's filed with the same Message-ID the recipient received. Attachments arrive byte for byte: a real send of a JPEG and a ZIP came out SHA-256 identical at the far end.

  • About 5 seconds to send.

    That's to an external domain through Microsoft Graph, and about 10 over SMTP. Both were timed.

Drafts

Writes drafts that Outlook and Gmail can open

Ask for a reply you want to read first, and it's saved in your real Drafts folder. It's threaded and quoted, and carries its files. You open it in Outlook or Gmail, change a sentence, and press Send yourself.

At the Draft and file level, further down this page, this is as far as a connection can go: it prepares, and nothing leaves. The AI does the writing, and the sending stays a thing you do, in the program you already trust for it.

An email reply drafted by an AI and left for you to send: the robot holding a written page over an open Drafts tray, pausing rather than posting it.
Into Drafts first, out of the mailbox second
  • The original stays unanswered.

    It's left unmarked, because it hasn't been answered yet.

  • Forwards can be drafted too.

    That's the message where checking first matters most, because the part being sent isn't yours.

  • A change rewrites the same draft.

    It doesn't save a second one. A wording you went through 5 times leaves one message in Drafts and nothing in your bin.

  • Files and threading survive the rewrite.

    The files already attached, and the headers that keep a reply in its conversation, both carry over.

Without being asked

Add the Replies waiting routine to Claude or ChatGPT, and every weekday morning a reply to each person still waiting on you is in Drafts before you sit down. It's one of 5 email routines your AI can run on a schedule.

Filing

Files, flags, archives and junks, in bulk when you ask

Up to 500 messages move between folders in a single call. That turns "file a year of newsletters" from an afternoon into one request. Messages are marked read, unread or flagged in the same batches.

The tidying happens the way you'd have done it, and nothing is filed anywhere you wouldn't have put it. The filing guide walks through a real clear-out.

Filing and flagging email from an AI client: the robot holding a letter with a blue flag tab at an open filing drawer full of folders.
Move, flag and mark, in the folders you already have
  • New folders show up in Outlook.

    Folders can be created, renamed, or moved under a different parent with their sub-folders. A folder it creates is subscribed, which is the difference between one that appears in Outlook and one that exists but never shows up.

  • Delete means Trash.

    Deleting moves a message to Trash, exactly as your own delete button does, so it's recoverable.

  • Archive goes where your Archive button would.

    That's a different place on each service. Microsoft 365 has a folder called Archive, and most IMAP hosts have none until one is created.

  • Gmail has no archive folder at all.

    Archiving there means the message leaves the inbox and carries on living in All Mail.

  • Reporting spam teaches your filter.

    It's the same move your spam button makes, which is what teaches your mail server's filter to catch the next one.

  • A rescued message keeps its date.

    Rescuing a message the filter got wrong returns it to the inbox with the date it originally arrived.

Checks

Tells you who really sent it, and whether yours arrived

Every message the AI reads says who really sent it. It carries what your own mail server concluded about the sender from SPF, DKIM, DMARC and ARC, as one verdict, and whether the From address is the mailbox's own.

So "is this really from the bank?" and "did my quote get there?" are questions your AI answers from evidence, rather than from the look of the message.

Checking who an email is really from: the robot holding a magnifying glass over the lit sender tag on an envelope, a small glowing panel beside him.
Who it is from is read, not assumed
  • Hidden writing is named, and never obeyed.

    It names writing a person wouldn't have seen: text styled invisible, hidden comments, invisible characters, an instruction aimed at the AI rather than at you. The text is quoted, reported and never acted on.

    The threat model sets out what that catches and what it doesn't.

  • Sent something and heard nothing? It finds the bounce.

    It looks in Inbox and Junk, and says whether the failure is permanent, so the address is wrong and resending changes nothing, or temporary, so their server was busy and yours is already retrying.

  • A missing read receipt proves nothing.

    It finds the read receipts that came back, and says plainly that a missing one is evidence of nothing, because most mail programs never send one.

  • Your own domain, checked.

    It checks the SPF, DKIM, DMARC and MX records of your own domain, and tells you when a DMARC record is published but set to do nothing.

Calendar

Your calendar too: Google, Microsoft 365 and CalDAV

Connecting a mailbox doesn't connect a diary. That's a separate step, with 3 routes to it. Once one is connected, the AI reads the diary, checks who is free, finds a time that works, and books, moves and answers meetings.

Unknown is never shown as free. When somebody's calendar can't be read (a different organisation, or a permission never granted), the answer for that person is unknown. For other people, what comes back is busy and free, never the subjects of their meetings.

A calendar connected beside a mailbox: the robot pointing at one of 3 days blocked out in blue on an open desk calendar, a reminder bell on the page, a mailbox on its post behind him.
The diary as well as the post, once a calendar is connected
  • Microsoft 365.

    Approve calendar access on a Microsoft 365 sign-in, and all 21 calendar tools arrive in full.

  • Google Calendar.

    A Google sign-in for Google Calendar, on any mailbox. The calendar tools arrive in the set this route supports.

  • A CalDAV server.

    The address of a CalDAV calendar server, which Fastmail, iCloud, Nextcloud and most mail hosts run beside the mail. The tools arrive in the set that server supports.

So a meeting is booked into a slot the AI could actually see, and the invitation goes out in your name only at the level you allow. The scheduling guide covers a week of real bookings.

Your address book connects the same way

Once a mailbox has an address book, the AI looks a person up in it when you ask.

A card is held in memory for about 10 minutes and then forgotten. Nothing about a contact is written to a database, a file or a log of ours.

  • On a password mailbox, 2 routes.

    Your Google contacts, by a Google sign-in of their own, or any other book by the address of a CardDAV contacts server.

  • On Microsoft 365, nothing to connect.

    A Microsoft 365 mailbox brings its Outlook contacts with the mail, on the same sign-in, so there is no address to give and nothing to connect.

  • It can change the book too.

    Where the book can be written to (a CardDAV book whose sign-in allows it; Outlook contacts and Google contacts always), the AI can add a card, correct one and import a contacts file at Draft and file, and delete one at Send and delete.

  • Your phone sees the change.

    Each change is written to your own book. Each is refused rather than forced if the card changed elsewhere in the meantime.

The CalDAV and CardDAV page has the addresses and the one password trap. The Gmail page has the Google route, and the Microsoft 365 page the Outlook one.

Works with

Works from Claude, ChatGPT, Cursor and the rest

Mailbox MCP is an ordinary remote MCP server, reached over HTTPS, and nothing in it knows which assistant is on the other end. Connect a mailbox once, and reach it from whichever AI client you actually work in. No extra licence, and no second price.

  • ChatGPT Assistant
  • Grok Assistant
  • Cursor Code editor
  • VS Code Code editor
  • Zed Code editor
  • Windsurf Code editor
  • Cline Coding agent

The one requirement: the client supports remote MCP connectors. A client that only runs local servers reaches it through the mcp-remote bridge. Each client has its own set-up guide, and so does each kind of mailbox: Microsoft 365, Gmail and any IMAP host.

See every client and the one requirement

The control you keep

The control you keep over the AI

You decide how much of everything above to allow: AI email permissions set per client, a ceiling on the mailbox that none of them can exceed, and a record of every call any of them made. This is the half to read before connecting anything.

Permission levels

Read only, draft, or send: a permission level per connection

Every connection an AI client makes by signing in carries one of 3 permission levels. You choose it on the consent screen when you approve the connection:

  • Read only: looks, and changes nothing.
  • Draft and file: prepares and tidies, and nothing leaves.
  • Send and delete: everything, including what cannot be taken back.

Each level contains the one below it. A calendar switch beside the level decides whether the diary comes with it.

A permission level for each AI client connected to one mailbox: the robot at the centre with lit cables running from him to 2 mailboxes and 3 screens, a monitor, a tablet and a laptop.
Every screen on its own cable, and a connection for each
  • Per connection, not per mailbox.

    Claude on your laptop can be Read only while ChatGPT in your browser is Draft and file, on the same mailbox.

  • Changed without reconnecting.

    Change either on the mailbox's Connector tab in the control panel. It's obeyed on that client's next call.

  • Only Send and delete can send.

    So whether to let Claude send emails at all is the same choice, made per connection.

  • Tools above the level aren't even shown.

    A connection below the top level never sees them, so the model is never offered send_email and never spends a turn finding out it can't use it. The tool reference lists every tool under the level that reaches it.

So AI email read-only access, "can I let it read my email but not send anything?", is a setting you make once, per client, rather than a promise the client makes.

An approval prompt is a different kind of control

Claude's own Gmail connector asks before it sends. A level decides what there is to ask about.

Anthropic's own Gmail connector, the one built into Claude, puts its safety in an approval step rather than in a level. Its help centre, read on , says:

Claude can send, reply to, and forward emails, but only does so with your explicit approval by default.

Anthropic help centre, Use Google Workspace connectors

"By default" is the phrase to notice. The same page goes on to say that on Team and Enterprise plans, an owner decides whether members can let those actions run without asking each time. That's a different kind of control from a level.

An approval prompt asks you every time, and lives in the client, where it can be switched off. A level is set on our server, per connection, and a client at Read only is never handed the send tool to ask about.

The two aren't in competition. Connect Mailbox MCP to Claude and you get both: Claude's own prompt before a tool it treats as destructive, and the level underneath it that decides which tools exist for that connection at all.

The mailbox limit

A limit under every connection that no AI client can exceed

Under every connection sits the mailbox's own limit. You set it on the same Connector tab: one of the same 3 levels, and the calendar switch. It defaults to Send and delete with the calendar on, so nothing changes until you change it.

It's enforced by the server, on every call, before the call is metered. So the most any AI can ever do with this mailbox is one setting, in a place only you can sign in to.

The mailbox limit under every AI connection: the robot kneeling to fit a small gauge with a padlock hanging from it onto the cable that runs from a mailbox to a screen, the cable lit bright on the mailbox side.
A gauge on the cable, locked, and nothing downstream can pass it
  • The lower of the two wins.

    What any connection can actually do is the lower of its own level and the limit, and it has the calendar only when both say so. A connection may be set below the limit, never above it.

  • No consent screen or person gets past it.

    A consent screen can't be approved above it. A person you share the mailbox with can't be given more than it.

  • A pasted token takes the limit as its level.

    That's the kind of access token Cline, Goose, LibreChat and n8n take instead of signing in.

  • Lower it, then raise it, and nothing is lost.

    Lower the limit and every connection above it is capped on its next call. Raise it again and each gets back exactly what was chosen, because nothing is rewritten.

A setting the AI side can't reach

The limit is a setting. Only the mailbox's owner can change it, signed in to the control panel.

Ivan Kuznetsov built a structurally read-only email server for his own 25 years of mail. Writing on HackerNoon on , he put the objection to client-side settings in one line:

A setting can be flipped, by a person or by a prompt.

Ivan Kuznetsov, How to Let Claude Search Your Email Without Letting It Send or Delete

He's right. His answer was to remove the write path from the code entirely, which also means his server can never send a reply.

Ours is a different trade, and it's worth being plain about the difference. The limit is a setting. What makes it more than a checkbox is who can flip it, and from where: only the mailbox's owner, signed in to the control panel, with a second factor if the account requires one. Never from the AI side.

A prompt can't reach it, and neither can a client. A consent screen that asks for more is refused by the server, not by the screen. That's what lets one mailbox be read-only to one client and able to send from another, which a server that can't write at all can't offer.

The Connector tab of the Mailbox MCP control panel, showing your connections to this mailbox, 2 clients: A desktop MCP client at Read only, signed in 3 days ago and last renewed 7 hours ago; Claude on my laptop at Draft and file with the calendar, marked capped by the mailbox limit, signed in 6 September 2026; each with Change and Disconnect, and a note headed Two separate ways in beneath them.
Two connections to one mailbox at two levels, and the second is capped by the mailbox limit.
The mailbox limit card on the Connector tab, headed The most any AI client may do with this mailbox: 3 level cards, Send and delete, Draft and file, which is selected, and Read only, each with a one-line description; a ticked switch reading The calendar may be included; and a Save the limit button.
The limit card: this mailbox is limited to Draft and file, with the calendar included.

Refusals

A refused tool says what it is, so the AI stops asking

A tool the connection isn't allowed is refused in one sentence. It comes back as an ordinary tool result, before the call is metered, naming what refused it and where to change it.

When the limit refused it, the sentence names the limit rather than the connection, because the limit is the control you'd have to change. This is what a mailbox limited to Read only hands back to any client that tries to send from it:

This mailbox is limited to "Read only" in the control panel, so no connection can send from it. The mailbox owner can change that under the mailbox's Connector tab.
A tool the connection's level does not reach: the robot hugging a bundle of letters at a filing cabinet whose drawers have no handles.
No handle on the drawer, and a sentence saying why
  • A made-up tool name gets a plain answer.

    A tool no level has ever placed (a typo, or a name the model made up) is answered with there is no tool called that on this connection, with the name quoted back.

  • Every refusal is on the Activity tab.

    A refusal by the level or the limit is recorded as a failed call, with Not allowed on this connection: in front of the reason. The note ends (mailbox limit) where the limit was the wall.

So the AI is told, in words it can pass on to you, what it may not do, instead of trying again or telling you something went wrong.

Account security

A second factor, and a record kept for as long as you choose

One switch requires a second factor of everyone on the account. It's under Settings, Security. Switch it on, and the account your AI's access hangs off needs more than a password to enter.

The audit record of each call is kept 400 days by default. You can shorten it under Settings to any whole number of days from 90 to 400, so it's kept for as long as you decide, not as long as we decide.

The Security card in the Mailbox MCP control panel: a switch, on, beside Everyone on this account must use a second factor to sign in, with its explanation; a field headed Keep the audit record for, empty and showing the default of 400 days, with the hint that it runs from 90 to 400 days; and a Save button.
The Security card: the second-factor switch, and the audit record kept for the days you choose.
  • No authenticator, no access.

    While the switch is on, a person without a confirmed authenticator can do nothing in the control panel but set one up. They can't accept an invitation onto your mailboxes, and every AI connection they made is refused on its next call until they do.

  • You can't lock yourself out.

    The switch can't be turned on until your own authenticator is set up, and yours can't be turned off while it's on.

  • A pasted access token isn't gated by it.

    That token is the mailbox's credential, not a person's sign-in.

  • The record is the fact of the call, never its contents.

    Nothing else is held, so there's nothing else to shorten. 90 days, the shortest, is the least that still covers a charge, the statement after it and the time it takes anyone to ask.

  • Audit record kept, by default 400 days
  • Shortest period you can choose 90 days
  • Second factor of everyone off until you switch it on
  • A pasted access token not gated by the switch

The record

Every call the AI made, on the Activity tab

Every call any AI client makes to your mailbox is a row on the Activity tab. When, which tool, which mailbox, who made it, whether it worked, how long it took, and the address it came from.

So "what did the AI actually do in my mailbox last week?" is a screen you open, an audit log of what the AI did, rather than a question you have to put to the AI.

The Activity tab of the Mailbox MCP control panel, filtered to one mailbox over the last 24 hours: 10 calls on info@lowsonparts.example, chips reading All 10, Read 7, Write 3 and Irreversible 0, and a table of when, tool, mailbox, who, outcome, took and from, with 8 rows by You and 2 by Harriet Moss, one marked Partly with the note 12 of 13 marked unread, 1 was no longer there, and a note beneath headed What is in this log.
A day of calls on one mailbox by 2 people, with one call that partly succeeded and says how far it got.
  • Filter it, and count it.

    Filter by period, mailbox, tool and outcome. The chips count reads, writes and irreversible calls separately.

  • A partial success says so.

    A call that partly succeeded says how far it got, rather than rounding itself up to a success.

  • The fact of the call, never the contents.

    No subject, no address, no line of a message, because none of that is stored anywhere.

  • Refusals and files, recorded plainly.

    A refused call is recorded as failed, with the reason. A download or an upload is recorded as the message and a file count, never a filename.

Until , every row was recorded as a success whatever the tool returned. The changelog says so, rather than leaving you to trust the older rows.

When something breaks

When a credential stops working, you are told once

If a calendar stops accepting its credential, the control panel shows it and you're emailed once, with the fix. Mail is unaffected throughout.

So a diary that has quietly gone dark is something you're told about, once, rather than something you discover when a meeting was never booked.

Being told once when a credential stops working: the robot ringing a small hand bell and pointing at a rack of letter slots, one of them glowing blue where an envelope should be.
One bell, rung once, at the slot that stopped
  • What counts.

    A calendar credential the provider now refuses, a Google permission revoked or lapsed, or a calendar server refusing its app password.

  • Where you see it.

    On the mailbox row, the calendar card and the overview in the control panel, and in one email, with the fix on the mailbox page.

  • Address books are watched the same way.

    A book that stops accepting its sign-in marks its own card, costs the contact tools and nothing else, and emails you once.

The changelog dates when this began, and says what happened before it.

What it costs

Free is 5 calls a day, Pro is 1,000 a day per mailbox

Any mailbox connects free, with no card, and stays free until you decide otherwise. Both figures are published ceilings, and Pro is a limit rather than an unlimited plan.

  • Free, on any mailbox 5 calls a day
  • Pro, per mailbox 1,000 calls a day
  • Pro, per mailbox, a year £34.99 + VAT
  • Calls are counted over a rolling 24 hours
  • Pro is £2.92 a month, per mailbox.

    That's paid annually at £34.99 + VAT. There's no per-client price: one mailbox on Pro serves however many AI clients you connect to it, each at its own level.

  • A free set-up costs nothing.

    Anthropic's help centre says a free Claude plan can add one custom connector, which is one mailbox. So the free tier here and a free AI plan together are a working set-up that costs nothing.

  • Routines are on every plan.

    They use calls from the same daily allowance. A Morning brief makes at most 5 a run, which is all of a free mailbox's day, so free is the way to try one. On Pro it's 5 of 1,000, which leaves the rest of the day for everything else you ask.

The pricing page for one person has both figures with what counts as a call. Team Access is the page for putting other people on a mailbox you own.

Limits

What it deliberately does not do

A feature list that admits nothing is a feature list nobody believes. These are the ones people are disappointed by, listed before you connect rather than after.

  • Nothing of yours is kept

    Stored credentials are encrypted at rest with AES-256, and the server keeps no copy of your messages.

  • Not a backup tool

    It does not back up, export or migrate a mailbox, and there is no tool that copies your mail anywhere. Archiving a message files it in your own Archive folder, which is filing rather than a backup.

  • Attachments are not scanned for malware

    Nothing here scans an attachment for malware. A file is identified by its bytes rather than by its declared type, so an executable arriving as "invoice.pdf" is named as a program before anybody opens it, but a file that is what it claims to be is not checked against any signature database. Your mail provider almost certainly scanned it on arrival.

  • Search is literal

    Search is substring matching over IMAP. There is no stemming and no ranking, so a search for invoices does not find a message that only ever says invoice.

  • Results are capped

    Search results and long threads are capped. The response reports the total, the number returned and whether it capped, but a very broad search will meet the cap.

  • Your own domain only

    The deliverability check reads the connected mailbox's own domain only. It will not look up a customer's domain, or a competitor's.

If one of those is a dealbreaker, it's better that you know now than after connecting a mailbox. The tool reference goes further and lists what each individual tool refuses to do. The security page sets out what is held for a connected mailbox, and what isn't.

Questions

Questions people ask before connecting

What can Claude or ChatGPT do with my email once it is connected?

Read it the way you would, attachments included. Answer it: send, reply and forward in the thread, from any of your addresses, or save a draft you finish in Outlook or Gmail. Tidy it: file, flag, archive and report spam, in bulk. Check it: who really sent a message, and whether yours bounced. With a calendar connected, a separate step, it books meetings too. That is 37 email tools, and you choose how many each AI client gets.

Can I let the AI read my email but not send anything?

Yes. Every connection carries one of 3 permission levels, chosen on the consent screen and changed on the mailbox's Connector tab. Read only lists, searches and reads, and changes nothing. Draft and file also files, flags and writes drafts, but never sends or deletes. Send and delete is everything. It is per connection, so Claude can be Read only while ChatGPT is Draft and file on the same mailbox. A tool above its level is never shown.

Can it read the attachments in my email?

Yes, on any mailbox. A PDF, Word document, spreadsheet or slide deck comes back as text, and a photo or scanned page as a picture the AI can look at. A file is judged by its first bytes, not its name. Reading a file never marks the message read, and nothing is kept. On the way out, attachments are capped at 20 MB per message in total across every file attached, which is our limit rather than a provider's.

Does my mail client see anything different?

No, and that is the promise the whole product is built around. Reading a message does not mark it read. A reply stays in its conversation. A send files exactly one copy in Sent Items, matched by its Message-ID. An attachment arrives byte for byte. Special folders are found by your server's own flag, never guessed by name, and nothing is invented. Each was checked in a mail client afterwards, on a live mailbox of 26,930 messages.

What record is kept of what the AI did?

Every call any AI client makes to your mailbox is recorded: when, which tool, which mailbox, which connection or person, whether it worked, how long it took and where it came from. The Activity tab shows it, filtered by day, mailbox, tool and outcome. It holds the fact of the call, never the contents. It is kept 400 days by default, and you can shorten that under Settings to any number of days from 90 to 400.

What stops a client doing more than I set?

The mailbox's own limit, on its Connector tab: one of the same permission levels, plus the calendar switch. A connection can do the lower of its own level and the limit. The server enforces it: a consent screen cannot be approved above it, a pasted access token takes it as its level, and a tool above it is refused before it costs a call. The most any AI can do is a setting only you can reach.

What does it cost?

Nothing to start. Any mailbox connects free, with no card, at 5 calls a day, enough to try every feature on this page against your own mail. Pro is £2.92 a month, paid annually at £34.99 + VAT, per mailbox, and lifts that mailbox to 1,000 calls a day. Both are published limits. There is no per-client price: one mailbox on Pro serves however many AI clients you connect to it.

Does it work with Outlook, Gmail and an ordinary IMAP mailbox?

Yes to all 3. A Microsoft 365 mailbox connects with one Microsoft sign-in, a Gmail mailbox with an app password, and any other mailbox with the IMAP settings your mail client already uses: Fastmail, iCloud, a domain host, a company mail server. Outlook, Apple Mail, Thunderbird and webmail carry on exactly as before. The one kind that cannot be connected is a Microsoft 365 shared or delegated mailbox, the sort with no sign-in of its own.

Attribution

Sources

The measured claims are ours. The attachment hashes, the threading headers, the sent-copy count and the delivery times were taken while the engine was being built, against a live mailbox of 26,930 messages. The 3 attachments were read on through the live service. How it works gives each figure with the method beside it, and the changelog dates every release named on this page.

Keep going

Read next

For teams

Everything only a team gets on a shared mailbox: single sign-on, a connection and a level per person, approvals, and a record that says who did what.

Tool reference

Every tool by its registered name, what it touches, which are read-only, and the level that reaches each one.

Pricing for one person

Free on any mailbox, Pro per mailbox, what counts as a call, and how cancelling and refunds work.

Is it safe to give an AI your email?

The questions worth asking any tool that wants your mailbox, written so they work on a competitor as well as on us.

Connect a mailbox and try it.

5 calls a day free, on any mailbox, with no card. Set the level on the consent screen and the limit on the Connector tab before the AI has done anything at all.