
Fleetpost
io.github.StanimirTenev由 GitHub 帳號 StanimirTenev 發布v0.2.0更新於 Oct 25, 2026
A mailbox for your machines: read fleet capabilities, send a request. Offline, no server.
概覽
Fleetpost 是本地 MCP 伺服器,為助理提供「機器信箱」,透過共用的 rclone 遠端在多台機器之間協調任務,不需要中央伺服器。
- 可以做什麼
- 檢視機群狀態:待處理請求、協定變更、已知機器與上次週期,以及各機器能力,皆讀取已同步的檔案,可離線使用。從本機收件匣讀取單一請求。向另一台機器的收件匣送出請求,必須提供需求、完成定義與到期時間。將請求標記為已處理,移入本機收件匣的已處理目錄。立即執行一次協調週期,這是少數會存取遠端的操作之一。
- 適用情境
- 適合跨多台並非隨時在線的機器協調工作:讓助理查詢各機器能做什麼、分派任務,並透過共用資料夾而非伺服器或常駐程式處理收到的請求。
- 執行需求
- 以 stdio 在本機執行,通常用 uvx 從 fleetpost-mcp 的 PyPI 套件啟動。需要可用的 Fleetpost 程式碼檢出與填妥的 config.env,以 FLEETPOST_CONFIG 指定,或放在啟動目錄中。若設定檔被複製到檢出目錄之外,需以 FLEETPOST_HOME 指向檢出目錄,因為 fleet_sync 與 fleet_handle 會執行儲存庫自帶的指令碼。送出與同步需要 rclone 遠端。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Fleetpost,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
fleetpost-mcp
Give your agent the fleet's mailbox. An MCP server for Fleetpost — offline-tolerant, server-less coordination between machines over any rclone remote.
Your agent can ask what the other machines can do, hand one of them a task, and work through its own inbox — without a server, a daemon, or every machine being online at once. A machine that is off picks up its mail on its next cycle.
Tools
Only fleet_send_request and fleet_sync touch the remote. Everything else reads files the
sync already pulled, so status is instant and works with no network at all.
Setup
You need a working Fleetpost checkout with a filled-in config.env — see the
main README. The MCP server reads that same
file; it introduces no configuration of its own.
FLEETPOST_CONFIG can be omitted if the server starts in the directory holding config.env.
If you copied the config away from the checkout, also set FLEETPOST_HOME to the checkout —
fleet_sync and fleet_handle run the repo's own scripts.
Then ask your agent:
Anything waiting for me? — and if the build box can sign, ask it to sign the release.
What it will not do
The protocol's rules are enforced here, not just documented:
- Writes only into another machine's inbox, at the top level. Never into
handled/, never into anyone's descriptors. That is what keeps concurrent writes safe. fleet_handleonly tidies your own inbox — the owner is the only one allowed to.- A request must be complete to be sent. What is wanted, what "done" means, and an expiry are required arguments; a malformed request cannot be created.
- Ask for actions, not access. If a job needs a credential you lack, the machine that has it does the work and returns the result. Secrets never travel.
There is no server, no database, and no daemon of our own — the transport stays a folder on an rclone remote, and this server only reads and writes files in it.
License
MIT.
來源:mcp/README.md,提交 d2e4f9c
工具
0版本歷史
1- v0.2.0最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分