Tempo

io.github.tsutera09Published by GitHub account tsutera09v0.2.0Updated Oct 24, 2026

Founder-vitals connector joining human capacity to business load for solo operators.

VerifiedSTDIODesktop onlyProductivity & Workflow Finance Data & Analytics

Server details

Identifier: io.github.tsutera09/tempo
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account tsutera09 for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.tsutera09%2Ftempo.svg)](https://sourceweft.com/mcp/io.github.tsutera09%2Ftempo?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Tempo joins a solo founder's personal state (sleep, mood, stress, energy) with business load (meetings, revenue) so an assistant can advise on workload and…

What you can do: Tempo is a local MCP server that fuses human capacity data with business load into one signal. Tools let an assistant log check-ins (mood, energy, stress, sleep), record revenue and calendar events, compute a composite Tempo score and a Revenue per Recovery Hour metric, recommend business actions, log or execute those actions, retrieve time-series history, produce a weekly digest, and manage a licence. It stores everything in a local SQLite file.
When to use it: Worth adding if you run a business alone and want an assistant to weigh your sleep, stress and energy against meetings, revenue and deal flow when suggesting what to decline, reprice or rest from. Less useful if you only want task or calendar management without the personal-vitals angle.
Requirements: Runs locally over stdio as the PyPI package tempo-mcp; needs Python 3.10+ and the mcp library (1.x or 2.x). No accounts, API keys or environment variables are declared as required. Paid tiers are activated with a licence key, which can be supplied through the TEMPO_LICENSE_KEY environment variable or a local licence file.

Before you install

Paid tiers are subscription-based (Pro and Team Solo) and some tools execute actions rather than only logging them, so an assistant may take real business steps on your behalf. Data is kept in a local SQLite file, but the README notes an optional Pro cloud sync that would send it off the machine. Licence keys are secrets and should be handled as such.

Installation

In SourceWeft

Open Tempo in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

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):

json

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

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

Tools exposed over 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
`license_status`	Show the active plan and what it unlocks
`activate_license`	Activate a Pro / Team Solo key
`export_data`	Export 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.

	Free	Pro — $39/mo	Team Solo — $79/mo
Daily check-ins, Tempo score, RpRH	✅	✅	✅
Manual revenue / calendar logging	✅	✅	✅
History window	7 days	unlimited	unlimited
Week-over-week digest	—	✅	✅
Connector ingest (Stripe, calendar, wearable)	—	✅	✅
Executed actions	log only	3 / day	unlimited
Data export (JSON / CSV)	—	✅	✅
Seats	1	1	5

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

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

bash

git clone https://github.com/tsutera09/tempo-mcpcd tempo-mcppip install -e '.[dev]'pytestpython -m tempo_mcp   # runs the MCP server on stdio

git clone https://github.com/tsutera09/tempo-mcpcd tempo-mcppip install -e '.[dev]'pytestpython -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

Source: README.md at commit f2684b6

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.2.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts
Declare a license in the repository or the registry entry.