mcpbeat Sign in

Email-Ops MCP Server

answering

Email-Ops is answering right now. Last checked 12 min ago.

Mailbox threads; drafts wait for a person. Authenticated; OAuth 2.1 via Keycloak.

Uptime history 23 hours of history
23 hours agonow
100.0%
Uptime 24h
82 of 82 checks
—
Tools
hidden behind auth
660 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Email-Ops every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add email-ops --transport http https://email-ops.unicorncommander.ai/api/v1/mcp
Settings → Connectors → Add custom connector, then paste this address
https://email-ops.unicorncommander.ai/api/v1/mcp
~/.codex/config.toml
[mcp_servers.email-ops]
url = "https://email-ops.unicorncommander.ai/api/v1/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "email-ops": {
      "url": "https://email-ops.unicorncommander.ai/api/v1/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "email-ops": {
      "type": "http",
      "url": "https://email-ops.unicorncommander.ai/api/v1/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://email-ops.unicorncommander.ai/api/v1/mcp streamable-http sign-in 620 ms 12 min ago

Alternatives to Email-Ops

same job, measured the same way
Innmail for Agents
by innmail

Email inbox for an AI agent: threads, send, reply, drafts, verification codes, calendar.

answering
GrabMail disposable email
by grabmail

Disposable email for agents: create an inbox, wait for the message, read the code. No key needed.

6 tools answering
Openagentemail
by openagentemail

Unlimited agent mailboxes — create identities, read/wait for mail, extract OTPs, send email.

66 installs/wk local only
Shaka
by shaka

Company email for Rwanda. Read and send mail from a Shaka mailbox over OAuth or an API key.

answering
e2a — email for AI agents
by mnexa-ai

Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.

50 installs/wk answering
e2a — email for AI agents
by e2a

Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.

answering
Deskhand
by grain64-deskhand

Deskhand CRM for AI agents: key per agent, undo a run, email drafts. Start with one POST.

30 tools answering
smbCloud Mail & Auth
by smbcloudxyz

Email infrastructure and authentication for developers: domains, inbox routes, auth apps, deploys.

760 installs/wk answering

Email-Ops — questions

Answers built from our own checks of this server.

Why is there no tool list for Email-Ops?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Email-Ops working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 82 of 82 checks got a reply (100.0%), average response time 660 ms. The bar chart above shows every period we have measured.
How do I connect Email-Ops?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Email-Ops?
No API key is involved. Email-Ops answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Email-Ops?
It answers our handshake in 660 ms on average, which is faster than 14% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.