CashPilot MCP

cashpilot-mcp

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.

Features

• Read-only resources for earnings, deployed services, the catalog, fleet status, workers, health scores and collector alerts (cashpilot://earnings/summary, cashpilot://fleet/summary, ...).
• Tools to query daily and historical earnings, read service logs, and start, stop, restart, deploy or remove services.
• trigger_collection runs an earnings collection across all services now; get_compose returns a service's Docker Compose definition.
• One JSON-RPC endpoint (/mcp) over HTTP, or stdio with TRANSPORT=stdio.
• Listens on 127.0.0.1:8081 by default; MCP_AUTH_TOKEN adds bearer auth when you expose it.
• Ships as a Docker image, an npm package (npx cashpilot-mcp) and multi-arch Go binaries.

Quick start

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.

Documentation

• Getting started: Docker Compose, npm, local build
• Configuration: environment variables and MCP client configuration
• Usage: resources and tools
• Development: testing, contributing, credits
• Related projects: the family and registry listings

Related projects

CashPilot, the passive income fleet manager this server talks to.

License

GPL-3.0-or-later