Skip to content
nofeb

Integrations

Where nofeb plugs in

nofeb meets agents where they already run: any MCP client that can sign in with OAuth or send a header, any framework with an MCP adapter, the TypeScript and Python SDKs, and the mail and DNS providers your domain already uses. Every entry carries its status.

MCP clients

Exact configuration for each client, checked against its own documentation.

Agent frameworks

Through each framework's MCP adapter; no nofeb-specific package to install.

Mail and DNS providers

Inbound from Cloudflare Email Routing, Postmark, Mailgun, SendGrid or a raw POST, and DNS records set up for your DNS host.

APIs, events and inbound

Standard interfaces, so anything that speaks them can use nofeb without a dedicated package.

  • Remote MCP clients Shipped

    Any MCP client that supports remote servers over streamable HTTP, signed in with OAuth or authenticated with a nofeb API key as a bearer token.

  • Any HTTP client Shipped

    REST described by a published OpenAPI document, so generated clients and API tools work from the spec.

  • Webhook receivers Shipped

    Any HTTPS endpoint that can verify a Standard Webhooks signature, or pull the event feed instead.

  • Live clients over WebSocket Shipped

    Dashboards and browser apps that follow events as they happen, resuming from a cursor after a disconnect without a gap or a duplicate.

  • Your DNS host Shipped

    Records published through the Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun or Gandi API with a token used once, and instructions, a zone file, a Route 53 change batch and Terraform for every other host.

  • Cloudflare Email Routing Shipped

    Keep Cloudflare routing your domain's mail and pass it to nofeb with an Email Worker on your own zone.

  • Postmark, Mailgun and SendGrid inbound Shipped

    Point a Postmark inbound stream, a Mailgun route or SendGrid Inbound Parse at nofeb, authenticated by your rotatable inbound token.

  • Any mail server Shipped

    Point a domain's MX at nofeb and any server on the internet can deliver to your inboxes, with sender authentication and spam and virus checks before acceptance.

  • Your HTTPS services as hooks Shipped

    Signed callouts at inbound.resolve, inbound.pre_deliver and outbound.pre_send, so your own code can decide what happens to a message or a send.

  • Your code as WebAssembly hooks Shipped

    The same three stages as a module you upload, built against a published interface, run sandboxed inside the pipeline with no endpoint of yours to keep up.

  • Anything that produces MIME Shipped

    Push raw RFC 5322 messages into an inbox: imports, migrations and generic inbound webhooks.

Agent frameworks

Clients and sign-in for the agent stack you already use.

  • TypeScript and Python SDKs Shipped

    @nofeb/sdk and the nofeb Python package, generated from the OpenAPI document, with long-poll chaining, retries, pagination and webhook verification.

  • MCP sign-in Shipped

    OAuth 2.1 with client ID metadata documents and dynamic client registration, so claude.ai, ChatGPT and other MCP clients sign in instead of holding a key, and each grant can be disconnected from the console.

  • Cloud and CI workload identity Shipped

    Agents in Microsoft Entra ID (including Entra Agent ID), Google Cloud, Amazon EKS or GitHub Actions, or behind any OIDC issuer, exchange the token their platform issues for a short-lived nofeb token, so no API key is stored with the agent.

  • MCP client testing Shipped

    The official TypeScript and Python MCP SDK clients and the MCP inspector run against the server in CI on every change, including the full OAuth flow, so tool output stays compatible.

People and approvals

For the people who share mailboxes with agents and approve what they send.

  • Approvals in Slack Shipped

    Approve or reject a held send from a Slack message with Approve and Reject buttons, verified with your Slack app's signing secret.

  • Approvals by email link Shipped

    A signed, single-use, expiring link that decides only when the approver clicks, so link scanners cannot approve.

  • The nofeb webmail Shipped

    Mail and calendar on the same inboxes, with the approval queue, the agent-activity timeline and a per-thread driver lock.

  • Your identity provider Shipped

    Single sign-on to the console and webmail through Google Workspace, Microsoft Entra ID, Okta, any OIDC issuer or SAML 2.0, with SCIM 2.0 provisioning.

Standard mail protocols

So people, existing clients and legacy tools can use the same mailboxes.

  • JMAP clients Shipped

    JMAP Mail, submission and push, one account per inbox; the webmail is built on it.

  • IMAP and POP3 clients Shipped

    Desktop and mobile mail apps, and tools that read over IMAP, signed in with an inbox address and a per-inbox app password.

  • SMTP submission Shipped

    Software that can only send over SMTP, on ports 587 and 465, under the same autonomy tiers, approvals and caps as the API.

  • Calendar clients Shipped

    CalDAV and JMAP Calendars, with invitations and replies by email.

  • Archives and other mail systems Shipped

    Export an inbox, a folder, a thread or a search as mbox or EML, with its metadata as JSON.

Your sending and DNS accounts

Integrations that depend on a counterparty account, each with its status.

  • Bring your own Amazon SES Beta

    Send through your own AWS account by granting nofeb an IAM role.

  • Domain Connect DNS hosts Beta

    A signed one-click link at DNS hosts that support Domain Connect, once the host has adopted nofeb's template.