Skip to content

Overview

Surfing Dog Inbox is an open-source, self-hostable typed inbox for a business. It receives bookings, orders, quote requests and messages from people and from AI agents, through REST, MCP and email, and turns each one into a typed item with a lifecycle that rules, the owner, or the owner’s own AI can handle. It is fully functional with zero AI.

One codebase runs on Cloudflare Workers and on Node. One SQLite database holds everything the business owns. One discovery manifest at /.well-known/agent-inbox.json tells an agent where the REST, OpenAPI and MCP doors are.

Written on 21 September 2026. The self-hostable inbox is under way and this page says what actually runs. Working today, on both runtimes:

  • the core write path: typed items, five state machines, append-only events, idempotency keys and compare-and-set versions;
  • the rules engine, with presets for appointments, trades and shops;
  • REST with an OpenAPI document, a public MCP server and an owner MCP server;
  • owner API keys, owner sign-in by magic link, and an OAuth 2.1 authorization server for the owner MCP;
  • the owner app, first version: sign in by emailed link or owner key, a three-pane inbox, a typed item view with the valid next actions as buttons, and settings;
  • the email door: inbound MIME parsed, deduplicated and threaded onto the right item;
  • the job runner for notifications and rules, on cron and queues on Workers and on a loop on Node;
  • network membership: an instance reports to one or more networks, switched on in settings, with counts-only telemetry every hour and the receipts it issues;
  • our own live instance at inbox.surfingdog.ai and the network at network.surfingdog.ai.

Still to come: passkeys and a web form door (being built), connectors (coming), hosted tenancy, and the network’s reviews and reputation (coming). Every page in these docs says whether a feature is live.

  • Quickstart: deploy to Cloudflare, run on your own server, or join the hosted waitlist, then make your first calls.
  • Concepts: items and their states, rules, agent policy and trust tiers, receipts and two-sided reviews.
  • Connect your AI: let Claude, ChatGPT or any MCP client work your inbox through the owner MCP.
  • API: every public and owner operation, and the conventions they share.
  • Manifest: the discovery document an instance publishes.
  • Self-hosted vs hosted: an honest comparison.
  • Security and privacy: what leaves the instance, and what never does.
  • Contributing: licences, the toolchain and the rules of the repo.

The source is at github.com/surfingdogai/inbox; the plan and the architecture decision records live in its docs/ folder.