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
| Tool | What it does |
|---|---|
fleet_status |
What is waiting: unhandled requests, protocol changes, who is known, last cycle |
fleet_capabilities |
What each machine in the fleet can do |
fleet_read_request |
Read one request from this machine's inbox |
fleet_send_request |
Ask another machine to do something — drops a request in its inbox |
fleet_handle |
Mark a request done; moves it to inbox/handled/ |
fleet_sync |
Run one coordination cycle now |
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.
{
"mcpServers": {
"fleetpost": {
"command": "uvx",
"args": ["fleetpost-mcp"],
"env": {
"FLEETPOST_CONFIG": "/path/to/fleetpost/config.env"
}
}
}
}
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.
Metadata
Release files for fleetpost-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| fleetpost_mcp-0.2.0.tar.gz | 11.8 kB | Without provenance | Details for fleetpost_mcp-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fleetpost_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for fleetpost_mcp-0.2.0-py3-none-any.whl |
Total release size: 22.4 kB
Release files / fleetpost_mcp-0.2.0.tar.gz
| Download URL | fleetpost_mcp-0.2.0.tar.gz |
|---|---|
| Size | 11.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d3742a513935e747d4fb6dfbd8e08c1d198e3d8d9ed2bd635a11d2c3fe0d8fb
|
|
BLAKE2b-256 checksum How to use checksums |
01bdf7c72c30775778e0720beddac17ab4724c502c5194c77d259651245e1dde
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / fleetpost_mcp-0.2.0-py3-none-any.whl
| Download URL | fleetpost_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 10.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5d662f3adf83b739049edaa9f7f98b588de9064aa5a6fdf9f2b4a0df47ecd318
|
|
BLAKE2b-256 checksum How to use checksums |
2a93a6698e0ce3db76e2402b350b9996e43985769dfdc57e02773d6e97c78a82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for fleetpost-mcp 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.