Skip to content
nofeb

nofeb in Claude Code

MCP client · configuration checked against the vendor's documentation on 2026-10-02

Run claude mcp add --transport http nofeb https://api.nofeb.com/mcp and sign in from /mcp with OAuth, or add an Authorization: Bearer header carrying a nofeb API key, or commit a .mcp.json that reads the key from NOFEB_API_KEY. Claude Code then lists nofeb's tools, and the model can create inboxes, wait for codes, read threads and reply.

Checked against the engine on .

Where does the configuration go?

One CLI command, or a project-scoped .mcp.json committed with the repository.

How do I connect Claude Code?

  1. To sign in instead of using a key: add the server without a header, run /mcp, choose nofeb and finish the sign-in in your browser (or run claude mcp login nofeb in a shell). In the nofeb console, pick the organization, optionally one inbox, and approve the scopes.
  2. To use a key: create a nofeb API key, ideally bound to one inbox, and export it as NOFEB_API_KEY in the shell Claude Code runs from.
  3. Add the server with the CLI, or commit the .mcp.json form so the key stays out of the file.
  4. Run /mcp in Claude Code to confirm nofeb is connected and its tools are listed.
Claude Code: shell / JSON
# OAuth sign-in (no key): add the server, then authenticate from /mcp or the shell
claude mcp add --transport http nofeb https://api.nofeb.com/mcp
claude mcp login nofeb

# API key instead (add --scope user to make it available in every project; default scope is local)
claude mcp add --transport http nofeb https://api.nofeb.com/mcp \
  --header "Authorization: Bearer $NOFEB_API_KEY"

# or commit a project-scoped .mcp.json (key stays in the env, expanded at load time):
{
  "mcpServers": {
    "nofeb": {
      "type": "http",
      "url": "https://api.nofeb.com/mcp",
      "headers": {
        "Authorization": "Bearer ${NOFEB_API_KEY}"
      }
    }
  }
}

Checked against Claude Code's documentation on . source: code.claude.com

What should I know about Claude Code's setup?

  • Scopes: --scope user makes nofeb available in every project; the default is the current project only.
  • Claude Code expands ${VAR} and ${VAR:-default} in .mcp.json URLs and headers.
  • With OAuth, Claude Code discovers nofeb's protected resource and authorization server metadata, registers itself (nofeb supports both dynamic registration and client ID metadata documents), stores the token and refreshes it; nofeb rotates the refresh token each time. Clear authentication in /mcp, or claude mcp logout nofeb, removes it.

What can I ask it to do?

Create a nofeb inbox for this branch's sign-up test, register with it on the local dev server, and paste the verification code you receive into the terminal output.

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 Code.

Frequently asked questions

Should I use OAuth or an API key in Claude Code?

OAuth for your own interactive use: nothing secret sits in a file, and the grant shows up in the nofeb console's connected apps, where it can be disconnected. An API key suits a committed .mcp.json shared by a team or a CI job, where nobody is there to sign in.

Where does Claude Code store the nofeb key?

With the CLI form your shell expands $NOFEB_API_KEY when you run the command, so the key is saved in Claude Code's config. The .mcp.json form keeps ${NOFEB_API_KEY} as a reference that is expanded when the file is loaded.

Can I share the nofeb server with my team?

Commit .mcp.json with the ${NOFEB_API_KEY} reference and have each developer set their own key, ideally one bound to their own inbox.

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
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