
Fleetpost
io.github.StanimirTenevPublished by GitHub account StanimirTenevv0.2.0Updated Oct 25, 2026
A mailbox for your machines: read fleet capabilities, send a request. Offline, no server.
Overview
Fleetpost is a local MCP server that gives an assistant a mailbox for coordinating several machines through a shared rclone remote, without a central server.
- What you can do
- Check fleet status: pending requests, protocol changes, known machines and last cycle, plus each machine's capabilities, all read from already-synced files and working offline. Read a single request from this machine's inbox. Send a request to another machine's inbox, with required description, definition of done and expiry. Mark a request handled, moving it into the handled folder of your own inbox. Run one coordination cycle now, which is one of the few actions that touches the remote.
- When to use it
- Use it when you coordinate work across several machines that are not always online and want an assistant to ask what each machine can do, hand off tasks, and process incoming requests through a shared folder rather than a server or daemon.
- Requirements
- Runs locally over stdio, typically launched with uvx from the fleetpost-mcp PyPI package. Needs a working Fleetpost checkout with a filled-in config.env, pointed to by FLEETPOST_CONFIG or found in the starting directory. If the config was copied away from the checkout, FLEETPOST_HOME must point to the checkout because fleet_sync and fleet_handle run the repo's own scripts. An rclone remote is needed for sending and syncing.
Installation
In SourceWeft
- Open Fleetpost in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
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.
Source: mcp/README.md at commit d2e4f9c
Tools
0Version history
1- v0.2.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts