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.
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file fleetpost_mcp-0.1.0.tar.gz.
File metadata
- Download URL: fleetpost_mcp-0.1.0.tar.gz
- Upload date:
- Size: 10.2 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/7.0.0 CPython/3.12.3
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
d9c0748b13b4f391adf1ea312e7594b8adc74ebdac2ad3589044193da15be59f
|
|
| MD5 |
9b10ad36ffb1461456e71b3e4435f2fa
|
|
| BLAKE2b-256 |
6d41cdce8e8e644fbeec78aff379229fa488d459d698c3b39bef7865051f224c
|
File details
Details for the file fleetpost_mcp-0.1.0-py3-none-any.whl.
File metadata
- Download URL: fleetpost_mcp-0.1.0-py3-none-any.whl
- Upload date:
- Size: 9.9 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/7.0.0 CPython/3.12.3
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
b1616904150f52c3da83557aa388ef8649e84307542bf7f8410f9437f8cab2a6
|
|
| MD5 |
42f482bbce5f4e9af09eb2dee6146156
|
|
| BLAKE2b-256 |
0c4af67ec0e581e7d3b7603b2c1187cb27c196dbb491dae36557726b95db8d66
|