Install
"url": "https://mcpemails.com/api/mcp"Who it is for
If you want an agent to use an existing mailbox to read, search, send, organize, and schedule mail, without the server keeping message bodies long term, this service matches. Officially it is written as a hosted MCP server for Claude, Cursor, or any MCP-compatible client.
It suits people who can already add a remote HTTP server in the client and who will log in on the official site to bind a mailbox. First log in on the site and connect Gmail (one-click OAuth) or any IMAP/SMTP account (app-specific password). Credentials are encrypted with AES-256-GCM before they are written to the database. Site:
https://mcpemails.com
It is not for people who only want fully local IMAP, or who would grant delete on the first try. Permissions are split by key: you can grant only read:email, or grant send and folder management without exposing delete.
Official repository:
https://github.com/Albretsen/MCPEmails
First try in 3 minutes
The official recommended path is one: connect the hosted interface. Do not hunt for a local installer.
https://mcpemails.com/api/mcp
Prerequisites: the mailbox is already bound on that site; create a key that contains only read:email for this trial. In the client set url to that interface and put Authorization Bearer in headers. Keep the key only in local config. Do not paste it into the chat, and do not use the sample string from the docs.
Where to configure: the remote-server settings of the current MCP client. After connecting, make one low-risk call: pick a read or search action from the tools the client shows. Officially there are 11 tools; most pick an action by resource plus action. This page does not write function names in a row, so do not invent them. A read still goes out to the network and brings mail content into the chat; it is not a "no privacy boundary." Officially they claim mail is not stored, but this session still sees the body.
Success signal: one message or search result comes back, with no send, no folder change, and no delete. On 401, first check that Bearer matches the read-only key.
Usage cases
Case 1: read and search. The objects are read and search from the official capabilities, scoped to read:email only. Use a read or search action the client actually shows. The evidence has no field list; success is a subject or snippet coming back. Do not assume the server will archive long term.
Case 2: send or organize. The same official sentence also names send, organize, and schedule. Extra permissions are required. The confirmation point is that you have already seen the recipient and body, or the folder action about to run, and you accept that mail will really go out or labels will change, then act. Do not put delete in this step; without a delete scope, do not call related actions.
Limits
The exact names of the 11 tools are not confirmed in sequence on this page. Do not invent inbox or draft function names from common sense. Do not add unnamed automation or contacts features.
Do not connect without a bound mailbox or a read-only key. Send, organize, and schedule all change your real mailbox. Official docs do not write a step to recall already-sent mail. The hosted interface accesses the mailbox on your behalf, so there is a risk of mistaken account actions. App-specific passwords and OAuth tokens must not appear in the chat.