Where does the configuration go?
~/.cursor/mcp.json for every project, or .cursor/mcp.json in one project.
How do I connect Cursor?
- Create a nofeb API key and export it as NOFEB_API_KEY.
- Add the entry below to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project). Remote entries take url and headers, with no type field.
- Open Cursor's MCP settings and check that nofeb is connected with its tools listed.
// ~/.cursor/mcp.json (global) or .cursor/mcp.json (project)
{
"mcpServers": {
"nofeb": {
"url": "https://api.nofeb.com/mcp",
"headers": {
"Authorization": "Bearer ${env:NOFEB_API_KEY}"
}
}
}
} Checked against Cursor's documentation on . source: cursor.com
What should I know about Cursor's setup?
- Remote entries take url and headers and no type field.
- Cursor interpolates ${env:NAME}, ${userHome} and ${workspaceFolder} in configuration values.
- Cursor's documentation says it supports OAuth for servers that require it. Leave out the headers block and Cursor can sign in to nofeb instead of sending a key; nofeb supports dynamic client registration, so no static client ID is needed.
What can I ask it to do?
Write a Playwright test for our sign-up page that uses a nofeb inbox, then run the flow once against staging and confirm the code arrives.
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 Cursor.
Frequently asked questions
Why does Cursor not see NOFEB_API_KEY?
Cursor resolves ${env:…} from its own process environment. Launch it from a shell that exports the key, or set the variable where your OS passes it to desktop apps.
Can I restrict which inbox Cursor can use?
Yes. Use a key bound to one inbox; nofeb refuses any call outside it.
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 |