MCP Server

Connect MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A MCP server that reads email with notmuch and uses sendmail for LaTeX-enhanced email composition. The mcp mcp server is what makes that connection.

What the server does

Let Claude be your email assistant! MCP Notmuch Sendmail connects Claude Desktop to your notmuch email database, allowing it to:

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• find_email_thread — Find email threads in the notmuch database
• Input — notmuch_search_query (string)
• view_email_thread — View all messages for an email thread
• compose_new_email — Compose a new email draft from markdown. A signature will be automatically added if SENDMAIL_EMAIL_SIGNATURE_HTML is set
• Inputs — - subject (string): Email subject
• compose_email_reply — Compose a reply to an existing email thread. A signature will be automatically added if SENDMAIL_EMAIL_SIGNATURE_HTML is set
• send_email — Sends the composed email draft
• sync_emails — Synchronizes emails by running the configured script
• Tools — The Tools tool exposed by this server
• English — The English tool exposed by this server
• German — The German tool exposed by this server
• French — The French tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: NOTMUCH_DATABASE_PATH, NOTMUCH_REPLY_SEPARATORS, SENDMAIL_FROM_EMAIL, SENDMAIL_EMAIL_SIGNATURE_HTML, NOTMUCH_SYNC_SCRIPT, LOG_FILE_PATH, DRAFT_DIR. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — find_email_thread, Input, view_email_thread and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Rune Kaagaard; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.