Where does the configuration go?
~/.config/goose/config.yaml, or interactively with goose configure.
How do I connect Goose?
- Run goose configure and choose Add Extension → Remote Extension (Streamable HTTP).
- Enter https://api.nofeb.com/mcp and add the Authorization header with your key.
- Or edit config.yaml directly as below. Goose's own example shows an empty headers map; put the Authorization entry in it.
# ~/.config/goose/config.yaml (Windows: %APPDATA%\goose\config.yaml)
extensions:
nofeb:
type: streamable_http
name: nofeb
enabled: true
uri: "https://api.nofeb.com/mcp"
headers:
Authorization: "Bearer <NOFEB_API_KEY>"
env_keys: []
envs: {}
timeout: 300 Checked against Goose's documentation on . source: goose-docs.ai
What should I know about Goose's setup?
- Goose uses uri (not url) and type streamable_http, with an underscore.
- Goose's documentation moved to goose-docs.ai.
What can I ask it to do?
Create a nofeb inbox for the vendor onboarding run and keep checking it until the welcome email 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 Goose.
Frequently asked questions
Can I add nofeb for one session only?
goose session --with-streamable-http-extension takes the URL, but its documented form takes no headers, so use the configured extension for an authenticated 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 |