Hi eM Client team,
I’d like to request support for the Model Context Protocol (MCP) in eM Client.
MCP is an open standard developed by Anthropic for connecting AI assistants to external tools (email, calendars, CRMs, etc.) in a secure and structured way. It allows an AI client to call well‑defined “tools” exposed by an MCP server instead of screen‑scraping or ad‑hoc APIs. More about it here: https://modelcontextprotocol.io
It’s already being adopted by several AI clients and tools, and there are reference implementations and documentation here:
- Model Context Protocol site (spec and examples) modelcontextprotocol
- MCP Apps overview showing how desktop apps integrate tools via MCP blog.modelcontextprotocol
Why this would be valuable for eM Client:
- Allow AI assistants (desktop and cloud) to safely read, search, and act on email and calendar data via a standard protocol, instead of custom integrations. blog.modelcontextprotocol
- Make it possible to build MCP servers around eM Client data or to let eM Client act directly as an MCP client for external tools (e.g., CRM, ticketing, knowledge bases). blog.modelcontextprotocol
- Attract power users who are already building MCP‑based workflows and want to keep eM Client as their primary mail app.
From a product perspective, even a minimal MCP implementation (read‑only access to messages, search, and sending via a small set of tools) would already be very useful.
Could you please let me know:
- Whether MCP support is on your roadmap or under consideration.
- If there is a preferred channel (beta program, GitHub, etc.) where technically inclined users could help test or provide concrete use‑cases.
Thanks a lot for considering this – I think eM Client could be a great first‑class unit in the emerging MCP ecosystem.
Thanks, best…