Where does the configuration go?
cline_mcp_settings.json in the IDE (MCP Servers → Configure), or ~/.cline/mcp.json for the CLI.
How do I connect Cline?
- Open the MCP Servers panel in Cline and choose Configure MCP Servers.
- Add the entry below with your nofeb key, keeping "type": "streamableHttp".
- Save; Cline lists nofeb's tools when it connects.
// cline_mcp_settings.json (IDE: MCP Servers icon > Configure > "Configure MCP Servers"; CLI: ~/.cline/mcp.json)
{
"mcpServers": {
"nofeb": {
"type": "streamableHttp",
"url": "https://api.nofeb.com/mcp",
"headers": {
"Authorization": "Bearer <NOFEB_API_KEY>"
},
"disabled": false,
"autoApprove": []
}
}
} Checked against Cline's documentation on . source: docs.cline.bot
What should I know about Cline's setup?
- type must be exactly streamableHttp, in that case.
- Cline's documentation does not describe variable expansion for remote headers; use an inbox-scoped key.
What can I ask it to do?
Wait up to a minute for an email with a code in my nofeb test inbox and tell me the code.
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 Cline.
Frequently asked questions
Why does Cline fail to connect to nofeb?
Most often the type is missing or misspelled, so Cline tries SSE. Use "streamableHttp" exactly.
Should I add tools to autoApprove?
Only read-only ones such as list_messages or get_thread_context. Sends are already governed by the inbox's autonomy tier on the server.
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 |