productivity-mcp
productivity-mcp
Lokaler Model Context Protocol-Server, der einem LLM-Client (Claude Desktop, Kiro, jede MCP-fähige App) Lese-/Schreibzugriff auf Ihre E-Mails und Kalender gewährt.
Unterstützt:
Anbieter | Kalender | Authentifizierung | |
Gmail | ✅ (API) | ✅ (Google Kalender) | OAuth2 (Desktop-App) |
Apple / iCloud | ✅ (IMAP/SMTP) | ✅ (CalDAV) | App-spezifisches Passwort |
Allgemeines IMAP (Fastmail, selbstgehostet, Arbeits-E-Mail) | ✅ | — | Passwort / App-Passwort |
Läuft vollständig auf Ihrem Rechner über stdio. Es verlassen keine Daten Ihren Computer, außer an Ihre konfigurierten Mail-/Kalender-Server.
Installation
Erfordert macOS mit installiertem Homebrew. Alles andere (Python 3.13, uv, git) wird bei Bedarf installiert.
git clone https://github.com/seandkendall/productivity-mcp.git
cd productivity-mcp
./setup.sh./setup.sh installiert fehlende Voraussetzungen via Homebrew, erstellt ein virtualenv, installiert das Paket und startet den interaktiven Konfigurationsassistenten.
Related MCP server: claude-2-mail
Konfiguration
Führen Sie den interaktiven Assistenten aus – er erstellt ein venv, installiert das Paket, fragt dann nach Ihren Anmeldedaten und schreibt die Konfiguration für Sie:
./setup.shDer Assistent unterstützt:
iCloud / Apple Mail — E-Mail + app-spezifisches Passwort eingeben, fertig. Richtet sowohl Mail als auch Kalender ein.
Gmail / Google Kalender — Verweisen Sie auf Ihre OAuth-Client-JSON (siehe unten, wie man eine erhält).
Allgemeines IMAP — Wählen Sie eine Voreinstellung (Fastmail, Yahoo, Outlook) oder geben Sie einen benutzerdefinierten Host/Port ein.
Die Konfiguration wird mit 0600-Berechtigungen unter ~/.config/productivity-mcp/config.toml gespeichert. Führen Sie den Assistenten jederzeit erneut aus, um Konten hinzuzufügen oder zu ersetzen.
Gmail: Einmalige Google Cloud-Einrichtung
Google hat IMAP/SMTP-App-Passwörter im März 2025 deaktiviert, daher erfordert Gmail OAuth2. Vor dem Ausführen des Assistenten:
Öffnen Sie die Google Cloud Console → erstellen oder wählen Sie ein Projekt.
APIs & Dienste → Bibliothek → aktivieren Sie Gmail API und Google Calendar API.
APIs & Dienste → OAuth-Zustimmungsbildschirm → als Extern einrichten (fügen Sie sich selbst als Testnutzer hinzu).
Anmeldedaten → Anmeldedaten erstellen → OAuth-Client-ID → Desktop-App → laden Sie die JSON herunter.
Führen Sie dann productivity-mcp setup aus, wählen Sie Gmail und verweisen Sie auf die heruntergeladene JSON. Der erste Tool-Aufruf öffnet einen Browser zur Autorisierung; das Refresh-Token wird lokal zwischengespeichert.
iCloud: Einmalige Apple ID-Einrichtung
Melden Sie sich unter appleid.apple.com an → Anmelden und Sicherheit → App-spezifische Passwörter → generieren Sie eines. Fügen Sie es bei Aufforderung in den Assistenten ein.
Manuelle Konfiguration (optional)
Wenn Sie TOML lieber direkt bearbeiten möchten, kopieren Sie example.config.toml nach ~/.config/productivity-mcp/config.toml.
Ausführung
productivity-mcpDies läuft über stdio – Sie binden es in einen Client ein, anstatt es als langlebigen Daemon auszuführen.
Claude Desktop
Bearbeiten Sie ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"productivity": {
"command": "/absolute/path/to/.venv/bin/productivity-mcp"
}
}
}Starten Sie Claude Desktop neu. Die Tools erscheinen unter dem 🔌-Menü.
Kiro
Fügen Sie in den Kiro-Einstellungen einen MCP-Server mit dem Befehl productivity-mcp (oder dem absoluten Pfad zum venv-Binary) hinzu. Er wird über stdio ausgeführt.
Verfügbare Tools (39)
Wenn account bei einem Tool weggelassen wird, wird das erste konfigurierte Konto dieses Typs verwendet. Siehe list_email_accounts / list_calendar_accounts, um Namen und Aliase zu entdecken.
E-Mail — Lesen & Entdecken
list_email_accounts— konfigurierte Konten mit ihrenaddresses(primär + Aliase)list_folders(account?)— IMAP-Ordner / Gmail-Labelslist_emails(account?, folder="INBOX", limit=25, query?, unread_only=false, recipients?, since_days?, senders?)read_email(message_id, account?, folder="INBOX", format="text"|"html"|"both")— HTML-Inhalte werden standardmäßig als Klartext gerendertsearch_threads(account?, folder="INBOX", query?, senders?, recipients?, since_days?, limit=25)— Deduplizierung nach Konversationsearch_emails_by_sender(senders, account?, folder="INBOX", since_days?, limit=25)count_emails(account?, folder="INBOX", query?, unread_only=false, senders?, recipients?, since_days?)count_unread(account?, folder="INBOX", since_days?)list_recent_senders(account?, folder="INBOX", since_days=30, top=20)summarize_inbox(account?, folder="INBOX", since_days=7, top=10)— Summen, Top-Absender, Top-Domains, Top-Empfänger-Aliase, Histogramm pro Tagresolve_contact(query, account?, limit=10)— Namens-/E-Mail-Suche (Gmail People API oder Scan aktueller Nachrichten)
E-Mail — Schreiben (ratenbegrenzt)
send_email(to, subject, body, account?, cc?, bcc?, html=false)reply_email(message_id, body, reply_all=false, account?, folder="INBOX", html=false)forward_email(message_id, to, body="", account?, folder="INBOX", html=false)set_email_read(message_id, read=true, account?, folder="INBOX")delete_email(message_id, account?, folder="INBOX")move_email(message_id, target_folder, account?, folder="INBOX")bulk_set_read(message_ids, read=true, account?, folder="INBOX")bulk_delete_emails(message_ids, account?, folder="INBOX")bulk_move_emails(message_ids, target_folder, account?, folder="INBOX")
E-Mail — Entwürfe & Anhänge
save_draft(to, subject, body, account?, cc?, bcc?, html=false)list_drafts(account?, limit=25)send_draft(draft_id, account?)list_attachments(message_id, account?, folder="INBOX")download_attachment(message_id, attachment_id, save_to?, account?, folder="INBOX")— auf Festplatte speichern oder base64 zurückgeben
Kalender
list_calendar_accountslist_calendars(account?)list_events(account?, calendar?, start?, end?, limit=100)— standardmäßig die nächsten 7 Tageget_event(event_id, account?, calendar?)search_events(query, account?, calendar?, start?, end?, limit=50)create_event(summary, start, end, account?, calendar?, description?, location?, attendees?)update_event(event_id, account?, calendar?, summary?, start?, end?, description?, location?, attendees?)delete_event(event_id, account?, calendar?)respond_event(event_id, response, account?, calendar?)— accept | decline | tentativefree_busy(start, end, account?, attendees?)— native Googlefreebusy.query; EWS/CalDAV greifen auf Ereignisaufzählung zurücksuggest_meeting_times(duration_minutes, window_start, window_end, account?, attendees?, working_hours_start=9, working_hours_end=17, limit=5)
Aufgaben
list_tasks(account?, limit=50)— Google Tasks (Google Kalender-Konten) oder EWS Tasks (WorkMail)create_task(title, account?, due?, notes?)
Diagnose
ping(account?)— prüft jedes konfigurierte Konto; gibt{ok, latency_ms, error?}pro Konto zurück
Beobachtbarkeit
Jeder Tool-Aufruf sendet strukturiertes JSON an stderr:
{"ts":"...","level":"INFO","msg":"tool_call.start","tool":"list_emails","call_id":"b69185a6","arg_keys":["limit"]}
{"ts":"...","level":"INFO","msg":"tool_call.end","tool":"list_emails","call_id":"b69185a6","duration_ms":420}Nur Argument-Schlüssel werden protokolliert – Werte werden niemals preisgegeben. Leiten Sie stderr beim Debuggen in eine Datei um.
Ratenbegrenzungen
Destruktive Tools haben weiche Ratenbegrenzungen, um versehentliche LLM-Schleifen einzudämmen. Standardwerte (pro Serverprozess, gleitendes Fenster):
Tool | Limit |
| 20 / Minute |
| 20–50 / Minute |
| 30 / Minute |
| 10 / Minute |
Bei Überschreitung gibt das Tool einen RuntimeError mit der Wiederholungsverzögerung zurück. Starten Sie den Server neu, um ihn zurückzusetzen.
Entwicklung
# Lint
ruff check src tests
ruff format src tests
# Tests
pytestSicherheit
Geheimnisse liegen in
~/.config/productivity-mcp/config.toml– werden niemals committet und nirgendwohin übertragen, außer an Ihre konfigurierten Mail-/Kalender-Server.Gmail OAuth-Token werden unter dem von Ihnen angegebenen
token_file-Pfad zwischengespeichert; behandeln Sie diese wie Passwörter.Verwenden Sie für iCloud/IMAP immer app-spezifische Passwörter, niemals Ihr Hauptkontopasswort.
Lizenz
MIT
Available Tools
39 toolsbulk_delete_emailsA
Delete many emails in one call. IMAP expunges; Gmail moves to Trash. Rate-limited.
Inputs: message_ids (required), account, folder. Returns: object
bulk_move_emailsC
Move many emails to another folder/label in one call. Rate-limited.
Inputs: message_ids (required), target_folder (required), account, folder. Returns: object
bulk_set_readA
Mark many emails read/unread in one call. Returns counts of successes and failures. Rate-limited.
Inputs: message_ids (required), read, account, folder. Returns: object
count_emailsA
Count messages matching filters without fetching full envelopes. General-purpose counter — e.g. 'how many emails from Amazon this month?'
Inputs: account, folder, query, unread_only, +3 more. Returns: object
count_unreadB
Count unread messages in a folder (optionally within the last N days).
Inputs: account, folder, since_days. Returns: object
create_eventC
Create a calendar event. Times are ISO 8601.
Inputs: summary (required), start (required), end (required), account, +4 more. Returns: object
create_taskC
Create a new task. due is ISO 8601 and optional.
Inputs: title (required), account, due, notes. Returns: object
delete_emailA
Delete an email. IMAP expunges; Gmail moves to Trash (recoverable).
Inputs: message_id (required), account, folder. Returns: object
delete_eventC
Delete a calendar event by id.
Inputs: event_id (required), account, calendar. Returns: object
download_attachmentA
Download an attachment. If save_to (directory) is provided, writes the
file there and returns its path. Otherwise returns base64-encoded bytes.
Inputs: message_id (required), attachment_id (required), save_to, account, +1 more. Returns: object
forward_emailC
Forward an email to new recipients, optionally prepending a note.
Inputs: message_id (required), to (required), body, account, +2 more. Returns: object
free_busyA
Return busy time windows between start and end (ISO 8601).
If attendees is provided, queries busy times for those addresses; otherwise
returns your own busy times. Native Google freebusy.query is used for
Google Calendar; EWS / CalDAV fall back to enumerating events.
Inputs: start (required), end (required), account, attendees. Returns: result
get_eventB
Fetch a single calendar event with full detail.
Inputs: event_id (required), account, calendar. Returns: object
list_attachmentsC
List attachments on a message. Each entry has {attachment_id, filename, mime_type, size}.
Inputs: message_id (required), account, folder. Returns: result
list_calendar_accountsA
List configured calendar accounts.
Inputs: no named parameters. Returns: result
list_calendarsC
List calendars on an account.
Inputs: account. Returns: result
list_draftsC
List pending email drafts.
Inputs: account, limit. Returns: result
list_email_accountsA
List configured email accounts.
Each entry includes:
name: the account LABEL used as the
accountargument in other toolskind: provider class (ImapEmailProvider / GmailProvider)
addresses: every email address this mailbox receives mail at — the primary login address PLUS any configured aliases. Use these when answering 'who emailed me at X?' questions; the
nameis NOT the user's email address.
Inputs: no named parameters. Returns: result
list_emailsA
List messages in a folder.
Args:
account: Account label (use list_email_accounts to see options). If
omitted, the first configured account is used.
folder: Folder (IMAP) or label (Gmail). Default INBOX.
limit: Max number of messages to return. Default 25.
query: Free-text search. For Gmail, pass native Gmail operators
(e.g. from:@example.com). For IMAP this becomes a TEXT search.
unread_only: If true, only return unread messages.
recipients: Filter to messages delivered to (or Cc'd / Bcc'd to) any
of these addresses OR domains. Each entry may be a full address
(sean@nasource.com) or a bare domain (nasource.com). Use this
to answer questions like "who emails me at my alias domains?" —
pass e.g. ["nasource.com", "seankendall.com"]. OR-combined.
since_days: Only return messages newer than this many days. STRONGLY
recommended when using recipients on a large mailbox — a full-
mailbox recipient search can take minutes on accounts with tens
of thousands of messages. For "last 30 days" questions pass 30.
Inputs: account, folder, limit, query, +3 more. Returns: result
list_eventsA
List events in a time range (defaults: now → +7 days). ISO 8601 strings.
Inputs: account, calendar, start, end, +1 more. Returns: result
list_foldersC
List folders/labels for an email account.
Inputs: account. Returns: result
list_recent_sendersA
Top senders over the last N days, ordered by message count. Useful for "who has been emailing me lately?" style questions.
Inputs: account, folder, since_days, top. Returns: result
list_tasksB
List tasks from the account's task list. Supported on Google Calendar (Google Tasks) and EWS / WorkMail (Tasks folder).
Inputs: account, limit. Returns: result
move_emailC
Move an email to another folder/label.
Inputs: message_id (required), target_folder (required), account, folder. Returns: object
pingA
Probe every configured account (or just the named one). Returns per- account {name, kind, ok, latency_ms, error?} so the LLM can self-check.
Inputs: account. Returns: result
read_emailA
Fetch a single message with its body.
Args:
message_id: Provider message id from list_emails.
account: Account label (see list_email_accounts).
folder: Folder / label. Default INBOX.
format: 'text' (default) renders HTML bodies to plaintext — the
LLM-friendly default. 'html' keeps raw HTML. 'both' returns a
body_html field alongside plaintext body.
Inputs: message_id (required), account, folder, format. Returns: object
reply_emailC
Reply to an email. Set reply_all=True to include the original Cc list.
Inputs: message_id (required), body (required), reply_all, account, +2 more. Returns: object
resolve_contactA
Look up a contact by name or partial email. Returns up to limit
{name, email} matches. Gmail queries the People API; other providers fall
back to scanning recent messages. Use before send_email / create_event
when the user refers to someone by name ("email Alice").
Inputs: query (required), account, limit. Returns: result
respond_eventB
Respond to a meeting invitation. response: accept | decline | tentative.
Inputs: event_id (required), response (required), account, calendar. Returns: object
save_draftA
Save an email as a draft instead of sending. Useful when the LLM should let the human review before committing to send. Returns {draft_id}.
Inputs: to (required), subject (required), body (required), account, +3 more. Returns: object
search_emails_by_senderC
List emails from specific senders or sender domains.
Each senders entry may be a full address (alice@example.com) or a bare
domain (example.com). OR-combined.
Inputs: senders (required), account, folder, since_days, +1 more. Returns: result
search_eventsA
Substring search across calendar events (summary, location, description). Default window: now → +60 days.
Inputs: query (required), account, calendar, start, +2 more. Returns: result
search_threadsA
List conversations (not individual messages) matching the filters.
Returns one entry per thread, with the latest message's metadata plus a
message_count field. Gmail uses native threadId; IMAP uses the Message-Id
/ References chain to group. Use this when the user asks "who has been
discussing X?" and you want to avoid seeing 15 near-duplicates of one reply
chain.
Inputs: account, folder, query, senders, +3 more. Returns: result
send_draftC
Send an existing draft by id.
Inputs: draft_id (required), account. Returns: object
send_emailC
Send an email. Returns the provider message id.
Inputs: to (required), subject (required), body (required), account, +3 more. Returns: object
set_email_readC
Mark an email as read (read=True) or unread (read=False).
Inputs: message_id (required), read, account, folder. Returns: object
suggest_meeting_timesA
Find time slots where everyone listed in attendees is free.
Combines each attendee's busy windows (via free_busy) with simple working-
hours filtering. If attendees omitted, uses your own busy times.
Inputs: duration_minutes (required), window_start (required), window_end (required), account, +4 more. Returns: result
summarize_inboxA
One-call inbox overview. Returns counts, top senders, top recipient
addresses (useful when multiple aliases hit the same mailbox), and a
per-day histogram for the last since_days days.
Inputs: account, folder, since_days, top. Returns: object
update_eventB
Update an existing event. Pass only the fields you want to change. Times (start/end) are ISO 8601.
Inputs: event_id (required), account, calendar, summary, +5 more. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 39 tools
Each tool has a clearly distinct purpose. Single vs bulk operations are explicitly separated, email, calendar, task, and contact tools are grouped by domain, and search utilities have specific scopes (by sender, threads, events). No two tools appear to overlap in functionality.
All tools follow a consistent verb_noun pattern with lowercase underscores (e.g., 'create_event', 'list_emails', 'delete_event'). No mixing of camelCase or other conventions, making it easy for an agent to predict tool names.
With 39 tools covering email, calendar, tasks, and contacts, the count is on the higher side but still reasonable for a comprehensive productivity suite. Each tool serves a distinct purpose, and the breadth is justified by the domain's complexity.
The tool surface is largely complete, covering CRUD for email (including bulk operations and drafts) and calendar (including free/busy and suggestion), plus tasks and contacts. Minor gaps like missing update/delete for tasks are not critical for most use cases.
Maintenance
Related MCP Connectors
Your IMAP mailbox as an MCP server: read, search and (if you allow it) organize mail. Open source.
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Hosted Google Calendar MCP server for AI agents. No self-hosting or Google Cloud setup.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvider-agnostic email MCP server that connects any IMAP mailbox to AI assistants, enabling email management through natural language.8AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceLocal MCP server for reading/sending email via Gmail and managing Google Calendar events, enabling an AI agent to handle email and calendar operations through natural language.MIT
- FlicenseNot gradedqualityBmaintenanceA private, single-user MCP server that unifies Gmail, Microsoft 365/Outlook, and IMAP mailboxes for LLMs to search and read emails live, without storing or caching mailbox contents.-
- AlicenseNot gradedqualityAmaintenanceA local MCP server that unifies email and calendar management across multiple providers, enabling AI agents to search, read, and write with explicit approval and local-first security.2Apache 2.0