openagent.email MCP Server — Claude, Cursor, and Agents

Use this page to pick the MCP path you already have docs for. It does not replace the client, public-ingress, or REST references.

Three existing routes

• Local stdio. Agents on the same machine run@openagentemail/mcp as a stdio process. Copy-paste configs are inMCP client setup.
• Self-hosted remote HTTP/OAuth. Cloud agents can callPOST /mcp on your own origin. Public ingress is inExposing MCP publicly; the HTTP client shape is in MCP client setup.
• Hosted connector. Web chat products connect to the hosted MCP URL over OAuth. Tested connection paths for Claude, ChatGPT, Grok, and related clients are in Connect your agent (naming clients indicates tested compatibility, not vendor endorsement).

Docs this hub points to

• Quickstart
• Connect your agent
• MCP client setup
• Agent tasks
• Exposing MCP publicly
• REST API
• OTP extraction

openagent.email can be self-hosted; MailSlurp's MCP is hosted SaaS. Seeopenagent.email vs MailSlurp.

How do I connect Claude Desktop or Cursor?

Follow Connect your agent and paste the matching config from MCP client setup. Claude Desktop and Cursor connect to MCP over local stdio or remote HTTP with your scoped token or OAuth.

Do I need a public MCP URL?

Only when a cloud or web agent must reach your server. Local stdio stays on the same machine. Public HTTP/OAuth ingress is covered inExposing MCP publicly.

Can I use REST instead of MCP?

Yes. The REST API exposes the same mailbox and task endpoints, including the wait/read flow in the OTP extraction guide and task threads in the Tasks guide.