Email

This Email MCP Server provides remote access to your email accounts via HTTP/SSE, letting you read, search, send, reply, and forward messages securely through Claude Web and other MCP clients. It supports multiple providers, secure storage, and easy remote access, so you can manage your mail from anywhere.

How to use

Connect to the MCP server from your MCP client or Claude Web using the provided SSE endpoint. You can manage multiple email accounts, perform common mail actions, and switch between providers like Gmail, Outlook, Yahoo, and others. Use the HTTP/SSE bridge for remote access or run the local server and connect via the CLI/SDK you prefer.

How to install

Prerequisites: ensure you have Node.js installed for the local MCP server setup, and Docker if you want to run the Docker deployment.

1. Clone the project and install dependencies locally.

2. Build the local MCP server package.

3. Run the local setup to configure your accounts via the web wizard.

4. (Optional) Run the server in Docker for remote deployment and use the gateway URL to connect from Claude Web.

Configuration and connectivity

The server can be accessed in two ways: a remote HTTP/SSE endpoint and a local stdio-based runtime. Choose the method that fits your workflow.

HTTP (remote) endpoint example for Claude Web Custom Connector: use the following URL to connect and start streaming events.

MCP endpoints and configs

{
  "mcpServers": {
    "imap_email": {
      "type": "http",
      "name": "imap_email",
      "url": "https://mcp.svsfinpro.ru/email/sse",
      "args": []
    }
  }
}

Local runtime (stdio) setup

If you want to run a local instance and connect via a stdio channel, use the command shown here. This is the runtime invocation you need to start the local MCP server process.

{
  "mcpServers": {
    "imap_email": {
      "type": "stdio",
      "name": "imap_email",
      "command": "node",
      "args": ["/path/to/imap-mcp-server/dist/index.js"]
    }
  }
}

Security and storage

All credentials are stored securely using AES-256 encryption. Do not use your main password; instead, generate App Passwords for each provider and store them securely within the container or vault.

Environment and deployment notes

Environment variables you may configure include HOST, PORT, IMAP_SERVER_PATH, and LOG_LEVEL to customize the server runtime.

Deployment can be done locally or via Docker. When deploying with Docker, you can verify health with a simple health check request.

Troubleshooting

If the server container fails to start, view logs with the container management tool you use (for example, docker logs). Verify that App Passwords are correct, IMAP is enabled for the accounts, and network access is not blocked by a firewall.

Notes

A health endpoint is available to confirm the server is running, and a dedicated gateway URL is provided for Claude Web integration.

Available tools

imap_add_account

Add a new email account to manage via MCP.

imap_list_accounts

List all configured email accounts.

imap_remove_account

Remove a configured email account.

imap_connect

Establish a connection to a configured account.

imap_disconnect

Disconnect from a configured account.

imap_search_emails

Search emails across configured mailboxes.

imap_get_email

Retrieve a specific email by identifier.

imap_get_latest_emails

Fetch the most recent emails.

imap_mark_as_read

Mark an email as read.

imap_mark_as_unread

Mark an email as unread.

imap_delete_email

Delete an email.

imap_send_email

Send a new email.

imap_reply_to_email

Reply to an email.

imap_forward_email

Forward an email.

imap_list_folders

List mail folders.

imap_folder_status

Get the status of a folder.

imap_get_unread_count

Get count of unread messages.