MCP server · many mailboxes, one conversation

All your mailboxes,
one single conversation.
At home.

Gmail, Infomaniak, iCloud, your work server — MyChateMail brings your mailboxes together in a single conversation with your assistant. It reads, sorts, summarises and drafts your replies; it sends nothing, and nothing leaves in clear text. You copy, you send yourself. You stay in control from end to end.

To be fair: your mailbox stays with you; only what you ask to read leaves, going to the assistant's provider — and it leaves masked.
See how it works MCP-compatible · verified with Mistral
The problem

We receive too much. We forget what we haven't replied to. And handing your mailbox to an assistant raises a privacy question no one is addressing.


How it works

Three steps, and nothing slips past you.

1

You connect a mailbox

From a local panel — buttons, not a terminal. Adding, pausing or removing a mailbox takes one click.

2

Everything is indexed and masked, locally

Your mail is indexed on your machine (SQLite database). Sensitive identifiers are replaced by markers before anything leaves.

3

You discuss it in your assistant

Your usual MCP-compatible assistant reads, sorts and summarises. It drafts replies that you copy and send yourself.

What your assistant can do

Seven functions. None of them write.

OverviewPer mailbox: the volumes, and how many threads are awaiting a reply.
What's awaiting a replyThreads where the last message received is more recent than your last reply.
SearchSubjects and senders, filterable — no message bodies.
Read a messageHeaders, masked body, defused links, attachments.
Read an attachmentThe extracted text, masked, paginated — without ever opening or running the file.
Read a conversationThe whole thread, with the meaning of each message.
FetchStarts a read-only synchronisation of your mailboxes.
No sending, no deleting, no movingThese functions do not exist in the software. You remain the only one at the controls.

What sets us apart

Six things no one else does.

01 Many mailboxes, one thread

Gmail, Infomaniak, iCloud, work server: your mailboxes, across every provider, brought into a single conversation. Google and Microsoft do have their connectors — but each one reads only its own mail, Gmail or Outlook. Never the one next door.

02 Masked before the model sees anything

IBAN, card, AVS, phone: replaced by markers before anything leaves. Elsewhere, the number leaves in clear text to the assistant's provider. Not here.

03 “Have I already replied?”

The system also indexes your sent messages and reconstructs threads — even when a conversation starts on one address and continues on another. No one does this.

04 The same marker everywhere

An IBAN quoted in an email and in an attached spreadsheet carries the same marker. The server itself tells you whether an account appears elsewhere: enough to spot a fake-supplier fraud without ever seeing the number.

05 The volume is capped by you

“The N most recent messages, going back no further than X days.” The cap leads: if the 10 requested messages fit within 3 days, we stop at 3 days.

06 A local panel, not a terminal

Add a mailbox, pause it, remove it: buttons. Removing it erases the local copy and leaves the messages untouched on the mail server.


Who it's for

Built for those a suite's assistant cannot serve.

An assistant locked inside a suite sees only one mailbox — its own. MyChateMail is built for those who have several, across several providers, and don't want their content to leave in clear text.

The freelancer

A personal mailbox, a work one, sometimes a third. One single conversation — without handing everything to a cloud giant.

The trustee, the accountant

Sensitive client data, several mandates, several mailboxes. Identifiers are masked before leaving, and the same marker follows an account from one email to the next.

The lawyer, the notary, the doctor

Professional secrecy. No write capability, the index stays with you: for these professions, that's an argument — not a shortcoming.

The Swiss SME

Several mailboxes across several providers, and the requirement that nothing leaves in clear text. A small machine at the office (plan B), and it's sorted.


What it cannot do — and that's by design

The code contains no write function at all. No sending, no deleting, no moving.

It isn't a setting that could be changed, nor a permission you're asked to tick. It's absent code — and it's verifiable by an auditor. The assistant cannot act on your mailbox for one simple reason: the means to do so doesn't exist.

// verifiable at audit: 0 write functions

Privacy, in detail

For the reader who wants to verify.

Masking doesn't cover everything — it covers structured identifiers. We say so, because that's what makes it trustworthy.

Key-verified maskingIBAN, card, AVS, NIR, SIRET, VAT, phone, IP — replaced by markers before anything leaves.
Stable markersThe same account always gets the same marker, from one session to the next. Persistent local vault.
Real value out of the assistant's reachThe tool that revealed it has been removed from the catalogue. Only the local panel, at your place, can display it.
AI manipulation detectedInjection attempts are spotted, and the message is not forwarded — refusal by default.
Attachments never openedRead-only extraction, bounded decompression. The file is neither opened nor executed.
Local audit logEvery output is logged: how much, never what.

And people's names? Your choice.

By default, structured identifiers — IBAN, card, AVS, NIR, SIRET, VAT, phone, IP — never leave; people's names, however, do leave, because without them the assistant can't help you. That's the trade-off for most uses, and we own it.

But you hold the cursor. An option — a single button — masks names too: they become markers ([PERSONNE_1]). And the local panel closes the loop: you paste the assistant's draft into it (“…Frau [PERSONNE_1]”), it hands you back the real text (“…Frau Huber”), you copy, you send. Nothing nominative has left your machine.

Name detection stays imperfect — it may miss a rare name or mask a company name — and it adds a step: many will leave it off. But for a trustee, a lawyer, a doctor, what matters isn't that it's convenient: it's that it's possible. And for a truly sensitive case, never_expose_matching prevents a message from leaving at all — masked or not.

The only commands sent to a mail server: login · logout · list_folders · select_folder(readonly) · search · fetch · starttls. Nothing else.

The three plans

You set the cursor between
everything at home and everywhere, all the time.

Keep the index within your walls, or have it available at all times: three plans, three balances. Plan B is where the two meet — we present the choice, instead of papering over the tension.

A

On your machine

The indexlives at your place
Constraintyour machine must be on
For the freelancer, in desktop use.
C

Hosted

The indexwith us, in Switzerland or the EU
Constraintnone
For those who favour permanent availability. Hosted with us, in Switzerland or the EU — never anywhere else.

In every case, a relay makes the machine reachable without opening a port or a fixed IP. The relay stores nothing — no index, no messages, no attachments. It carries, that's all.


Known limits

We state them. It strengthens the rest.

We're not trying to beat, on its own turf, the assistant already in your main mailbox. MyChateMail goes where it cannot — the other mailbox, at the other provider, without anything leaving in clear text.

Microsoft 365: not yet supported Microsoft's IMAP works, but only via OAuth 2 — password authentication is closed. Implementing it is planned development, not a technical obstacle.
One installation per person MyChateMail indexes one user's mailboxes. Not a shared multi-account service.
The machine must be on In plans A and B, the index lives at your place: the assistant reaches it only while the machine is running. (Except plan C.)

Which assistants

MCP-compatible,
the open standard for connectors.

The server speaks MCP (Model Context Protocol) over Streamable HTTP transport, with Bearer authentication. It's tied to no vendor.

Mistral Vibe Work

Verified end to end, in production. The first European AI, for a product built for Europe.

⏳ The other MCP assistants

Architecturally compatible, not yet verified. Built to work with them — we won't announce them as “supported” until a real test.

Contact

Let's talk.

A question, a demo, a particular use case? Write to us — we answer ourselves.

hello@mychatemail.io

Un produit Sophyia · Route du Golf 7, 3963 Crans-Montana (VS), Switzerland