English Français العربية

io.github.tsutera09/tempo

Registre officiel Autres

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

Code source Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

PYPI package tempo-mcp
Claude Code 
claude mcp add tempo -- uvx tempo-mcp==0.2.0
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "tempo": {
            "command": "uvx",
            "args": [
                "tempo-mcp==0.2.0"
            ]
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Tempo MCP
  2. What makes this novel
  3. Install
  4. Register with Claude Desktop / Cowork / Claude Code
  5. Tools exposed over MCP
  6. Plans
  7. Example conversation with Claude
  8. Data stays local
  9. Develop
  10. Publishing
  11. License

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

Questions fréquentes

Qu'est-ce que io.github.tsutera09/tempo ?

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

Comment installer io.github.tsutera09/tempo ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add tempo -- uvx tempo-mcp==0.2.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.tsutera09/tempo ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

io.github.tsutera09/tempo est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient io.github.tsutera09/tempo ?

Il est publié par tsutera09. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.