Where does the configuration go?
.vscode/mcp.json in the workspace, or the user profile through "MCP: Open User Configuration".
How do I connect VS Code (GitHub Copilot)?
- Create .vscode/mcp.json with the inputs and servers blocks below. The top-level key is servers, not mcpServers.
- Start the server from the editor; VS Code prompts for the nofeb key and stores it.
- In Copilot Chat, switch to agent mode and check that nofeb's tools appear in the tools picker.
// .vscode/mcp.json (workspace) - or "MCP: Open User Configuration" for the user profile
{
"inputs": [
{
"type": "promptString",
"id": "nofeb-api-key",
"description": "nofeb API key",
"password": true
}
],
"servers": {
"nofeb": {
"type": "http",
"url": "https://api.nofeb.com/mcp",
"headers": {
"Authorization": "Bearer ${input:nofeb-api-key}"
}
}
}
} Checked against VS Code (GitHub Copilot)'s documentation on . source: code.visualstudio.com
What should I know about VS Code (GitHub Copilot)'s setup?
- Use inputs with password: true so the key is prompted once and kept out of the file.
- A portable .mcp.json format is also documented for Copilot.
What can I ask it to do?
Use nofeb to create an inbox for the integration test fixtures and add its address to tests/fixtures/env.json.
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 VS Code (GitHub Copilot).
Frequently asked questions
Can I read the key from an environment variable instead?
Yes: "Bearer ${env:NOFEB_API_KEY}" also works in headers.
Can an organization block MCP servers?
Copilot Business and Enterprise administrators can turn MCP off by policy; check with yours if the server does not start.
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 |