Tempo MCP

The founder-vitals connector for solo operators. Tempo is the first MCP server that joins human capacity (sleep, mood, stress, energy) to business load (meetings, revenue, deal flow) and exposes them to Claude as one signal.

For a solopreneur, the founder is the single point of failure. Every other tool treats the business and the human as separate things. Tempo fuses them, so Claude can make business decisions — decline meetings, reprice services, prescribe rest days — based on the founder's real-time state.

What makes this novel

Tempo invents a single KPI that no other tool can compute on its own:

Revenue per Recovery Hour (RpRH) — revenue generated divided by hours of true recovery. Falling RpRH means you're working harder for less, and it's the earliest quantitative signal of founder burnout.

Install

pip install tempo-mcp

Requires Python 3.10+ and works with both mcp 1.x and 2.x.

Register with Claude Desktop / Cowork / Claude Code

~/.claude/settings.json (or equivalent):

{
  "mcpServers": {
    "tempo": {
      "command": "python",
      "args": ["-m", "tempo_mcp"]
    }
  }
}

Tools exposed over MCP

Plans

Tempo is free forever for the core loop. Paid tiers exist because the expensive parts — long history, connector ingest, executing actions — are the parts that need maintaining.

Subscribe at temposolo.app, then paste the key from your welcome email:

activate_license with key tempo_v1....

Or set it yourself — TEMPO_LICENSE_KEY in the environment, or one line in ~/.tempo/license.

Licence keys are Ed25519-signed and verified offline against a public key baked into the package. There is no licence server, no activation call, and no telemetry: Tempo works on a plane and cannot tell us when you use it. An expired or missing key quietly drops you to the free tier rather than locking you out of your own data.

Example conversation with Claude

You: "I slept 5 hours, energy's at 3/10, stress 8. Log it and tell me what to do about tomorrow."

Claude (using Tempo): logs checkin → pulls score → RpRH down 22% → 4 external calls booked tomorrow → recommends auto-decline of 2 discovery calls and a rest day.

Data stays local

Tempo stores everything in ~/.tempo/tempo.sqlite3. Nothing leaves your machine unless you enable the Pro cloud sync.

Develop

git clone https://github.com/tsutera09/tempo-mcp
cd tempo-mcp
pip install -e '.[dev]'
pytest
python -m tempo_mcp   # runs the MCP server on stdio

Publishing

See PUBLISH.md at the repo root for the ordered release checklist (PyPI, npm mirror, MCP registry).

License

MIT