
Postbag
dev.postbag由 postbag.dev 发布v0.1.1更新于 Oct 24, 2026
Form backend that routes: one tool per Postbag API operation, plus quickstart and explain.
概览
Postbag 的本地 MCP 服务器封装其表单后端 API,让助手管理表单端点、提交数据以及到邮件、Webhook 或 CRM 的路由。
- 可以做什么
- 通过每个 Postbag API 操作对应一个工具来管理表单端点及其提交数据
- 将表单数据路由到邮件、Telegram、Webhook、合作伙伴或 CRM 等目标
- 把多个表单归并为一个数据流,并将不同字段映射为统一结构
- 由助手提供快速上手说明和 Postbag 概念解释
- 适用场景
- 适合在搭建或维护带 HTML 表单的网站时使用,让助手在对话中配置端点、查看提交记录或设置路由与每日摘要。
- 运行要求
- 通过 npx 从 npm 包 @postbag/mcp 以 stdio 在本地运行,需要 Node.js。需要在环境变量 POSTBAG_API_KEY 中提供 Postbag API 密钥(正式或测试密钥)。POSTBAG_API_URL 为可选项,仅自托管实例需要。需要能访问 Postbag API 的网络。
安装
在 SourceWeft 中
- 打开 控制台中的 Postbag,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
Postbag
[CI] [npm: postbag] [npm: @postbag/sdk] [npm: @postbag/mcp] [License: AGPL-3.0] [skills.sh]
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.
来源:README.md,提交 192e431
工具
0版本历史
1- v0.1.1最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分