Skip to content
nofeb

nofeb in Windsurf (Cascade)

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

Add nofeb to Cascade's mcp_config.json with "serverUrl": "https://api.nofeb.com/mcp" and an Authorization header that reads ${env:NOFEB_API_KEY}. Cascade connects over streamable HTTP and can create inboxes, wait for codes and reply.

Checked against the engine on .

Where does the configuration go?

Cascade's raw MCP configuration file; current docs place it at ~/.config/devin/mcp_config.json.

How do I connect Windsurf (Cascade)?

  1. Export NOFEB_API_KEY.
  2. Open Cascade's MCP settings and edit the raw configuration. The current docs, now published under the Devin Desktop name, give ~/.config/devin/mcp_config.json (macOS and Linux) and %APPDATA%\devin\mcp_config.json (Windows); older installs may use a different path, so open it from the settings.
  3. Add the entry below and refresh the server list.
Windsurf (Cascade): JSON
// ~/.config/devin/mcp_config.json (macOS/Linux) or %APPDATA%\devin\mcp_config.json (Windows)
{
  "mcpServers": {
    "nofeb": {
      "serverUrl": "https://api.nofeb.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:NOFEB_API_KEY}"
      }
    }
  }
}

Checked against Windsurf (Cascade)'s documentation on . source: docs.devin.ai

What should I know about Windsurf (Cascade)'s setup?

  • Remote entries use serverUrl; the docs say url also works.
  • Values can come from ${env:VAR_NAME} or ${file:/path}.

What can I ask it to do?

Create an inbox called release-notes and write a reply to the latest message in it and show it to me before sending.

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 Windsurf (Cascade).

Frequently asked questions

Why is nofeb blocked in my team's Windsurf?

Team admins can restrict Cascade to an approved set of MCP servers; once any server is approved that way, every other server is blocked. Ask an admin to add nofeb.

Can I keep the key in a file?

Yes: Cascade also expands ${file:/path/to/file} in configuration values.

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