Tempo Api Mcp
Log Tempo worklogs, plans, and timesheet approvals from Claude without leaving the agent chat.
Overview
Tempo API MCP is a build-phase MCP server that exposes Tempo worklogs, plans, and timesheet approvals to Claude through stdio and your workspace API token.
What is this MCP server?
- stdio npm MCP server (tempo-api-mcp v2.1.4)
- Worklogs, plans, and timesheet approval tools against Tempo API
- Requires TEMPO_API_TOKEN from Tempo workspace Settings → API integration
- Built for Claude Code-style agents via Model Context Protocol
- No local database—live Tempo workspace data only
- Registry package tempo-api-mcp at version 2.1.4
- stdio transport; one required secret env var TEMPO_API_TOKEN
- Published under io.github.chrischall/tempo-api-mcp on GitHub
What problem does it solve?
Switching between Claude and Tempo to log time or approve timesheets breaks flow when you are trying to ship and report hours in one sitting.
Who is it for?
Freelancers and indie teams on Jira + Tempo who want agent-driven worklog and approval tasks during delivery.
Skip if: Builders without a Tempo workspace, API token, or any need to track billable or issue-linked time.
What do I get? / Deliverables
After you add the server and TEMPO_API_TOKEN, your agent can query and act on Tempo time data from the same session where you code and plan.
- MCP tools callable for Tempo worklogs, plans, and approvals
- Agent sessions grounded in live Tempo workspace data
- Reduced context switching between agent chat and Tempo UI
Recommended MCP Servers
Journey fit
Time tracking and approval workflows sit where solo builders manage delivery cadence during active product and client work. The pm subphase is the canonical shelf for issue-linked hours, plans, and timesheet governance in Tempo.
How it compares
Tempo API integration via MCP, not a standalone time-tracking app or agent skill.
Common Questions / FAQ
Who is tempo-api-mcp for?
It is for developers and PMs who use Tempo on Jira and want Claude to manage worklogs, plans, and timesheet approvals through MCP.
When should I use tempo-api-mcp?
Use it during active builds when you log hours, review plans, or approve timesheets and prefer doing that from your coding agent instead of only the Tempo web UI.
How do I add tempo-api-mcp to my agent?
Install the npm package tempo-api-mcp, add a stdio MCP server entry in Claude Code or Cursor, and set the required secret environment variable TEMPO_API_TOKEN from Tempo Settings → API integration.