Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Founder-vitals connector joining human capacity to business load for solo operators.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"tempo": {
"command": "uvx",
"args": [
"tempo-mcp"
]
}
}
}Run this in your terminal
claude mcp add tempo -- uvx tempo-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"tempo": {
"command": "uvx",
"args": [
"tempo-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"tempo": {
"type": "stdio",
"command": "uvx",
"args": [
"tempo-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account tsutera09, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Asset Notation
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Read and maintain an Asset Notation file on disk: net worth, holdings, valuations, CSV import.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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.
pip install tempo-mcp
Requires Python 3.10+ and works with both mcp 1.x and 2.x.
~/.claude/settings.json (or equivalent):
{
"mcpServers": { "tempo": { "command": "python", "args": ["-m", "tempo_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) |
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:
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.
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.*
Tempo stores everything in ~/.tempo/tempo.sqlite3. Nothing leaves your machine unless you enable the Pro cloud sync.
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
See PUBLISH.md at the repo root for the ordered release checklist (PyPI, npm mirror, MCP registry).
MIT