MCP server for CashPilot — monitor passive income, bandwidth sharing, and DePIN earnings
Runs on your machine from its package; the steps are below.
At most: moves money, runs code or commands, deletes data, or sends messages for you.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y cashpilot-mcp
MCP client config
{
"mcpServers": {
"cashpilot": {
"command": "npx",
"args": [
"-y",
"cashpilot-mcp"
]
}
}
}Run
docker run -i --rm drumsergio/cashpilot-mcp:v0.2.3
MCP client config
{
"mcpServers": {
"cashpilot": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"drumsergio/cashpilot-mcp:v0.2.3"
]
}
}
}
A tiny bridge that exposes any CashPilot instance as an MCP server, enabling LLMs to monitor passive income earnings, manage services, and control fleet workers.
It talks to your own CashPilot instance with its admin API key, over HTTP or stdio.
cashpilot://earnings/summary, cashpilot://fleet/summary, ...).trigger_collection runs an earnings collection across all services now; get_compose returns a service's Docker Compose definition./mcp) over HTTP, or stdio with TRANSPORT=stdio.127.0.0.1:8081 by default; MCP_AUTH_TOKEN adds bearer auth when you expose it.npx cashpilot-mcp) and multi-arch Go binaries.Register the npm package in your MCP client (Claude Desktop, Claude Code, Cursor); npx runs it over stdio:
{
"mcpServers": {
"cashpilot": {
"command": "npx",
"args": ["-y", "cashpilot-mcp"],
"env": {
"CASHPILOT_URL": "http://localhost:8080",
"CASHPILOT_API_KEY": "<your CASHPILOT_ADMIN_API_KEY>"
}
}
}
}
The key is CashPilot's admin API key, not the fleet key. Docker Compose, the HTTP server and local builds are in Getting started.
CashPilot, the passive income fleet manager this server talks to.