What do you need?
- A nofeb API key (an agent can sign itself up to get one)
- An MCP client that supports remote servers with headers
Steps
-
1. Create a narrow key
For a coding agent, bind a key to a single inbox with only the scopes it needs. The inbox's autonomy tier still applies to every tool call.
An inbox-scoped key curl -X POST https://api.nofeb.com/v1/keys -H "Authorization: Bearer $NOFEB_ORG_KEY" -H 'content-type: application/json' \ -d '{"inbox_id": "inb_…", "scopes": ["inbox:read", "message:read", "message:send", "metadata:write"], "label": "claude-code"}' -
2. Add the server to Claude Code
One command; the header carries the key.
Claude Code claude mcp add --transport http nofeb https://api.nofeb.com/mcp \ --header "Authorization: Bearer $NOFEB_API_KEY" -
3. Or to Cursor
Cursor reads remote servers from mcp.json with url and headers.
~/.cursor/mcp.json { "mcpServers": { "nofeb": { "url": "https://api.nofeb.com/mcp", "headers": { "Authorization": "Bearer ${env:NOFEB_API_KEY}" } } } } -
4. Ask for something
Try: "Create an inbox for the staging sign-up test, register with it at the staging URL, and tell me the verification code." The model calls create_inbox, then wait_for_email with has_otp, and reads the code from the result.
What about clients that sign in instead of taking a key?
ChatGPT custom connectors and claude.ai connectors expect OAuth rather than a static key. Give them only the URL. A request without a credential gets a 401 whose WWW-Authenticate header points at /.well-known/oauth-protected-resource/mcp; from there the client finds the authorization server, registers itself and opens a sign-in page.
You sign in at the nofeb console, pick the organization and, if you like, a single inbox, and approve the scopes the client asked for (members can grant only read scopes to third-party apps). The client receives a token bound to the MCP server alone; refresh tokens rotate, a reused one revokes the grant, and you can disconnect the app from the list of connected apps at any time.
The Claude Desktop app can also reach the server with a key through the mcp-remote bridge; the per-client pages give exact configuration.
Frequently asked questions
Can Claude Code send email?
With nofeb connected, yes: send_message, reply_to_message and forward_message are tools. Whether a send goes out at once or waits for a person depends on the inbox's autonomy tier, enforced on the server.
Which MCP tools does nofeb expose?
Inboxes, messages and drafts, wait_for_email, search, threads and their metadata, sends and the approval queue, quarantine and safety reports, calendars and scheduling, policy lists and rules, events, webhooks, domains with DNS setup, and hooks. The Agents and MCP page lists every tool.
Does OAuth replace API keys?
No. Both work on the same server. A key suits a coding agent or CI job you configure once; OAuth suits a person connecting an assistant, because nobody copies a secret and the grant can be revoked from the console.
Is the MCP server different from the REST API?
No. Tools are generated from the same operation table and dispatched through the same router, so a tool validates, authorizes and fails exactly like its endpoint.
Status of everything on this page
Every capability named above, with its status as reconciled against the engine.
| Capability | What it does | Status |
|---|---|---|
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |