Tempo
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.
- tools
- 11
- transport
- STDIO
- last updated
- Aug 9, 2026
Tools
11 toolsPublic tool metadata for what this MCP can expose to an agent.
log_checkinLog mood / energy / stress / sleep
Log mood / energy / stress / sleep
No parameter schema in public metadata yet.
ingest_revenue_eventRecord revenue (from Stripe connector or manual)
Record revenue (from Stripe connector or manual)
No parameter schema in public metadata yet.
ingest_calendar_eventRecord a calendar block (internal, sales, deep work)
Record a calendar block (internal, sales, deep work)
No parameter schema in public metadata yet.
tempo_scoreCompute the composite Tempo score + RpRH
Compute the composite Tempo score + RpRH
No parameter schema in public metadata yet.
recommend_actionsPrescriptive business moves based on current state
Prescriptive business moves based on current state
No parameter schema in public metadata yet.
apply_actionLog (or, on Pro, execute) an action
Log (or, on Pro, execute) an action
No parameter schema in public metadata yet.
get_historyFull time-series history over N days — for trend analysis
Full time-series history over N days — for trend analysis
No parameter schema in public metadata yet.
weekly_digestNarrative week-over-week summary Claude can read aloud
Narrative week-over-week summary Claude can read aloud
No parameter schema in public metadata yet.
license_statusShow the active plan and what it unlocks
Show the active plan and what it unlocks
No parameter schema in public metadata yet.
activate_licenseActivate a Pro / Team Solo key
Activate a Pro / Team Solo key
No parameter schema in public metadata yet.
export_dataExport the whole local dataset as JSON or CSV (Pro)
Export the whole local dataset as JSON or CSV (Pro)
No parameter schema in public metadata yet.
Sponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageReadme
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):
Details
- Repository
- github.com/tsutera09/tempo-mcp
- Package
tempo-mcp- Transport
- STDIO
- Registry
- MCP registry, active