Email MCP Server for Cloudflare Workers
Integrates with AOL Mail accounts over IMAP/SMTP, providing tools for mailbox management, searching and reading messages, handling attachments and flags, organizing messages, and managing drafts and sending.
Integrates with Gmail accounts over IMAP/SMTP, enabling account management, mailbox and folder inspection, message search and retrieval, attachment access, flag updates, moving/archiving/deleting messages, and draft creation, updating, forwarding, and sending.
Integrates with iCloud Mail accounts over IMAP/SMTP, enabling mailbox and folder operations, message search and retrieval, attachment access, flag and move operations, and draft and send workflows.
Integrates with Zoho Mail accounts over IMAP/SMTP, providing tools for account connection testing, mailbox status, message search and retrieval, attachment handling, message organization, and draft creation and sending.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Email MCP Server for Cloudflare Workers
A container-free remote MCP server for Gmail, Outlook, iCloud, Yahoo, AOL, QQ Mail, NetEase Mail, Tencent Exmail, Fastmail, Zoho, and custom IMAP/SMTP accounts.
The Worker connects directly to IMAP and SMTP using Cloudflare outbound TCP sockets. Mailbox credentials are AES-256-GCM encrypted before being stored in Workers KV.
Table of contents
Related MCP server: imap-mcp-server
Public source, private deployments
This repository publishes the server source under the MIT License. It does not provide a shared, publicly accessible email service. Every operator deploys their own Worker, KV namespace, Cloudflare Access application, Microsoft Entra application, and secrets.
All configured mailboxes share one encrypted account store within a deployment. The server is therefore intended for one owner or a small group of mutually trusted users. Do not grant Cloudflare Access to unrelated tenants or users who should not share mailbox access.
The checked-in wrangler.toml is a sanitized example. For a local or manually initiated
deployment, copy it to the ignored production configuration and replace every placeholder with
identifiers from your own accounts:
cp wrangler.toml wrangler.production.tomlNever commit wrangler.production.toml, .dev.vars, private keys, certificates, Worker secrets,
mailbox credentials, or OAuth client secrets.
For repository-connected Cloudflare builds, do not commit or upload
wrangler.production.toml. The build generates an ignored wrangler.generated.json containing
the real KV binding while preserving the runtime variables and secrets already configured in the
Cloudflare dashboard. See Cloudflare repository builds.
Tools
email_add_account,email_list_accounts,email_update_account_sender,email_remove_accountemail_test_connectionemail_list_folders,email_get_mailbox_status,email_get_all_account_mailbox_statusesemail_search_messages,email_search_all_accounts,email_list_all_inbox_messages,email_get_message,email_get_message_thread,email_get_message_attachmentemail_update_message_flags,email_move_messages,email_archive_messages,email_move_messages_to_trash,email_delete_messages_permanentlyemail_create_message_draft,email_create_forward_draft,email_update_message_draft,email_send_draft
Every tool publishes an MCP output schema and returns validated structuredContent. A JSON text
copy is also returned for compatibility with clients that do not yet consume structured output.
Local setup
Create .dev.vars:
CREDENTIAL_ENCRYPTION_KEY=base64-encoded-32-byte-key
ACCESS_LOCAL_DEV=trueGenerate the encryption key with:
openssl rand -base64 32Then run:
npm install
npm run devDependency installation generates worker-configuration.d.ts from the public Wrangler config
using the installed Wrangler version. The generated file is ignored by Git and formatting tools.
After changing wrangler.toml, or if you install with --ignore-scripts, run npm run cf-typegen
before type checking or starting development.
Connect an MCP client to http://localhost:8787/mcp.
ACCESS_LOCAL_DEV bypasses Access verification only when the request hostname is localhost,
127.0.0.1, or ::1. Never configure it as a production Worker variable or secret.
MCP tool calls emit structured events to Cloudflare Workers Logs with the tool name, status,
duration, and a safe error category. Tool arguments, upstream error text, credentials, and email
content are not logged.
View production events under Workers & Pages → email-mcp-server → Observability or stream
local/deployed events with npx wrangler tail.
In VS Code, open Run and Debug, select Email MCP: Local server, and click Run (or
press F5). Wrangler loads the same .dev.vars file automatically in the integrated terminal.
Cloudflare Access
Production authentication is handled by a Cloudflare Access self-hosted application with
Managed OAuth. The Worker also verifies every Cf-Access-Jwt-Assertion signature, issuer, and
audience before routing a request. Assertions issued for Access service tokens (non-identity
authentication, which carry a common_name instead of an email claim) are accepted as well,
so programmatic clients such as MCP Inspector can connect with CF-Access-Client-Id and
CF-Access-Client-Secret headers once a service-auth policy allows the token.
Deploy the Worker once to obtain its
*.workers.devhostname. Until Access is configured, the placeholder issuer and audience make the Worker fail closed.In Zero Trust → Access controls → Applications, create a Self-hosted and private application for the Worker hostname.
Add an Allow policy restricted to your email or identity group. This server uses one shared encrypted account store, so do not authorize unrelated users.
Configure one-time PIN or an identity provider. Enable MFA at the identity provider or in the Access policy where appropriate.
Under the application's advanced settings, enable Managed OAuth. Configure only the redirect URIs required by your MCP clients; enable localhost or loopback redirects only when needed for local clients such as MCP Inspector.
Copy the application AUD tag and your Zero Trust team domain into the ignored
wrangler.production.toml:
[vars]
TEAM_DOMAIN = "https://your-team.cloudflareaccess.com"
POLICY_AUD = "your-access-application-aud-tag"
OUTLOOK_CLIENT_ID = "your-microsoft-entra-application-client-id"
OUTLOOK_TENANT = "consumers"See Cloudflare's Secure MCP servers and Managed OAuth guides for the current dashboard and redirect-URI configuration.
Administrator password sign-in (management UI)
The MCP endpoint always requires Cloudflare Access. As an alternative for the web management pages only, the Worker can accept an operator-chosen username and password:
Set the
ADMIN_PASSWORDsecret on the Worker, and optionally theADMIN_USERNAMEvariable (defaultadmin).Open
/login, sign in, and you will be redirected to the management page. The session cookie is encrypted withCREDENTIAL_ENCRYPTION_KEY, lasts 24 hours, and can be ended with the Sign out button. Five failed attempts from one IP address lock sign-in for 15 minutes.
With this enabled, the Cloudflare Access application can be scoped to the /mcp path
only: the management pages then rely on the password sign-in, while MCP clients keep
authenticating through Access. A valid Access assertion is still accepted on the
management pages when one is present.
Microsoft Entra app registration for Outlook
Outlook.com, Hotmail, Live, and Microsoft 365 accounts use interactive Microsoft OAuth. The Microsoft account that owns the app registration does not need to be the mailbox account. Each mailbox owner signs in and grants the app access when Outlook is selected in the account form.
In the Microsoft Entra admin center, open Entra ID → App registrations → New registration.
Enter any name and choose the supported account type:
For Outlook.com, Hotmail, and Live accounts only, choose Personal Microsoft accounts only.
To support both personal and work/school accounts, choose Accounts in any organizational directory and personal Microsoft accounts.
After registering, copy Application (client) ID from Overview. Do not use the object ID, client-secret ID, or client-secret value as
OUTLOOK_CLIENT_ID.Open Authentication → Add a platform → Web and add every callback URL from which the flow will be started. The path and port must match exactly:
https://<worker>.<subdomain>.workers.dev/oauth/outlook/callback http://localhost:8787/oauth/outlook/callbackThe localhost entry is only needed for local development. Add another localhost URL if Wrangler runs on a different port. Leave both implicit grant checkboxes clear and leave Allow public client flows disabled; this server uses the authorization-code flow with PKCE.
Open API permissions → Add a permission → APIs my organization uses → Office 365 Exchange Online → Delegated permissions, then add:
IMAP.AccessAsUser.AllSMTP.Send
The Worker also requests
openid,profile,email, andoffline_accessduring sign-in. Organizational policies may require an administrator to grant consent; personal accounts can normally grant consent interactively.Open Certificates & secrets → Client secrets → New client secret. Copy the secret's Value immediately. Microsoft only displays it once. Do not copy the Secret ID.
Set the application client ID and appropriate Microsoft sign-in tenant in
wrangler.production.toml:
[vars]
OUTLOOK_CLIENT_ID = "your-application-client-id"
OUTLOOK_TENANT = "consumers"Use "consumers" for personal Microsoft accounts, "organizations" for work/school accounts,
"common" for both, or a specific tenant ID for one organization. The app registration's
supported account type must allow the value selected here.
For local development, put the client-secret Value in .dev.vars:
OUTLOOK_CLIENT_SECRET="your-client-secret-value"For production, install it as a Worker secret instead of placing it in the TOML configuration:
printf '%s' 'your-client-secret-value' | npx wrangler secret put OUTLOOK_CLIENT_SECRET --config wrangler.production.tomlCommon configuration errors:
unauthorized_clientor “not enabled for consumers” means the app's supported account type does not allow personal accounts, orOUTLOOK_CLIENT_IDis not the Application (client) ID.AADSTS50011means the callback URL does not exactly match a configured Web redirect URI.invalid_clientduring the callback usually means the secret is expired or the Secret ID was supplied instead of the secret Value.
See Microsoft's documentation for registering an application, redirect URIs, client credentials, and OAuth for IMAP and SMTP.
Google OAuth client for Gmail
Gmail accounts can use interactive Google OAuth sign-in instead of an app password. The Google account that owns the Cloud project does not need to be the mailbox account. Each mailbox owner signs in and grants the app access when Gmail is selected in the account form.
In the Google Cloud console, create or select a project.
Open APIs & Services → OAuth consent screen, choose External, and fill in the app name and contact emails.
Open APIs & Services → Credentials → Create Credentials → OAuth client ID, choose Web application, and add this authorized redirect URI exactly:
https://<worker>.<subdomain>.workers.dev/oauth/google/callbackCopy the client ID (it ends in
.apps.googleusercontent.com) asGOOGLE_CLIENT_IDand install the client secret as theGOOGLE_CLIENT_SECRETWorker secret, the same way asOUTLOOK_CLIENT_SECRETbelow.
The Worker requests the https://mail.google.com/ scope with openid, email, and profile,
using access_type=offline and prompt=consent so Google issues a refresh token for IMAP and
SMTP access.
While the consent screen publishing status is Testing, Google expires refresh tokens after
7 days and the mailbox stops syncing until it is connected again. Publish the app to
Production to keep refresh tokens valid. An unverified app shows a warning during sign-in
that the signed-in user can accept; Google verification is only required to distribute the app
publicly. If GOOGLE_CLIENT_ID or GOOGLE_CLIENT_SECRET is unset, the Gmail form keeps using
an app password instead.
Production secret and deployment
Create and fill wrangler.production.toml as described above. The public example intentionally
cannot be deployed until its placeholder KV namespace and Access values are replaced.
For an existing deployment, first confirm the required secrets are present:
npx wrangler secret list --config wrangler.production.tomlDo not replace an existing CREDENTIAL_ENCRYPTION_KEY; existing encrypted account records depend
on it. For a brand-new deployment with no stored accounts, generate and install the key without
writing it to disk:
CREDENTIAL_ENCRYPTION_KEY="$(openssl rand -base64 32)"
printf '%s' "$CREDENTIAL_ENCRYPTION_KEY" | npx wrangler secret put CREDENTIAL_ENCRYPTION_KEY --config wrangler.production.toml
unset CREDENTIAL_ENCRYPTION_KEYDeploy after updating the Access variables:
npm run deployThe production MCP endpoint is https://<worker>.<subdomain>.workers.dev/mcp.
Open https://<worker>.<subdomain>.workers.dev/ to manage email accounts through the
Access-protected web interface. Credentials submitted there go directly from the browser to the
Worker and do not pass through an MCP client or language model.
Connect ChatGPT
After deploying the Worker and configuring Cloudflare Access, add its MCP endpoint to ChatGPT:
MCP server URL: https://<worker>.<subdomain>.workers.dev/mcpOpen Settings → Security and login and turn on Developer mode.
Open Settings → Plugins and select Add custom plugin.
Enter
Email MCP Serveras the name andhttps://<worker>.<subdomain>.workers.dev/mcpas the server URL.Select OAuth if prompted, then select Scan Tools and complete the Cloudflare Access sign-in.
Select Create, then choose the plugin in a new chat.
Cloudflare repository builds
Cloudflare only receives files committed to the connected Git repository, so it cannot read the
ignored local wrangler.production.toml. Configure the existing Worker as follows:
Keep these runtime values under Settings → Variables and Secrets:
Plaintext:
OUTLOOK_CLIENT_ID,OUTLOOK_TENANT,GOOGLE_CLIENT_ID,POLICY_AUD, andTEAM_DOMAIN.Secret:
CREDENTIAL_ENCRYPTION_KEY,OUTLOOK_CLIENT_SECRET, andGOOGLE_CLIENT_SECRET.
Under Settings → Build → Variables and Secrets, add a build environment variable named
EMAIL_KV_NAMESPACE_ID, set it to the existingEMAIL_KVnamespace ID, and enable Encrypt. Runtime variables from step 1 are not available to repository build commands.Set the deploy command to
npm run cloudflare:uploadfor the first verification build. This creates a version without promoting it to the active deployment.After verifying the uploaded version, change the deploy command to
npm run cloudflare:deployto deploy successfulmainbuilds automatically.
The repository includes .node-version, so Cloudflare uses the supported Node version without a
separate build variable. The generated configuration sets keep_vars: true, omits vars, and
declares the required secret names without supplying or replacing their values. It is written
with owner-only file permissions and ignored by Git.
Do not replace CREDENTIAL_ENCRYPTION_KEY on an existing deployment. Existing encrypted account
records can only be read with the key that encrypted them.
Dependency updates
Dependabot checks npm packages and GitHub Actions weekly. Minor and patch updates are grouped into
one pull request per ecosystem (npm-routine and github-actions-routine). Major updates remain
individual pull requests and require manual review; the auto-merge workflow never selects them.
This MCP server declares @modelcontextprotocol/sdk and @modelcontextprotocol/server as direct
production dependencies. Agents 0.31.0 and later make these peer dependencies optional, so npm does
not install them automatically. Keep both packages pinned to the versions required by the installed
agents release and update them together with agents in package.json and package-lock.json.
Agents 0.32.0 requires SDK 1.32.2 and server 2.4.0.
The repository enables strict peer dependency checking in .npmrc; do not bypass conflicts with
--force or --legacy-peer-deps.
CI generates Worker types during npm ci and validates them with the updated dependencies.
No workflow commits generated types to Dependabot branches, allowing Dependabot to keep rebasing
and updating its pull requests automatically. CI also checks the installed Agents/MCP dependency
tree with npm run dependencies:check and bundles the Worker with npm run build:check. The bundle
check uses the public Wrangler configuration without credentials and does not upload or deploy.
For same-repository Dependabot pull requests targeting main, the workflow reads Dependabot's
metadata without checking out or executing pull request code. It queues squash auto-merge only for
minor and patch updates. GitHub merges the pull request after every required check and ruleset
condition succeeds, using the current pull request head commit.
Enable the following repository settings for this workflow:
Under Settings → General → Pull Requests, enable Allow auto-merge.
Configure the
mainruleset to require branches to be up to date and these status checks:checks(theCIworkflow, GitHub Actions app ID15368) andWorkers Builds: email-mcp-server(Cloudflare app ID85455). Keep Cloudflare builds enabled for Dependabot branches; a missing required check blocks merging.If the ruleset restricts who can update
main, it must allow the GitHub Actions identity used by the workflow to complete an approved auto-merge. Keep required checks enabled and do not use a bypass actor for the Dependabot workflow. An admins-only update restriction can leave auto-merge queued indefinitely.
Account settings
Prefer the web management interface at the Worker root to add, edit, or remove accounts. Editing
can change the display name, email address, IMAP/SMTP hosts, ports, and TLS modes without replacing
the stored password or OAuth tokens. The email_add_account tool remains available for clients
that explicitly need programmatic setup.
To use an iCloud or Outlook alias, choose Edit, leave Login email address as the address
used to authenticate, enter the mailbox's authorized addresses in Email aliases (comma
separated), and set Default From address to the address you want to send from. Leaving
Default From blank uses the login email. Sender-only changes save without a connection test or
replacing credentials. Existing accounts continue using their login email until you change this.
For MCP clients, call email_list_accounts to get the account ID, login email, aliases, and
defaultFrom. Then use email_update_account_sender, for example:
{
"accountId": "account-id-from-email_list_accounts",
"aliases": ["personal@icloud.com", "work@icloud.com"],
"defaultFrom": "personal@icloud.com"
}The same aliases and defaultFrom fields are available on email_add_account. Updating aliases
replaces the entire list; omitted settings are preserved. Set defaultFrom to the login email to
reset it. To remove all aliases, supply aliases: [] and reset the default in the same call if it
currently uses an alias. Addresses are matched without regard to case and duplicates are removed.
These tools only configure this MCP server: they do not create aliases at the provider or sync
the provider's default sender automatically. First enable the address with your provider; see
Apple's iCloud alias settings.
Exchange Online administrators may need to enable sending from aliases; see
Microsoft's send-from-alias guidance.
The provider can still reject or rewrite a From address according to its own configuration.
Each configured account also has a Test connection action that authenticates with its stored credentials and reports the connection result without exposing those credentials to the browser.
Use the exact folder path returned by email_list_folders. Search results default to newest
first; set sortOrder to oldest for chronological order. Results include their folder path;
pass that folder and IMAP UID to email_get_message or mutation tools.
email_search_messages returns a structured result with status, outcome, count, total, empty,
messages, and an opaque nextCursor when another page is available. Pass nextCursor back as
cursor with otherwise identical search criteria. An outcome of no_matches explicitly means
the IMAP search completed successfully with zero matching messages; it does not indicate a
connection or folder error.
email_list_all_inbox_messages lists message summaries from INBOX across all configured accounts,
or the supplied accountIds, without requiring search filters. email_search_all_accounts applies the
same summary shape with optional filters across INBOX by default or another supplied folder. Both
return a flat message list with account identity on every message plus per-account totals, errors,
and account-specific nextCursor values for follow-up single-account searches. email_get_all_account_mailbox_statuses
checks message counts across the same selected accounts. These multi-inbox tools are read-only;
archive, move, trash, delete, and mark operations remain scoped to one explicit account.
Search filters can be combined and include from, to, cc, bcc, subject, body-only text,
all header/body text, Message-ID, internal and sent dates, message size, IMAP keywords, and the
seen, flagged, answered, draft, or deleted states. All supplied filters must match. Search
summaries include messageId, inReplyTo, references, and a header-derived threadId.
State filters use explicit three-way values rather than checkboxes: for example, seen accepts
any, seen, or unseen, while flagged accepts any, flagged, or unflagged. The answered,
draft, and deleted filters follow the same pattern, so an unset state is distinct from not
filtering by that state.
email_get_message_thread accepts the folder and IMAP UID of any message and returns up to 100 summaries from
the same header-based conversation, oldest first. This works without requiring the optional IMAP
THREAD extension, but it is scoped to one folder and depends on messages having valid
Message-ID, In-Reply-To, and References headers. Use each returned IMAP UID with email_get_message when
full message content is required.
email_get_mailbox_status returns the total and unread message counts plus IMAP RECENT, UIDNEXT,
and UIDVALIDITY values for one folder.
email_get_message includes a zero-based attachmentIndex for every attachment. Pass the folder, IMAP UID,
and index to email_get_message_attachment to retrieve its raw bytes as contentBase64.
IMAP configuration is required for every account. SMTP is optional; accounts without it can read,
search, draft, and manage mail but cannot use email_send_draft. email_list_accounts reports
capabilities.canSend so MCP clients can determine whether sending is available before attempting it.
email_update_message_flags accepts one IMAP UID or an array of up to 100 IMAP UIDs and seen: true/false for read/unread
and flagged: true/false for flagged/unflagged. Either or both states can be changed in one call.
email_move_messages accepts either one IMAP UID or an array of up to 100 IMAP UIDs and moves them in one IMAP
operation to an explicit targetFolder.
Use email_archive_messages for archiving; it moves up to 100 messages to the account's advertised
IMAP Archive folder, or the provider all-mail folder when that is the advertised archive destination.
Use email_move_messages_to_trash for normal deletion; it moves up to 100 messages to the folder advertised with
the IMAP \Trash special-use flag. email_delete_messages_permanently permanently marks and expunges up to 100
messages by IMAP UID and should only be used when permanent deletion is intended.
Draft creation (including replies and forwards) uses defaultFrom unless you supply from to
select the login email or a configured alias. All draft tools return the saved from address.
email_update_message_draft preserves it when from is omitted and lets you change it explicitly.
Changing the default affects new drafts only. SMTP uses the draft's saved From for its envelope
sender while authenticating with the login email and existing credentials. A sender removed from
the configured addresses cannot be sent until you update the draft or add the alias again.
Automatically derived reply and reply-all recipients exclude the login email and all configured
aliases; explicit recipient overrides are respected.
Sending is a two-step workflow: call email_create_message_draft, then pass its returned folder and
IMAP UID field uid to email_send_draft. After SMTP accepts the message, the server appends a copy to the IMAP Sent
folder and then removes the draft. A Sent append failure is reported as sentSaved: false, and a
cleanup failure is reported as draftDeleted: false, without reporting the already accepted send
as failed.
Draft attachments use native MIME encoding. Pass up to 20 attachments as attachments, each
with filename, contentType, and contentBase64. The base64 value must contain the raw file
bytes without a data-URL prefix. Draft text and HTML bodies are emitted as quoted-printable MIME
parts; base64 is only required for attachment bytes.
To create a reply, call email_create_message_draft with replyToMessage.folder and
the original message's IMAP UID in replyToMessage.uid. The server derives the recipient and subject and adds the correct
In-Reply-To and References headers. Reply drafts quote the original message by default; set
replyToMessage.quoteOriginal: false only when the original message should not be quoted. Set
replyAll within replyToMessage when needed; top-level to, cc, and subject values override
the derived values. Set top-level replyTo when the outgoing draft should include a Reply-To header.
email_create_forward_draft creates a forward draft and includes the original attachments unless
includeAttachments is false. email_update_message_draft replaces an existing IMAP draft and returns its
new IMAP UID; omitted fields are preserved, and an empty attachments array removes all attachments.
Provider | IMAP | SMTP | Authentication |
Gmail |
|
| Google OAuth2 sign-in or app password |
Outlook |
|
| Microsoft OAuth2 sign-in |
iCloud |
|
| Apple app-specific password |
Yahoo |
|
| Yahoo app password |
AOL |
|
| AOL app password |
QQ Mail |
|
| QQ authorization code |
163 Mail |
|
| NetEase authorization code |
126 Mail |
|
| NetEase authorization code |
Tencent Exmail |
|
| Password or authorization code |
Fastmail |
|
| Fastmail app password |
Zoho |
|
| Zoho app password |
Custom | Provider supplied | Provider supplied | Password or OAuth2 |
For port 587, set smtpSecure to false; the native SMTP client negotiates STARTTLS. Cloudflare blocks outbound SMTP port 25.
Outlook refresh uses the Entra application client ID and Worker-held client secret. Microsoft may require tenant administrator consent for delegated Exchange permissions, depending on the tenant's consent policy. SMTP AUTH must also be enabled for the Exchange Online mailbox if sending fails.
Security
Cloudflare Access authenticates users and enforces the application policy before traffic reaches
the Worker. The Worker independently validates the Access JWT using the team JWKS, issuer, and
application audience. Mailbox passwords and OAuth tokens are AES-256-GCM encrypted in Workers KV
and are never returned by account tools. Changing CREDENTIAL_ENCRYPTION_KEY makes existing
stored accounts unreadable.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
Email inboxes for AI agents: send, receive, reply, search, and manage threaded email over MCP.
Hosted email MCP for your own Gmail, Outlook.com, Microsoft 365, iCloud or IMAP inbox: read, search, draft, reply in thread, forward and file mail. It moves or flags up to 500 messages in one call, and a send leaves exactly one copy in Sent. A calendar is a separate connection, and connecting one adds diary and scheduling tools.
Email: search, read, fetch attachments; attach files when the MCP client supports inputs.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables remote email management for Gmail, Outlook, iCloud, Yahoo, and custom IMAP/SMTP accounts via MCP, supporting account setup, search, read, draft, and send operations.MIT
- AlicenseBqualityCmaintenanceEnables email integration through MCP, including sending, receiving, searching, replying to, and forwarding emails, plus folder management and multi-account support with encrypted credential storage.401,009 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to work with ordinary email accounts over IMAP and SMTP — listing mailboxes, searching and reading messages, managing flags, folders, attachments and drafts, and sending, replying or forwarding mail. Supports multiple accounts and providers with per-account safety controls such as read-only mode, send/delete restrictions, recipient allow-lists and rate limits.35 npmMIT
- AlicenseAqualityBmaintenanceEnables MCP clients to manage multiple IMAP/SMTP mailboxes by listing folders, searching and reading messages, preparing Markdown drafts and replies, and sending only a draft the user has reviewed and confirmed.944 npmMIT