Tempo API MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 331 installs a week from npm. Last commit 15 Sep 2026.
Tempo time-tracking for Claude — worklogs, plans, and timesheet approvals
Today is the operative word: we check Tempo API MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add tempo-api-mcp -- npx -y tempo-api-mcp
{
"mcpServers": {
"tempo-api-mcp": {
"args": [
"-y",
"tempo-api-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.tempo-api-mcp]
command = "npx"
args = ["-y", "tempo-api-mcp"]
{
"mcpServers": {
"tempo-api-mcp": {
"args": [
"-y",
"tempo-api-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"tempo-api-mcp": {
"args": [
"-y",
"tempo-api-mcp"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
TEMPO_API_TOKEN (Your Tempo API token (Settings → API integration in your Tempo workspace)).
The author declared them in the registry entry; get the values from the project itself.
Calendar workflow engine for time off, approvals, and quick actions on any calendar backend.
Governed AI workflows with human approval gates and audit trails for Claude and MCP clients.
Six Flags MCP for Claude — live wait times, park hours, shows, and day planning
Time tracking and invoicing for AI agents and their humans: track, log and bill work by agent.
MCP server for Monnet — motions, plans, files, approvals, and the team's company brain.
AI cost tracking: 11 tools for spend, budgets, and Claude Code + Cursor + Cline costs
Aztra workspace: projects, issues, sprints, goals, wiki and time tracking.
MCP server for Toggl Track — gives Claude access to your time tracking data
Answers built from our own checks of this server.