What is dev.postbag/mcp?

Form backend that routes: one tool per Postbag API operation, plus quickstart and explain.

How do I install dev.postbag/mcp?

Install dev.postbag/mcp via npm from https://registry.npmjs.org, then add the server config to your MCP client (Claude Desktop, Cursor, or VS Code).

Is dev.postbag/mcp open source?

Yes, dev.postbag/mcp is open source under the AGPL-3.0 license. Source code is available at https://github.com/faahim/postbag.

What category does dev.postbag/mcp belong to?

dev.postbag/mcp is listed under Other MCP servers on MCPFind.

dev.postbag/mcp — MCP Server for Other

Postbag

A form backend that routes. Point any HTML form at a Postbag endpoint and it lands in your inbox — then goes wherever it should: email, Telegram, a webhook, a partner, your CRM. Built for people who run many sites, and for the AI agents that build them.

<form action="https://api.postbag.dev/s/fm_8f3kq2" method="POST">
  <input name="email" type="email" required>
  <textarea name="message"></textarea>
  <button>Send</button>
</form>

That's the whole integration for one form. Everything else — grouping forty forms into one stream, mapping their different fields onto one shape, sending that shape to a partner between two dates, a daily digest, never losing a submission — is there when you need it and invisible when you don't.

New here (human or AI agent)? Read CLAUDE.md first.

Why it exists

Every website has forms. Every form needs somewhere to go. Formspree and friends solve "somewhere" for one site; they fall over when you have fifteen sites feeding one partner with fifteen slightly different forms. Postbag is the source of truth for what each form collects, what each downstream system receives, and the versioned contract between them.

The one idea

The database makes it correct; events make it fast.

A submission is accepted the instant it is a row. Delivery is a durable outbox that a worker drains with retries. Realtime nudges are an accelerator, never a transport. If every event stream in the system died, every submission would still arrive — late, never lost. (Inherited from the lead pipeline this generalises; see docs/ARCHITECTURE.md.)

Status

Phase 1 — MVP live at postbag.dev (site, docs, dashboard at /app, API at /v1). See PROGRESS.md for the live blueprint and docs/ROADMAP.md for phases.

Documentation

Start at docs/README.md.

License

The server, dashboard, site and domain packages (apps/*, packages/core, packages/db, packages/auth) are licensed under AGPL-3.0. The client packages that run inside your own code — @postbag/sdk, the postbag CLI and @postbag/mcp — are MIT. Rationale in ADR-006.

Set up in your AI client

AI clientOperating system

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json

{
  "mcpServers": {
    "dev-postbag-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@postbag/mcp"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Compatible MCP Clients

dev.postbag/mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.

Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.

VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.

Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.

Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

dev.postbag/mcp