Ethora MCP Server vs Email MCP

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

Ethora MCP Server logoEthora MCP ServerCommunication · Local subprocess (stdio)MCP server for the Ethora chat & messaging platform: chat ops, AI agents, RAG, automation.67GreatAuth: oauth 2.0Email 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 Ethora MCP Server for communication work as a local process; 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?

Ethora MCP Server logoChoose Ethora MCP Server when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
  • You have the keys it needs: ETHORA_API_URL, ETHORA_APP_JWT, ETHORA_B2B_TOKEN, ETHORA_MCP_AUTH_ISSUER.
  • You want tools like ethora-configure, ethora-status, ethora-help.
Explore Ethora MCP Server

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.

SpecEthora MCP Server logoEthora MCP ServerEmail MCP logoEmail MCP
CategoryCommunicationCommunication
Quality signal67/100 · Great68/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthOAuth 2.0other
PricingFreeFree
Required env varsETHORA_API_URLETHORA_APP_JWTETHORA_B2B_TOKENETHORA_MCP_AUTH_ISSUERNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars626
Directory activity 5 views 0 installs 0 upvotes 8 views 0 installs 0 upvotes
Tools8933

Tools & capabilities

Ethora MCP Server tools 89

  • ethora-configureSet the Ethora API URL and credentials for this MCP session. Stores values in memory only; each call merges with omitted fields kept. Alternative to env vars (ETHORA_API_URL / ETHORA_APP_JWT / ETHORA_APP_TOKEN / ETHORA_B2B_TOKEN). On a hosted server `apiUrl` is fixed and cannot be changed; credentials are per session. Auth: none required — this establishes auth material. Errors: only if a value is structurally invalid. Follow with an `ethora-auth-use-*` tool to pick the active mode.
  • ethora-statusReport the current Ethora MCP session state: configured API URL, active auth mode, which credentials are present (booleans like `hasAppJwt` — values never echoed), the selected appId/agentId, and `hosted`/`sessionId` on the hosted (Streamable HTTP) server. Auth: none required. Errors: effectively none. Related: `ethora-doctor` for an active connectivity check.
  • ethora-helpTask-oriented orientation for this MCP server: explains the three Ethora auth modes (user / app-token / B2B) and recommends next tool calls + recipes based on current session state. Auth: none required — inspects state, no API calls. Errors: effectively none. Related: pass a recommended recipe id to `ethora-run-recipe`.
  • ethora-run-recipeExecute a built-in recipe — an ordered sequence of this server's own tool calls — by id. Recipes capture common flows (B2B bootstrap, broadcast, sources ingest). Use `dryRun: true` to preview resolved steps. Omit `recipeId` to list runnable recipes for a `goal`. Requires: the inputs the chosen recipe lists; call without `recipeId` first to see the recipes and their required inputs. Auth: depends on the recipe's steps — configure those first (see `ethora-help`). Errors: stops at the first failing step and returns the partial log; a missing required `vars` entry fails fast before any step runs.
  • ethora-doctorDiagnose the session: validate the config is internally consistent for the active auth mode and ping the Ethora API (`GET /v1/ping`). Returns `{ state, checks, ping, suggestions }`. Auth: none required; report is tailored to whatever credentials are set. Errors: rarely throws — instead returns `suggestions` and a `ping.ok: false` block when the API is unreachable.
  • ethora-auth-use-appSwitch this session's active auth mode to app-token, so subsequent app-scoped calls authenticate with the configured `appToken`. Auth: requires an `appToken` to already be configured (via `ethora-configure`, ETHORA_APP_TOKEN env, or `ethora-app-select`). Errors: returns an error if no `appToken` is configured. Related: use after `ethora-app-select`.
  • ethora-auth-use-userSwitch this session's active auth mode to user-session, so subsequent calls authenticate as a logged-in Ethora user. Auth: the switch needs nothing, but user-auth tools only work once `ethora-user-login` stores a user token (login also needs a configured `appJwt`). Errors: none on the switch; downstream tools return 401 until login succeeds. Related: follow with `ethora-user-login`.
  • ethora-auth-use-b2bSwitch this session's active auth mode to B2B, so subsequent calls authenticate as a tenant actor via the `x-custom-token` header. Auth: requires a `b2bToken` (JWT with `type=server`) to already be configured (via `ethora-configure` or ETHORA_B2B_TOKEN env). Errors: returns an error if no `b2bToken` is configured. Related: server-side automation — pairs with `ethora-b2b-app-create`, `ethora-users-batch-create-v2`, `ethora-app-tokens-*-v2`.
  • ethora-app-selectSet the current app context for this session so app-scoped tools can omit their `appId` argument. Stores `currentAppId` and, if given, `appToken` (which defaults the auth mode to app-token unless `authMode` overrides). Auth: none required to set the context. Errors: effectively none — a non-existent `appId` is not validated here; the first app-scoped API call surfaces the 404. Related: pairs with `ethora-auth-use-app`.
  • ethora-chats-broadcast-v2Enqueue an asynchronous broadcast job posting a message to one or more chat rooms of an app — returns a `jobId`; messages are not sent synchronously. Targeting is exclusive: `allRooms`, `chatIds`, or `chatNames`, not a mix. Requires: a selected app with at least one room (`ethora-app-create-chat`). Auth: app-token mode OR B2B mode with an explicit `appId`. Errors: 401/403 wrong auth; 400 no target or conflicting targets; 404 unknown `appId` or room. Related: track with `ethora-wait-broadcast-job-v2`.
  • ethora-chats-broadcast-job-v2Fetch the current status and per-room results of a broadcast job by `jobId` (one-shot, no polling). Returns the job object with its `state` (pending/running/completed/failed). Requires: a selected app with at least one room (`ethora-app-create-chat`). Auth: app-token mode OR B2B mode with an explicit `appId` — must match the auth used to enqueue the job. Errors: 401/403 wrong auth; 404 unknown `jobId`. Related: `ethora-wait-broadcast-job-v2` for a blocking wait.
  • ethora-wait-broadcast-job-v2Block until a broadcast job reaches a terminal state (`completed` or `failed`) or until `timeoutMs` — read-only polling wrapper around `ethora-chats-broadcast-job-v2`. Returns `{ done, state, job }`, or `{ done: false, reason: "timeout" }` on timeout. Requires: a `jobId` returned by `ethora-chats-broadcast-job-v2`. Auth: app-token mode OR B2B mode with an explicit `appId` — must match the auth used to enqueue the job. Errors: 401/403 wrong auth; 404 unknown `jobId`.
  • +77 more on 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.

Ethora MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ethora-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@ethora/mcp-server"
      ],
      "env": {
        "ETHORA_API_URL": "YOUR_ETHORA_API_URL_HERE",
        "ETHORA_APP_JWT": "YOUR_ETHORA_APP_JWT_HERE",
        "ETHORA_B2B_TOKEN": "YOUR_ETHORA_B2B_TOKEN_HERE",
        "ETHORA_MCP_AUTH_ISSUER": "YOUR_ETHORA_MCP_AUTH_ISSUER_HERE"
      }
    }
  }
}

Email MCP

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

Frequently asked questions

Ethora MCP Server is categorized under Communication and uses a local stdio subprocess. Email MCP belongs to Communication and uses a local stdio subprocess. Pick Ethora MCP Server 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.

Ethora MCP Server is listed as free. Auth: oauth 2.0. 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 ethora-mcp-server and marlinjai-email-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Ethora MCP Server has a quality signal of 67/100 (Great) with 5 views, 0 installs and 6 GitHub stars. Email MCP has 68/100 (Great) with 8 views, 0 installs and 26 GitHub stars.