Tempo

io.github.tsutera09由 GitHub 账号 tsutera09 发布v0.2.0更新于 Oct 24, 2026

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

已验证STDIO仅桌面效率与工作流金融数据与分析

概览

AI 生成的概览

Tempo 将单人创业者的个人状态（睡眠、情绪、压力、精力）与业务负荷（会议、收入）结合，让助手能就工作量和休息给出建议。

可以做什么
Tempo 是一个本地 MCP 服务器，把人的承载能力数据与业务负荷融合成一个信号。工具可让助手记录状态打卡（情绪、精力、压力、睡眠）、录入收入与日历事件、计算综合 Tempo 分数和每恢复小时收入指标、推荐业务动作、记录或执行这些动作、获取时间序列历史、生成每周摘要，并管理许可证。所有数据存放在本地 SQLite 文件中。
适用场景
如果你独自经营业务，希望助手在建议拒绝哪些会议、如何调价或何时休息时，把你的睡眠、压力和精力与会议、收入和商机一起考虑，那么这个服务器值得添加。若你只需要任务或日历管理、不关心个人状态维度，则用处不大。
运行要求
以 PyPI 包 tempo-mcp 通过 stdio 在本地运行；需要 Python 3.10+ 以及 mcp 库（1.x 或 2.x）。未声明必须的账号、API 密钥或环境变量。付费档位通过许可证密钥激活，密钥可通过 TEMPO_LICENSE_KEY 环境变量或本地许可证文件提供。
安装前请注意
付费档位为订阅制（Pro 与 Team Solo），且部分工具会执行动作而不只是记录，助手可能代你采取真实的业务操作。数据保存在本地 SQLite 文件中，但 README 提到可选的 Pro 云同步会把数据发送到本机之外。许可证密钥属于机密信息，应妥善保管。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Tempo，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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

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

json
{  "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

bash
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

来源：README.md，提交 f2684b6

工具

0
SourceWeft 尚未在沙箱中启动过该软件包，因此其工具未知。

版本历史

1
  1. v0.2.0最新Sep 16, 2026

评分

已满足适用检查项的 40%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。