Log inSubmit server
Tempo API MCP logo

Tempo API MCP

Connects Claude and other MCP clients to Tempo for worklogs, plans, and timesheet actions with write confirmations.

InstallRepository
Full README Compare alternatives Embed widget Claim this listing

Install Tempo API MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "tempo-api-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tempo-api-mcp"
      ],
      "env": {
        "TEMPO_API_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The tempo-api-mcp MCP server connects MCP clients to Tempo for managing worklogs, plans, and timesheet approval actions. It runs as an npm package over a local stdio configuration and uses a Tempo API token. Reach for it when an agent needs to inspect or change time-tracking data while retaining confirmation safeguards for writes.

Use cases

  • Create and update Tempo worklogs from an MCP client
  • Review and manage Tempo plans
  • Submit or approve timesheets with confirmation
  • Preview destructive or approval-related writes before execution

Key features

  • Tempo worklog management
  • Tempo plan access
  • Timesheet submit and approval actions
  • Confirmation prompts for writes
  • Preview and token-based write confirmation
  • Configurable confirmation token lifetime

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

6/6 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · tempo-api-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.4kPackage downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.

How Tempo API MCP works

What tempo-api-mcp does

tempo-api-mcp MCP server exposes Tempo time-tracking operations to Claude and other MCP-compatible clients. Its supported scope includes worklogs, plans, and timesheet workflows. Timesheet actions include submitting, approving, rejecting, reopening, and recalling a timesheet.

The server is intended for agent-driven time tracking. It can support requests that read or modify Tempo data, while treating modifications as actions that require confirmation before execution.

How it works

The tempo-api-mcp MCP server is launched as an npm package and communicates with the MCP client through a local process. A Tempo API token is supplied through the server environment. The repository’s example uses npx -y tempo-api-mcp as the command.

Every create, update, or delete operation requires confirmation. The same applies to timesheet submit, approve, reject, reopen, and recall actions. On clients that support confirmation prompts, the server can show a prompt before proceeding. On clients without that capability, the first request returns a preview of the intended request and a confirmation token; a later call with the token performs the action.

Setup and configuration

Configure the server as a local MCP process with npx -y tempo-api-mcp, and provide TEMPO_API_TOKEN in its environment. The tempo-api-mcp MCP server also accepts confirmation-related settings:

  • MCP_CONFIRM_MODE controls the fallback behavior when a client cannot display a confirmation prompt. ask-user is the default, auto permits the model to use a reviewed token, and refuse blocks writes.
  • MCP_CONFIRM_ELICITATION defaults to on. Set it to off when the client claims prompt support but does not display prompts, including opencode v2.
  • MCP_CONFIRM_TTL_SECONDS controls token lifetime and defaults to 600 seconds.
  • MCP_CONFIRM_SECRET provides a signing key when confirmation tokens need to remain valid after a server restart. Otherwise, a random key is generated for each process.

Tools and capabilities

The available capability areas are:

  • Creating, updating, and deleting worklog-related records.
  • Working with Tempo plans.
  • Submitting and managing timesheet approval states.
  • Previewing write requests before confirmation on clients without prompt support.

Limitations and notes

The tempo-api-mcp MCP server does not execute writes silently by default. An unrecognized MCP_CONFIRM_MODE value is treated as refuse. Confirmation tokens expire according to MCP_CONFIRM_TTL_SECONDS, and tokens do not survive a restart unless a stable MCP_CONFIRM_SECRET is configured.

Client behavior matters: opencode v2 requires MCP_CONFIRM_ELICITATION=off because its unsupported prompt display can cause writes, including timesheet approvals, to hang. The provided configuration example targets Claude and uses a local server definition.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Tempo API MCP

tempo-api-mcp is an MCP server that connects Claude and compatible MCP clients to Tempo’s time-tracking system. Its main capabilities cover worklogs, plans, and timesheet actions, including submit, approve, reject, reopen, and recall operations. Write actions require confirmation through a prompt or a preview-and-token flow.

Run it as a local MCP process with `npx -y tempo-api-mcp`. Configure the command in your MCP client and provide `TEMPO_API_TOKEN` in the server environment, as shown in the repository’s opencode configuration example.

Every create, update, delete, and listed timesheet action requires confirmation. Clients with prompt support receive a confirmation prompt; other clients first receive a request preview and token, then need a follow-up call containing that token.

Set `MCP_CONFIRM_ELICITATION=off` in the server’s environment. opencode v2 reports prompt support but does not display the prompts, so disabling elicitation makes the server use the two-step preview and confirmation-token flow.

Yes, it can be configured as a standard local stdio MCP server in Cursor. Use the `npx -y tempo-api-mcp` command and provide the required Tempo API token through the client’s environment configuration.

Related MCP servers

All in Workplace & Productivity All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTempo API MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/tempo-api-mcp?style=directory)](https://allmcps.com/mcp/tempo-api-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/tempo-api-mcp"><img src="https://allmcps.com/api/badge/tempo-api-mcp?style=directory" alt="Tempo API MCP on AllMCPs" /></a>