Where does the configuration go?
A custom connector under Customize > Connectors (on Team and Enterprise, added by an Owner in Organization settings > Connectors), signed in to nofeb with OAuth. No API key is pasted anywhere.
How do I connect Claude Desktop and claude.ai?
- On Free, Pro or Max: open Customize > Connectors and click Add custom connector. On Team or Enterprise, an Owner opens Organization settings > Connectors, selects Add, then Custom, then Web.
- Enter https://api.nofeb.com/mcp as the MCP server URL. Leave the OAuth client ID and secret empty.
- If the dialog asks: choose Sign in now (or Sign in when needed) for Authentication, and Use Claude's published identity for the OAuth client. Register automatically also works, because nofeb supports dynamic client registration.
- Click Connect. In the nofeb console, sign in, pick the organization and, if you want the connector confined to it, one inbox, then approve the scopes. Team and Enterprise members each click Connect with their own nofeb account.
- Ask Claude to list your nofeb inboxes to check the connection.
# claude.ai or Claude Desktop: Customize > Connectors > Add custom connector
# (Team/Enterprise Owner: Organization settings > Connectors > Add > Custom > Web)
# MCP server URL: https://api.nofeb.com/mcp
# Authentication: Sign in now
# OAuth client: Use Claude's published identity (or: Register automatically)
# Then click Connect and approve in the nofeb console.
#
# What Claude discovers from nofeb (no configuration needed):
# POST https://api.nofeb.com/mcp -> 401, WWW-Authenticate: Bearer resource_metadata="…"
# GET /.well-known/oauth-protected-resource/mcp -> resource https://api.nofeb.com/mcp, its authorization server
# GET /.well-known/oauth-authorization-server -> /oauth/authorize, /oauth/token, /oauth/register, /oauth/revoke
#
# Alternative with an API key instead of sign-in, in Claude Desktop only:
# a local stdio bridge in claude_desktop_config.json (pattern from the mcp-remote README)
{
"mcpServers": {
"nofeb": {
"command": "npx",
"args": [
"mcp-remote",
"https://api.nofeb.com/mcp",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer <NOFEB_API_KEY>"
}
}
}
} Checked against Claude Desktop and claude.ai's documentation on . source: claude.com
What should I know about Claude Desktop and claude.ai's setup?
- Your role in the nofeb organization caps what you can approve. Admins and owners can grant the full agent scopes, including sending. A member can grant a third-party app read access to inboxes, metadata and calendars only, so a member's connector can look things up but not read or send mail.
- Sending still follows the inbox's autonomy tier. A token cannot approve a held send unless the person who connected granted send:approve, and when a tool needs a scope the token lacks, nofeb answers 403 insufficient_scope naming it, so Claude can ask you to approve more.
- Refresh tokens rotate on every use, and a reused one revokes the whole grant. To disconnect, remove the connector in Claude, or disconnect the app from the connected-apps list in the nofeb console (
DELETE /v1/oauth/grants/{grant_id}); its tokens stop working on the next request. - Connector authentication cannot be edited after the connector is added; remove it and add it again to change it. If your organization has the Request headers option, an API key sent as
authorizationwith No sign-in also works, but it is shared by everyone who uses the connector.
What can I ask it to do?
Make me a throwaway inbox that expires in an hour and tell me its address. When an email arrives there, summarise it.
117 tools are available, including create_inbox, wait_for_email, reply_to_message, get_thread_context, set_thread_state and get_dns_setup. Whether a send goes out at once or waits for a person is decided by the inbox's autonomy tier on the server, not by Claude Desktop and claude.ai.
Frequently asked questions
Do I need an API key to connect claude.ai to nofeb?
No. The connector signs in with OAuth, and each person who connects gets a token for their own nofeb account, scoped to what they approved and, optionally, to one inbox. API keys remain for the mcp-remote bridge and for code.
Which OAuth client option should I pick?
Use Claude's published identity, which Claude's documentation recommends: nofeb reads Claude's client details from the client ID metadata document Anthropic hosts. Register automatically uses dynamic client registration, which nofeb also supports. You do not need your own OAuth client.
Does the mcp-remote bridge work on claude.ai or mobile?
No. It runs as a local process, so it works only in the Claude Desktop app. The OAuth custom connector is the route for claude.ai.
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 |
| TypeScript and Python SDKs | Official clients generated from the OpenAPI document: @nofeb/sdk for Node, Deno, Bun and edge runtimes, and nofeb for Python with sync and asyncio clients. Both chain long polls for waitForEmail, retry idempotent requests, page through lists and verify webhook signatures. | 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 |