Skip to content
nofeb

Email for Claude, ChatGPT, Cursor and every MCP client

For people using Claude, ChatGPT, Claude Code, Cursor, VS Code, Windsurf and other MCP clients

nofeb's MCP server is a URL, https://api.nofeb.com/mcp. Clients that support OAuth, such as claude.ai and ChatGPT connectors, discover sign-in from the server, send you to approve the scopes (and optionally one inbox), and connect; clients that send headers can use an API key instead. Either way your assistant gets its own inboxes rather than your mailbox, and every send it attempts goes through the inbox's autonomy tier on the server.

Checked against the engine on .

What gets in the way?

  • Most email MCP servers connect the assistant to your personal mailbox, with all of its history and the power to send as you.
  • Local servers need installing and updating on every machine.
  • Pasting a long-lived key into every client config is how keys leak.

How does nofeb handle it?

Remote, nothing to install

Streamable HTTP at one URL, with the same tools on every client.

Sign in instead of pasting a key

The server answers an unauthenticated client with where to sign in; the client registers itself, you approve the scopes in the nofeb console, and the token it gets is bound to the MCP server, rotates on refresh and can be disconnected at any time.

Its own inboxes

The assistant creates inboxes for the job at hand, with time-to-live inboxes for one-off tasks, and never sees your personal mail.

Tools named for the job

wait_for_email, get_thread_context, search_email, set_thread_state and find_availability do in one call what would otherwise take several.

The same rules as the API

Tools are generated from the API's operation table and dispatched through the same router, and the official TypeScript and Python MCP clients and the MCP inspector exercise the server in CI on every change.

What does the code look like?

Connect any MCP client that supports remote servers
{
  "mcpServers": {
    "nofeb": {
      "url": "https://api.nofeb.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_NOFEB_API_KEY" }
    }
  }
}
The same as MCP tool calls
create_inbox    { "local_part": "signup-bot", "ttl_seconds": 3600 }
wait_for_email  { "inbox_id": "inb_…", "has_otp": true, "timeout": 60 }
→ { "message": { "otps": [{ "code": "482913", "source": "body" }], "links": [ … ], … } }

Where does nofeb stop?

  • The assistant acts in nofeb inboxes; it does not read or send from your existing Gmail or Outlook mailbox.

Frequently asked questions

What is the best email MCP server for Claude or Cursor?

One that gives the assistant its own inbox rather than yours, runs remotely, and enforces a sending policy on the server. nofeb's tools cover inboxes, waiting for codes, search, threads, replies, approvals and the calendar.

Can I add nofeb to ChatGPT or claude.ai?

Yes. Add https://api.nofeb.com/mcp as a custom connector; the client finds nofeb's OAuth sign-in, registers itself, and sends you to the console to approve the scopes. The integration pages walk through each client.

Can Claude Code send emails?

With nofeb connected, yes, through send_message and reply_to_message, subject to the inbox's autonomy tier.

Is there a remote email MCP server I do not have to install?

Yes: nofeb is a URL, with OAuth sign-in or an API key.

Status of everything on this page

Every capability named above, with its status as reconciled against the engine.

CapabilityWhat it doesStatus
MCP server A remote MCP server over streamable HTTP whose tools are generated from the same operation table as the REST API and dispatched through the same router, so a tool cannot behave differently from its endpoint. Shipped
MCP sign-in with OAuth MCP clients connect by signing in instead of pasting a key: OAuth 2.1 with discovery, dynamic client registration, client ID metadata documents, PKCE, tokens bound to the MCP server, refresh-token rotation and immediate revocation. A person approves the scopes, and optionally one inbox, in the console, and can disconnect the app at any time. API keys keep working beside it. Shipped
MCP client conformance suite The official TypeScript and Python MCP SDK clients and the MCP inspector drive the server in CI on every change: initialization, tool listing, tool calls, error mapping and the full OAuth sign-in flow. Shipped
Scoped API keys Keys bound to the organization, one pod or one inbox, holding only the scopes they are given. A key cannot mint a key wider than itself. Shipped
Disposable inboxes with a time to live Give an inbox a lifetime in seconds; it and its mail are removed when it expires, and an event says so. Shipped
Wait for an email Long-poll an inbox for up to a minute until a message matching sender, subject or has-a-code arrives. Shipped
LLM-ready thread context A whole thread, oldest first, with safe_body text and the thread's metadata, in one call. Shipped
Search that understands Full-text and semantic search over subjects, addresses, the new text of each message, attachment names and attachment text, across every inbox a key can see. Filter by inbox, pod, folder, thread, sender, recipient, date, attachments, keywords, authentication failures and metadata; results carry highlighted snippets and can be grouped by thread. Shipped
Calendar per inbox A calendar on every inbox: events with recurrence and time zones, invitations, updates, cancellations and replies by email, auto-accept rules, free/busy, availability and booking that sends the invitations, MCP tools for scheduling, and CalDAV and JMAP Calendars for standard clients. Invitations an agent sends follow its inbox's autonomy tier. Shipped
Autonomy tiers enforced by the server Every inbox carries a sending policy, from read-only to autonomous, enforced on the server for every surface that sends, so switching from the API to MCP cannot bypass it. Shipped