15:00The Salon · projects
Maily Case study 2026 ★ Public source code

All my mailboxes. All my assistants. One bridge.

Maily is a free desktop app with public source code, under the PolyForm Shield licence. I built it as a bridge: installed on the computer, it connects to all my mailboxes, several Gmail accounts and IMAP mailboxes, and gives all my AI assistants one shared local access through MCP, instead of plugging every mailbox into every app.

Role Design & development
Year 2026
Licence PolyForm Shield · free
Maily, Classic theme: the unified inbox, the message list and an open message
The studio · MailyThe Classic theme, the default one: the unified inbox on the left, messages in the middle, reading on the right. Fictitious accounts and messages, in demo mode.
The problem

Several mailboxes, several assistants, no bridge between them.

My mail is spread across several Gmail accounts and IMAP mailboxes, and I work with several AI assistants. Hosted connectors are set up account by account, inside each app: according to Anthropic’s help centre, Claude’s Gmail connector reaches the data of “the Google account you’ve connected”.

I wanted the opposite: one door, on my computer, opening onto all my mailboxes, for every assistant to use.

The choices

Simple, efficient, free.

Four decisions, made from the start, that hold everything else together.
01

A bridge, not a service

Maily runs on the computer and talks directly to Gmail and to IMAP servers. There is no Maily server: mail stays with its provider, and Maily keeps a local copy for speed and search.

02

Public source code

The code is public, under the PolyForm Shield licence, and the app is free: anyone can read what it does with their mail, use it, change it and share it. Nobody may turn it into a competing product, for example by reselling it or offering it as a hosted service.

03

MCP, the assistants’ door

One local MCP server for every mailbox: Claude, or any MCP-compatible client, reads, searches, syncs, exports, trashes and sends through it.

04

Privacy

Your own OAuth credentials, tokens encrypted on disk, sanitised HTML and tracking pixels blocked by default. When an assistant reads a message, its content goes to that assistant’s provider: you choose which one.

The app

What Maily actually does.

A window to read and write, an MCP server for assistants: both go through the same engine.
01 / Assistants

A local MCP server

The tools go through MCP over standard input and output (stdio): list accounts and messages, read, search, sync, export to .eml, download an attachment, move to trash (reversible on Gmail) and send from a Gmail account. Works with Claude and any MCP-compatible client.

MCP · stdio
02 / Unified inbox

One inbox

Several Gmail and IMAP accounts side by side: a unified inbox, one view per account, Gmail categories and labels.

Gmail · IMAP
03 / Search

Search everywhere

Full-text search (SQLite FTS5) across every account at once, in the local copy: fast, even offline.

SQLite · FTS5
04 / Reading

Read without being tracked

Messages sanitised and shown in an isolated frame, remote images blocked until you allow them; reply, forward and attachments.

Sanitised HTML
05 / Look

Five languages, four themes

An interface in five languages and four themes: Classic by default, Frutiger Aero, Glassmorphism and Zero Day.

Languages · Themes
The result

Few parts, well chosen.

A Python engine, a local API bound to 127.0.0.1 and protected by a token, a light web window, a packaged macOS app.

One free app, a bridge to all my mailboxes, and all my assistants go through it.

Python 3.12 FastAPI Uvicorn SQLite · FTS5 Vanilla JavaScript pywebview PyInstaller · macOS app MCP · stdio PolyForm Shield licence

I have also built Maily’s engine into Babel, my own personal command centre.

A bridge between your mailboxes and your assistants.

Case study · Thanaël Fontaine · 2026 github.com/ThanaelFontaine/Maily contact@thanaelfontaine.eu