Email Outreach vs Email MCP

A side-by-side look at the Email Outreach and Email MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

E
Email OutreachCommunication · Remote HTTP/SSE
Goal-directed email outreach: research, draft, send, triage replies. Real data, never fabricated.37FairAuth: not declared
Email MCP logoEmail MCPCommunication · Local subprocess (stdio)IMAP/SMTP email MCP server with 42 tools for reading, searching, sending, scheduling, and managing emails across multiple accounts. Supports IMAP IDLE push, AI triage, desktop notifications, and auto-detects providers like Gmail, Outlook, and iCloud.69GreatAuth: other

Verdict: choose Email Outreach for communication work over a hosted endpoint; choose Email MCP for communication as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

E
Choose Email Outreach when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a remote HTTP/SSE transport.
Explore Email Outreach

Email MCP logoChoose Email MCP when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: other.
  • You have the keys it needs: MCP_EMAIL_ADDRESS, MCP_EMAIL_PASSWORD, MCP_EMAIL_IMAP_HOST, MCP_EMAIL_SMTP_HOST, EMAIL_ACCOUNTS.
  • You want tools like list_accounts, list_mailboxes, list_emails.
Explore Email MCP

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
E
Email Outreach
Email MCP logoEmail MCP
CategoryCommunicationCommunication
Quality signal37/100 · Fair69/100 · Great
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredother
PricingNot declaredFree
Required env varsNone listedMCP_EMAIL_ADDRESSMCP_EMAIL_PASSWORDMCP_EMAIL_IMAP_HOSTMCP_EMAIL_SMTP_HOSTEMAIL_ACCOUNTS
Verified ownerCommunity listingCommunity listing
GitHub stars—135
Directory activity 0 views 0 installs 0 upvotes 8 views 0 installs 0 upvotes
ToolsNot listed52

Tools & capabilities

Email Outreach tools

No tool names declared yet. Check the project README from the listing page.

Email MCP tools 52

  • list_accountsList all configured email accounts
  • list_mailboxesList folders with unread counts and special-use flags
  • list_emailsPaginated email listing with date, sender, subject, and flag filters; marks bulk mail; optional body preview
  • get_emailRead full email content with attachment metadata and bulk-mail classification (HTML converted to readable text by default)
  • get_emailsFetch full content of multiple emails in a single call (max 20); same bulk markers
  • get_email_statusGet read/flag/label state of an email without fetching the body
  • search_emailsSearch by keyword across subject, sender, and body; same bulk markers and optional preview as `list_emails
  • download_attachmentDownload an email attachment by filename or MIME part id, base64-encoded or (if configured) saved to the server's attachment download directory
  • find_email_folderDiscover the real folder(s) an email resides in (resolves virtual folders)
  • extract_contactsExtract unique contacts from recent email headers
  • get_threadReconstruct a conversation thread via References/In-Reply-To; same bulk markers
  • list_templatesList available email templates
  • +40 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Email Outreach

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "email-outreach": {
      "url": "https://openhelm.ai/mcp/email-outreach"
    }
  }
}

Email MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "codefuturist-email-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@codefuturist/email-mcp"
      ],
      "env": {
        "MCP_EMAIL_ADDRESS": "YOUR_MCP_EMAIL_ADDRESS_HERE",
        "MCP_EMAIL_PASSWORD": "YOUR_MCP_EMAIL_PASSWORD_HERE",
        "MCP_EMAIL_IMAP_HOST": "YOUR_MCP_EMAIL_IMAP_HOST_HERE",
        "MCP_EMAIL_SMTP_HOST": "YOUR_MCP_EMAIL_SMTP_HOST_HERE",
        "EMAIL_ACCOUNTS": "YOUR_EMAIL_ACCOUNTS_HERE"
      }
    }
  }
}

Frequently asked questions

Email Outreach is categorized under Communication and uses a remote HTTP/SSE transport. Email MCP belongs to Communication and uses a local stdio subprocess. Pick Email Outreach for communication work and Email MCP for communication.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Email Outreach has no declared pricing — check the project's own site. Email MCP is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add email-outreach and codefuturist-email-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Email Outreach has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Email MCP has 69/100 (Great) with 8 views, 0 installs and 135 GitHub stars.