mcpField
T
tempo

tempo

Local
github.com/tsutera09Health0Updated 12w ago

About tempo

tempo is an MCP server for solo operators that combines personal check-ins with business activity to inform decisions. It calculates a Tempo score and Revenue per Recovery Hour, and stores data locally by default.

Key features

  1. 01Log mood, energy, stress, and sleep
  2. 02Record revenue and calendar events
  3. 03Compute Tempo score and RpRH
  4. 04Recommend and track actions
  5. 05Review history and weekly digests
  6. 06Local SQLite data storage

Use cases

  1. 01Relate sleep and stress to business workload
  2. 02Review changes in revenue per recovery hour
  3. 03Use current capacity to plan business actions

MCP support

Exposes check-in, revenue and calendar logging, scoring, recommendations, action tracking, history, and digest tools to MCP clients.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"tsutera09-tempo": {
"command": "uvx",
"args": [
"tempo-mcp"
]
}
}
}
Run commanduvx tempo-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypitempo-mcp0.2.0

Tools

11

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
moodintegerYes
noteanyNo
energyintegerYes
stressintegerYes
sleep_hoursnumberYes

Details

From the project README

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

ToolPurpose
log_checkinLog mood / energy / stress / sleep
ingest_revenue_eventRecord revenue (from Stripe connector or manual)
ingest_calendar_eventRecord a calendar block (internal, sales, deep work)
tempo_scoreCompute the composite Tempo score + RpRH
recommend_actionsPrescriptive business moves based on current state
apply_actionLog (or, on Pro, execute) an action
get_historyFull time-series history over N days — for trend analysis
weekly_digestNarrative week-over-week summary Claude can read aloud
license_statusShow the active plan and what it unlocks
activate_licenseActivate a Pro / Team Solo key
export_dataExport the whole local dataset as JSON or CSV (Pro)

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.

FreePro — $39/moTeam Solo — $79/mo
Daily check-ins, Tempo score, RpRH✅✅✅
Manual revenue / calendar logging✅✅✅
History window7 daysunlimitedunlimited
Week-over-week digest—✅✅
Connector ingest (Stripe, calendar, wearable)—✅✅
Executed actionslog only3 / dayunlimited
Data export (JSON / CSV)—✅✅
Seats115

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.