Fuses founder biometrics (sleep, mood, stress, energy) with business metrics (revenue, calendar load, deal flow) into a single queryable surface for Claude. Exposes eight tools over stdio: log_checkin for vitals, ingest_revenue_event and ingest_calendar_event for business signals, tempo_score to compute Revenue per Recovery Hour, and recommend_actions for prescriptive moves like declining meetings or scheduling rest. Data lives in a local SQLite file. Built for solo operators where the founder is the bottleneck and traditional tools treat human capacity and business performance as separate systems. Use it when you want Claude to make scheduling or pricing decisions informed by how burned out you actually are.
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.
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.
pip install tempo-mcp
~/.claude/settings.json (or equivalent):
{
"mcpServers": {
"tempo": {
"command": "python",
"args": ["-m", "tempo_mcp"]
}
}
}
| Tool | Purpose |
|---|---|
log_checkin | Log mood / energy / stress / sleep |
ingest_revenue_event | Record revenue (from Stripe connector or manual) |
ingest_calendar_event | Record a calendar block (internal, sales, deep work) |
tempo_score | Compute the composite Tempo score + RpRH |
recommend_actions | Prescriptive business moves based on current state |
apply_action | Log (or, on Pro, execute) an action |
get_history | Full time-series history over N days — for trend analysis |
weekly_digest | Narrative week-over-week summary Claude can read aloud |
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.
Tempo stores everything in ~/.tempo/tempo.sqlite3. Nothing leaves your machine unless you enable the Pro cloud sync.
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
See PUBLISH.md at the repo root for the ordered release checklist (PyPI, npm mirror, MCP registry).
MIT