
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 分