Google MailPilot
Allows AI agents to read, search, triage, and draft emails with human-in-the-loop safety and Gmail-specific threading and labels.
Provides calendar access, event creation, editing, and deletion with offline-first operations and background sync.
Required for OAuth2 authentication and enabling the Google Calendar API integration.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Google MailPilotshow me urgent unread emails from today"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Google MailPilot
The AI-native command center for Gmail and Google Workspace
Google MailPilot is the renamed successor to Gmail Secretary, built so LLMs can read, triage, respond to, and calendar-manage Gmail with a production-grade MCP control plane.
โ ๏ธ Release Notice: v5.0.0 is the first public release under the Google MailPilot brand; it fixes MCP tool registration, tightens triage/compose coverage, adds new booking-link helpers, and keeps every mutation human-in-the-loop.
Release highlights:
Tools now register as soon as
workspace_secretary.toolsimports, preventing FastMCP registration bugs.Triage/compose tooling gained synchronous tests plus
tests/test_triage_priority_emails.pyandtests/test_web_compose.pyto cover CLI-aware workflows.Engine/web routes, booking links, and
raw:continuation-state handling now align with Google MailPilot expectations.
๐ฆ Stability Matrix
We believe in transparency. Here is the current readiness of our stack:
Component | Status | Stability Notes |
IMAP Sync Engine | ๐ข Stable | RFC-compliant, IDLE support, tested on >24k emails. |
Read Operations | ๐ข Stable | Search, Threading (X-GM-THRID), and Summarization work perfectly. |
Write Operations | ๐ก Beta | Draft creation is stable. Auto-sending is currently disabled via the Safety Interceptor. |
Web Dashboard | ๐ Alpha | Early preview. UI may change rapidly. |
A Google MailPilot IMAP/SMTP control plane for AI agents with calendar integration
Built for LLMs that need to read, search, triage, and respond to email autonomously. Not just an MCP wrapper โ a full-featured IMAP control plane engineered for AI orchestration workflows.
๐ Documentation ยท ๐๏ธ Architecture ยท โก Quick Start
Related MCP server: Email Triage MCP
Why This Exists
Most email integrations for AI are thin API wrappers. They poll. They re-fetch. They timeout. They don't understand email threading, modification sequences, or push notifications.
Google MailPilot is different. It's a production-grade IMAP control plane that:
Syncs intelligently โ CONDSTORE tracks what changed, IDLE pushes new mail instantly
Caches locally โ SQLite or PostgreSQL, your AI reads from local DB in milliseconds
Understands Gmail โ Native X-GM-THRID threading, X-GM-LABELS, X-GM-RAW search
Never sends without approval โ Human-in-the-loop by design, drafts first
๐ก RFC Compliance
We implement these IMAP extensions for efficient, real-time email sync:
RFC | Extension | What It Does | Benefit |
IMAP4rev1 | Core protocol | Full IMAP compliance | |
CONDSTORE | Tracks modification sequences | Skip sync when mailbox unchanged | |
CHANGEDSINCE | Fetch only changed flags | 10x faster incremental sync | |
IDLE | Push notifications | Instant new mail detection | |
ID | Client identification | Better server compatibility |
Gmail-Specific Extensions
Extension | Purpose |
| Native Gmail thread ID โ no heuristic threading needed |
| Stable message identifier across folders |
| Full Gmail label support (stored as JSONB) |
| Gmail's powerful search syntax for targeted sync |
โก Performance
Real benchmarks against a 50,000 email mailbox:
Operation | Traditional IMAP | Google MailPilot |
Check for new mail | 2-5s (fetch all UIDs) | < 50ms (HIGHESTMODSEQ compare) |
Sync flag changes | Re-fetch messages | Flags only (CHANGEDSINCE) |
New mail notification | 5-min poll interval | Instant (IDLE push) |
Search emails | Server roundtrip | < 10ms (local SQLite FTS5) |
Thread reconstruction | Parse References headers | Instant (X-GM-THRID) |
How CONDSTORE Works
Traditional Sync:
1. SELECT INBOX
2. FETCH 1:* (FLAGS) โ Downloads ALL flags every time
3. Compare with cache
4. Fetch changed messages
CONDSTORE Sync:
1. SELECT INBOX
2. Compare HIGHESTMODSEQ โ Single integer comparison
3. If unchanged โ done โ Skip everything
4. If changed โ FETCH 1:* (FLAGS) CHANGEDSINCE <modseq>
โ Only changed messages๐๏ธ Architecture
Dual-process design separating sync from AI interface:
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ AI Layer (Claude, etc.) โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ
โผ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ MCP Server (read-only) โ
โ โข Exposes 25+ tools for email/calendar operations โ
โ โข Reads directly from local database โ
โ โข Mutations proxied to Engine API โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ
โโโโโโโโโโโโโโโโโโโดโโโโโโโโโโโโโโโโโโ
โผ โผ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ SQLite / PostgreSQL โ โ Secretary Engine โ
โ โข Email cache (FTS5) โโโโโโโโโโ โข IMAP sync (CONDSTORE) โ
โ โข Gmail labels (JSONB) โ โ โข IDLE monitor โ
โ โข Embeddings (pgvector) โ โ โข OAuth2 management โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ โข SMTP send/draft โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ
โผ
โโโโโโโโโโโโโโโโโโโโ
โ Gmail IMAP โ
โ Gmail SMTP โ
โ Calendar API โ
โโโโโโโโโโโโโโโโโโโโWhy Two Processes?
Concern | Engine | MCP Server |
Sync | Owns IMAP connection, IDLE loop | Never touches IMAP |
Database | All writes | Read-only |
Uptime | Always running | Scales with AI requests |
Credentials | Holds OAuth tokens | Stateless |
๐ฏ AI-Native Features
Calendar Integration:
โก Instant Calendar Access: Sub-50ms queries via intelligent caching layer
๐ Offline-First Operations: Create/edit/delete events without internet, sync transparently
๐ Background Sync Worker: Autonomous daemon syncs every 60s using Google Calendar API sync tokens
๐ท๏ธ Status Indicators: Visual badges show pending/synced/conflict states for offline operations
โ๏ธ Multi-Calendar Support: Select which calendars to display via web UI settings
Email Intelligence:
Intelligent Signal Extraction
Every email is analyzed for actionable signals:
signals = {
"is_addressed_to_me": True, # In To: field, not just CC
"mentions_my_name": True, # Name appears in body
"has_question": True, # Contains "?" or question phrases
"mentions_deadline": True, # "EOD", "ASAP", "by Friday"
"mentions_meeting": True, # Scheduling keywords detected
"is_from_vip": True, # Sender in configured VIP list
"has_attachments": True, # PDF, DOCX, etc.
"attachment_filenames": ["Q4_Report.pdf"]
}Human-in-the-Loop Safety
The AI never sends email without explicit approval.
User: "Reply to Sarah saying I'll attend the meeting"
AI: I've drafted this reply:
To: sarah@company.com
Subject: Re: Team Meeting Tomorrow
Hi Sarah,
I'll be there. Looking forward to it!
Best regards
Send this email? (yes/no)
User: "yes"
AI: โ Email sent successfullyConfidence-Based Batch Operations
Bulk operations require approval with confidence tiers:
Confidence | Batch Size | Display |
High (>90%) | Up to 100 | Date, From, Subject only |
Medium (50-90%) | Up to 10 | + First 300 chars of body |
Low (<50%) | Individual | Full context required |
๐ Quick Start
Prerequisites
Docker and Docker Compose
Gmail account with App Password (or OAuth2)
Google Cloud project (for Calendar integration)
1. Clone and Configure
git clone https://github.com/johnneerdael/google-mailpilot.git
cd google-mailpilot
cp config.sample.yaml config/config.yaml2. Edit Configuration
# config/config.yaml
imap:
host: imap.gmail.com
port: 993
username: your-email@gmail.com
password: your-app-password # Gmail App Password
user:
email: your-email@gmail.com
first_name: Your
last_name: Name
timezone: America/New_York
working_hours:
start: "09:00"
end: "18:00"
vip_senders:
- ceo@company.com
- important-client@example.com
database:
backend: sqlite # or "postgres" for embeddings
path: /app/config/secretary.db
bearer_auth:
enabled: true
token: "generate-with-uuidgen"3. Start Services
docker-compose up -d4. Connect Your AI
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"secretary": {
"url": "http://localhost:8000/mcp",
"headers": {
"Authorization": "Bearer your-token-here"
}
}
}
}๐ง Available Tools
Email Operations
Tool | Description |
| FTS5-powered local search with Gmail query syntax |
| Full email content with signals and metadata |
| Complete thread via X-GM-THRID |
| AI-ready thread summary |
| Draft response (never auto-sends) |
| Send with explicit approval |
| Add/remove Gmail labels |
| Move between folders |
Calendar Operations
Tool | Description |
| Events in time range |
| Free/busy lookup |
| Create with timezone support |
| Find alternative meeting times |
Triage Operations
Tool | Description |
| Priority emails + today's calendar |
| Identify high-priority items |
| Batch cleanup with approval |
Semantic Search (PostgreSQL + pgvector)
Tool | Description |
| Search by meaning, not keywords |
| Similar emails to reference |
๐ Database Schema
Email Storage
CREATE TABLE emails (
uid INTEGER,
folder TEXT,
message_id TEXT UNIQUE,
gmail_thread_id BIGINT, -- X-GM-THRID
gmail_msgid BIGINT, -- X-GM-MSGID
gmail_labels JSONB, -- Full label set
subject TEXT,
from_addr TEXT,
to_addr TEXT,
date TIMESTAMPTZ,
internal_date TIMESTAMPTZ, -- INTERNALDATE
body_text TEXT,
body_html TEXT,
flags TEXT,
modseq BIGINT, -- CONDSTORE sequence
has_attachments BOOLEAN,
attachment_filenames JSONB,
-- FTS5 index on subject, from_addr, to_addr, body_text
);Folder State (CONDSTORE)
CREATE TABLE folder_state (
folder TEXT PRIMARY KEY,
uidvalidity INTEGER,
uidnext INTEGER,
highestmodseq BIGINT -- For CONDSTORE sync
);๐ Security
Layer | Protection |
Transport | TLS 1.2+ for IMAP/SMTP |
Authentication | OAuth2 or App Passwords (never plain passwords) |
API | Bearer token authentication |
Data | Local database, no cloud sync |
Actions | Human approval for all mutations |
Never Stored
Plain text passwords
OAuth refresh tokens in logs
Email content in error messages
๐ Documentation
Guide | Description |
Deep dive into dual-process design | |
All config options explained | |
HITL safety patterns | |
Complete tool documentation |
๐ ๏ธ Development
# Install with dev dependencies
pip install -e ".[dev]"
# Run tests
pytest
# Run locally
python -m workspace_secretary.engine.api & # Start engine
python -m workspace_secretary.server # Start MCP serverLicense
MIT License โ see LICENSE for details.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/johnneerdael/google-mailpilot'
If you have feedback or need assistance with the MCP directory API, please join our Discord server