tempo-api-mcp
# tempo-api-mcp
[](https://github.com/chrischall/tempo-api-mcp/actions/workflows/ci.yml)
[](https://www.npmjs.com/package/tempo-api-mcp)
[](LICENSE)
Tempo API MCP server for Claude — developed and maintained by AI (Claude Code)
## Confirmations
Every write (create/update/delete, and the timesheet submit/approve/reject/reopen/recall actions) asks the user to confirm before it changes anything: a confirmation prompt where the client supports one; otherwise the first call returns a preview of exactly what would be sent plus a `confirmToken`, and only a repeat call with that token proceeds.
| variable | default | |
|---|---|---|
| `MCP_CONFIRM_MODE` | `ask-user` | What a write does on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop). `ask-user`: two steps — the first call does nothing and returns a preview plus a token, and the model must get your approval in chat before calling again with it. `auto`: the same two steps, but the model may use the token after reviewing the preview itself. `refuse`: writes are refused on such clients. A client that can show prompts (Claude Code) always gets the real prompt. An unrecognised value is treated as `refuse`. |
| `MCP_CONFIRM_TTL_SECONDS` | `600` | How long a token stays valid. |
| `MCP_CONFIRM_SECRET` | random per process | Signing key; set it only if tokens must survive a server restart. |
TDQS
Scored across 48 tools
Most tools have clear verb_noun names, but the worklog retrieval family is oversized and overlapping: tempo_get_worklogs already supports filtering by project/issue, making tempo_get_worklogs_by_project and tempo_get_worklogs_by_issue redundant, and tempo_search_worklogs overlaps with both. Descriptions help distinguish the by_team/by_account variants, but an agent could easily misselect.
All tools follow a consistent tempo_<verb>_<object> pattern in snake_case, which is strong. Minor deviations like tempo_get_timesheet_approvals_waiting (odd phrasing) and singular/plural inconsistencies (approval vs approvals) prevent a perfect score.
48 tools is far beyond the typical 3-15 for a coherent MCP server and above the 25+ threshold. The worklog retrieval family alone has 7 near-overlapping tools, inflating the count. While Tempo is a broad domain, the surface could be consolidated.
The server covers CRUD for worklogs, plans, teams, and accounts, plus a full timesheet approval workflow. However, it provides no way to create, update, or delete team memberships, and only read access to account categories, roles, and periods, which are notable gaps for a supposedly comprehensive Tempo API surface.