Where does the configuration go?
Zed's settings.json, under context_servers.
How do I connect Zed?
- Open Zed's settings.json.
- Add the context_servers entry below. To sign in with OAuth, drop the headers line and approve the connection in the nofeb console when Zed opens it. To use a key, keep the header: Zed's docs do not describe environment-variable expansion for remote headers, so the key is written literally; use a narrowly scoped key.
- Open the agent panel and check that nofeb's tools are available.
// Zed settings.json
{
"context_servers": {
"nofeb": {
"url": "https://api.nofeb.com/mcp",
"headers": { "Authorization": "Bearer <NOFEB_API_KEY>" }
}
}
} Checked against Zed's documentation on . source: zed.dev
What should I know about Zed's setup?
- Zed's documentation does not describe variable expansion for remote headers, so a key sits in settings.json; prefer an inbox-scoped key, or sign in instead.
What can I ask it to do?
Check my nofeb inbox for anything from the payments provider since this morning and list the subjects.
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 Zed.
Frequently asked questions
Why does Zed open a sign-in page for nofeb?
Zed starts OAuth when a remote server has no Authorization header. Sign in to nofeb, choose the organization and optionally one inbox, and approve; or add the header with your key to skip sign-in.
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 |