Inbox Preview vs Email MCP

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

I
Inbox PreviewCommunication · Remote HTTP/SSE
Render HTML/.eml emails in real Gmail, Outlook & Yahoo web clients and screenshot them39FairAuth: no auth required
Email MCP logoEmail MCPCommunication · Local subprocess (stdio)Unified MCP server for email across Gmail (REST API), Outlook (Microsoft Graph), iCloud, and generic IMAP/SMTP. 24 tools for search, send, organize, and batch-manage emails with built-in OAuth2 and encrypted credential storage.68GreatAuth: other

Verdict: choose Inbox Preview 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?

I
Choose Inbox Preview when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: No auth required.
Explore Inbox Preview

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 want tools like email_list_accounts, email_add_account, email_remove_account.
Explore Email MCP

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
I
Inbox Preview
Email MCP logoEmail MCP
CategoryCommunicationCommunication
Quality signal39/100 · Fair68/100 · Great
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNo auth requiredother
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—26
Directory activity 1 views 0 installs 0 upvotes 8 views 0 installs 0 upvotes
ToolsNot listed33

Tools & capabilities

Inbox Preview tools

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

Email MCP tools 33

  • email_list_accountsList all configured email accounts and their connection status
  • email_add_accountAdd a new IMAP or iCloud email account (Gmail and Outlook require the setup wizard for OAuth)
  • email_remove_accountRemove an email account: deletes its stored credentials, revokes the Google grant for Gmail accounts, and removes Outlook tokens from the local token cache. The result reports whether provider-side revocation succeeded.
  • email_test_accountTest an email account connection
  • email_list_foldersList all email folders for an account
  • email_searchSearch emails with filters. By default returns compact results without full body content to save context. Set returnBody=true to include full email bodies.
  • email_getGet a single email by ID
  • email_get_threadGet an email thread by thread ID
  • email_get_attachmentGet an email attachment by ID, returns base64 encoded data
  • email_save_attachmentDownload an email attachment and save it directly to disk, returning metadata only (no base64 in the response) — avoids paying the token cost of round-tripping large attachments through the calling model. outputPath is relative to a fixed downloads directory (/home/user/.email-mcp/downloads, override with EMAIL_MCP_DOWNLOADS_DIR) and cannot escape it.
  • email_sendSend a new email
  • email_replyReply to an existing email
  • +21 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.

Inbox Preview

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "inbox-preview": {
      "command": "npx",
      "args": [
        "-y",
        "inbox-preview"
      ]
    }
  }
}

Email MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "marlinjai-email-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@marlinjai/email-mcp"
      ]
    }
  }
}

Frequently asked questions

Inbox Preview is categorized under Communication and uses a remote HTTP/SSE transport. Email MCP belongs to Communication and uses a local stdio subprocess. Pick Inbox Preview 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.

Inbox Preview has no declared pricing — check the project's own site. Auth: no auth required. 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 inbox-preview and marlinjai-email-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Inbox Preview has a quality signal of 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Email MCP has 68/100 (Great) with 8 views, 0 installs and 26 GitHub stars.