One AI, Every Mailbox - Our Own Outlook Connector
Company
Automate AI (our own business)
Industry
AI automation agency
What We Built
A custom Outlook connector (MCP server) for Claude
Connected To
Four mailboxes in two Microsoft 365 tenants, calendars and Trello
Why We Built It
We run more than one business, and each has its own Microsoft 365 organisation and its own mailboxes. The working day was spent hopping between them: check one inbox, then another, copy the important bits into Trello, and write replies that sound like us.
We wanted to ask one AI "what needs my attention this morning?" and have it answer across every mailbox, then act on the answer.
Where the Built-in Connectors Stopped
Claude's own Microsoft 365 connector is good at searching. But it connects one Microsoft account at a time, its write tools have to be switched on by an admin, it can't attach files, and it has no tool to move an email to a folder other than Deleted Items. ChatGPT's Outlook app sends plain-text email after you approve each draft, and each extra account is a separate connection.
None of them could see two separate Microsoft 365 organisations at once, and none could hold our own rules about how an email should be written.
What We Built
A custom connector, using the Model Context Protocol (MCP) that Claude and ChatGPT both support. It signs in to each organisation with its own Microsoft permissions, so every mailbox is reachable from one conversation. Each mailbox keeps its own signature, and the AI always has to say which mailbox it is sending from.
It runs on our own computer, beside Claude Desktop and Claude Code, so there is no server to host and no monthly cloud cost.
Mailboxes across two Microsoft 365 tenants, one connector
Tools across email, calendar and Trello
Hand-written emails behind the writing rules
What It Does
Everything the Inbox Needs, in One Place
Built around how we actually work, not around one mailbox.
Every mailbox, one conversation
Mailboxes in different Microsoft 365 organisations sit behind one connector. Ask for a morning briefing and the AI checks all of them, and keeps going if one is offline.
Full inbox control
Read, search, send, reply, forward, flag, mark read and move between folders, in any connected mailbox, with the right signature for each one.
Writes like us, enforced
Rules drawn from 6,300 hand-written emails are checked before anything is sent. A reply that is too long, uses stock phrases or breaks the house style is sent back to be fixed.
Attachments both ways
Incoming attachments are read straight into the conversation, and local files can be attached when sending, replying or forwarding.
Email to action
Unread mail across every mailbox is turned into proposed Trello cards, labelled by which business it came from, ready to approve.
Runs on our own machine
The connector runs locally beside Claude. Secrets live in the operating system's keychain, never in a config file, and there is no cloud server to pay for.
Compared
Our Connector vs Claude's Built-in Microsoft 365 Connector
Where a custom build earns its keep.
| Our Outlook connector | Built-in connector | |
|---|---|---|
| Mailboxes in one place | Several, across tenants | One account at a time |
| Separate Microsoft 365 organisations | Yes | No |
| Send, reply and forward | Yes | YesAdmin must enable |
| Move to any folder, flag, mark read | Yes | NoDeleted Items only |
| Attachments on outgoing email | Yes | No |
| House writing rules checked before sending | Yes | No |
| Cross-mailbox briefing and triage | Yes | No |
| Connects to other tools (e.g. Trello) | Yes | NoSeparate connectors |
Rules the AI Can't Talk Its Way Around
Telling an AI how to write only goes so far. So the rules sit in the connector itself. Before a send, reply or forward goes out, the text is checked: length limits, banned stock phrases and house style. If it fails, the email is not sent and the AI is told exactly what to fix. Only an explicit request for a longer email lets it through.
The same idea works for any business: approval rules, words you never use, who can be emailed from which mailbox, or which emails always need a person to look first.
Under the Hood
- Microsoft Graph: app-only access per tenant, with a sign-in fallback where an organisation needs it.
- Model Context Protocol: one server, 24 tools, used from Claude Desktop and Claude Code.
- Security: secrets in the operating system keychain, nothing stored in plain-text config.
- Reliability: automatic retries when Microsoft throttles, and a test suite covering mailbox selection, replies, forwards, attachments and the writing rules.
The Outcome
The day starts with one briefing across every mailbox: unread counts, flagged mail and the next 24 hours of meetings. Anything that needs action becomes a Trello card in a couple of clicks, and replies go out from the right mailbox, with the right signature, in our own voice.
Running More Than One Inbox?
We can build the same thing around your mailboxes, your rules and the tools you already use.
Free 30-min call · We'll show you 2–3 things to automate first · No obligation
More Success Stories
See how we've helped other New Zealand businesses transform with AI automation
Retro Bowl
Hospitality
An AI voice agent answering the phone in a busy eight-lane bowling alley, plus front-counter texting.
Read case studyPackaging Products
E-commerce
+20% ROAS in month one; social restarted after a 12-month gap.
Read case studyPackaging Products Sales Reporting
E-commerce
Custom dashboard reveals hidden cash sales patterns and high-value clients.
Read case study