Form backend that routes: one tool per Postbag API operation, plus quickstart and explain.
MCPpedia last refreshed this data
dev.postbag/mcp is an MCP server that form backend that routes: one tool per Postbag API operation, plus quickstart and explain. Its tool list has not been published yet over stdio, requires no API key, and scores 83/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"dev-postbag-mcp": {
"command": "npx",
"args": [
"-y",
"@postbag/mcp"
]
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Form backend that routes: one tool per Postbag API operation, plus quickstart and explain.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@postbag/mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @postbag/mcp against OSV.dev.
Click any tool to inspect its schema.
This server is missing a description.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in data
Manage Supabase projects — databases, auth, storage, and edge functions
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
DataForSEO API modelcontextprotocol server
The Apify MCP server enables your AI agents to extract data from social media, search engines, maps, e-commerce sites, or any other website using thousands of ready-made scrapers, crawlers, and automation tools available on the Apify Store.
MCP Security Weekly
Get CVE alerts and security updates for dev.postbag/mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.mdfirst.
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 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.)
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.
Start at docs/README.md.
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.