Tempo MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| log_checkinA | Log a morning (or moment-in-time) founder check-in. Args: mood: 1..10, subjective mood energy: 1..10, subjective energy stress: 1..10, subjective stress sleep_hours: hours of sleep last night (can be fractional) note: optional free text |
| ingest_revenue_eventA | Record a revenue event. Amounts in the user's home currency. Typing one in by hand (source="manual") is free. Automated ingest from an upstream connector — Stripe, QuickBooks, a wearable bridge — is a Pro feature. |
| ingest_calendar_eventA | Ingest a calendar event. kind ∈ {sales, deep_work, admin, personal}. As with revenue: manual entry is free, connector-sourced ingest is Pro. |
| tempo_scoreA | Compute the current Tempo score and supporting metrics. Returns tempo (0..100), capacity, load, RpRH (revenue per recovery hour) and its 7-day delta, plus human-readable signals and alerts. Free tier scores over the last 7 days; Pro over any window. |
| recommend_actionsB | Return prescriptive business actions based on current Tempo state. These are the decisions that separate Tempo from a wellness tracker: price raises, meeting declines, rest days, deep-work blocks. |
| apply_actionA | Record — or on Pro, execute — an action Tempo recommended. Args: kind: auto_decline, reprice, rest_day, block_deep_work, ... payload: the action's parameters (who, when, how much) outcome: applied | dismissed | pending execute: Pro only. Hand the action to the connected executor (Cal.com / Stripe / Gmail) instead of only writing it down. Pro allows 3 executions per day; Team Solo is unlimited. Logging is always free — the decision record is the point of the free tier, and it is what makes the weekly retrospective honest. |
| get_historyA | Return the full time-series history so Claude can surface trends. Returns daily check-in snapshots, revenue by day, and calendar load over the requested window. Useful for building sparklines, comparing weeks, or asking "am I actually getting better?" Free tier returns the last 7 days; Pro returns everything. |
| weekly_digestA | Generate a human-readable weekly digest Claude can read aloud or send. Compares this week vs last week on every key metric: Tempo score, capacity, load, RpRH, meeting hours, deep work hours, revenue. Returns a narrative summary string plus structured deltas. Week-over-week needs 14 days of history, so the comparison is Pro. Free tier gets this week's digest on its own. |
| license_statusA | Show the active Tempo plan and what it unlocks. Call this whenever the user asks what they're paying for, why a tool refused, or how much history they can see. |
| activate_licenseA | Activate a Tempo Pro or Team Solo licence key. Paste the key from the welcome email. It is verified offline against Tempo's signing key and saved to ~/.tempo/license — nothing is sent anywhere. |
| export_dataA | Export the full local Tempo dataset. Pro and Team Solo only. Args: fmt: "json" for the raw records, "csv" for one CSV block per table. Your data is yours; this is the door out. It reads the local SQLite database and returns it inline — nothing is uploaded. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tsutera09/tempo-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server