Form backend that routes: one tool per Postbag API operation, plus quickstart and explain.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent โ or use 1-click editor setup below.
Manual Client & Custom JSON ConfigExpand JSON โพ
Client Config & Setup
Choose your client or environment
Target File:
๐ก Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Documentation Overview
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.
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.mdfirst.
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.
Related MCP Servers
Reviews
No reviews yet โ be the first to share how this listing worked for you.
Frequently Asked Questions about Postbag
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/mcp-244)HTML Embed
<a href="https://allmcps.com/mcp/mcp-244"><img src="https://allmcps.com/api/badge/mcp-244?style=directory" alt="Postbag on AllMCPs" /></a>Technical Specs & Signals
CategoryDeveloper Tools
27Quality signal: Emerging ยท 27/100How this signal is calculated โพ
Server availabilityNot measured
Not scored for repo-hosted servers โ we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership8/20
Documentation & tools11/30
Adoption & activity1/15
Community engagement0/10
A guidance signal from public completeness & health data โ not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge โ proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it โ no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.