Tempo API MCP logo

Tempo API MCP

Manage Tempo worklogs, plans, teams, memberships, accounts, and categories through MCP tools.

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",
        "MCP_CONFIRM_MODE": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_ELICITATION": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_TTL_SECONDS": "YOUR_VALUE_HERE",
        "MCP_CONFIRM_SECRET": "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— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

tempo-api-mcp connects MCP-compatible AI clients to Tempo for time tracking and resource management. It provides tools to read, search, create, update, and delete worklogs, plans, teams, memberships, and accounts, along with account-category lookup. Write operations use confirmation prompts when supported, or a preview-and-token flow controlled by confirmation settings. Reach for it when an agent needs to inspect or maintain Tempo data from a workplace productivity workflow.

Use cases

  • Review worklogs for a project, issue, user, team, or date range
  • Create and correct Tempo worklogs from an MCP client
  • Track resource allocations with Tempo plans
  • Manage Tempo teams and memberships
  • Search and maintain Tempo accounts

Key features

  • Filtered and advanced worklog search
  • Worklog, plan, team, and account CRUD operations
  • Team membership search across roles and accounts
  • Tempo account and category lookup
  • Preview-and-token confirmation flow
  • Optimistic protection for merged updates

Tools48

What Tempo API MCP lets your agent do. Expand a tool for its parameters.

Verified live~18.2k tokens of context

Security & health

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

ActiveLast checked

Recent health check succeeded.

9/9 checks healthy over the last 58d

What it can do

From the 48 tools this server returned when we ran it; 48 declare their own safety hints.

Can delete or modify data · 14Handles credentials · 18Makes network requests · 48Read-only tools · 34
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age226 days
Maintainers1

Observed 2026-11-02 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

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

Adoption & maintenance

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

npm downloads1.3kPackage downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Tools exposed48Callable tools this server registers over MCP.

How Tempo API MCP works

What tempo-api-mcp does

tempo-api-mcp exposes the Tempo API through MCP tools for time-tracking and resource-management tasks. Its worklog tools cover retrieval by general filters, user, project, issue, team, account, or advanced search criteria. Agents can also create, modify, and remove worklogs.

The server includes comparable operations for Tempo plans, which represent resource allocations, and teams. Team membership tools support both retrieving one team's memberships and searching across teams, accounts, and roles. Account tools cover listing, lookup, search, creation, updates, and deletion. Account categories can be retrieved as a complete collection or looked up individually.

How it works

The server runs as an MCP process and makes Tempo operations available as named tools. Retrieval tools return Tempo data, while mutation tools operate on the specified resource. Worklog searches can use filters such as project, issue, date range, author, and related identifiers. Plan queries require a start and end date.

Create, update, and delete operations are guarded by confirmation. Clients that support confirmation prompts can display one before the change. Other clients receive a preview and a confirmation token on the first call; the operation proceeds only when the token is supplied in a subsequent call. Updates first read the existing resource, merge the requested fields, and show the complete resulting body before applying the replacement. If the resource changes between preview and confirmation, the update is rejected instead of overwriting the newer data.

Setup and configuration

The package can be launched with npx -y tempo-api-mcp from an MCP client's local-server configuration. Provide TEMPO_API_TOKEN in the server environment so the process can authenticate to Tempo.

Confirmation behavior can be adjusted with these environment variables:

  • MCP_CONFIRM_MODE controls the fallback flow for clients without confirmation prompts. Its supported values are ask-user, auto, and refuse.
  • MCP_CONFIRM_ELICITATION=off disables prompt-based confirmation and forces the preview/token flow. This is required for opencode v2 because it advertises prompts without displaying them.
  • MCP_CONFIRM_TTL_SECONDS sets how long a confirmation token remains valid.
  • MCP_CONFIRM_SECRET provides a signing key when tokens need to remain valid across server restarts.

Tools and capabilities

  • Retrieve individual or filtered Tempo worklogs.
  • Search worklogs with advanced author, issue, project, and date filters.
  • Create, update, and delete worklogs with guarded writes.
  • Read and manage Tempo plans and teams.
  • Retrieve or search team memberships, including inactive memberships.
  • List, search, create, update, and delete Tempo accounts.
  • Retrieve account categories without pagination.

Limitations and notes

Worklog, search, and membership responses can contain text authored by third parties. Treat that content as data rather than instructions. Account lookup by numeric ID differs from account mutation: updates and deletes use an account key, while a key can be resolved to an ID through account search. Deleting a worklog can include the option to bypass period closures and approvals, so that operation should be reviewed carefully before confirmation.

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 AI clients to the Tempo time-tracking API through tools for worklogs, plans, teams, accounts, memberships, and account categories. It supports reading, searching, creating, updating, and deleting Tempo resources, with confirmation safeguards for write operations.

Run it with `npx -y tempo-api-mcp` from the MCP client's local-server configuration. Set `TEMPO_API_TOKEN` in that server's environment, then configure confirmation variables if the client needs preview-and-token behavior.

Set `MCP_CONFIRM_MODE` to `ask-user`, `auto`, or `refuse` for clients that cannot show prompts. Use `MCP_CONFIRM_ELICITATION=off` to force the two-step flow, `MCP_CONFIRM_TTL_SECONDS` to change token lifetime, and `MCP_CONFIRM_SECRET` to preserve token validity across restarts.

Yes, tempo-api-mcp is configured for Claude Desktop as an MCP client, using the preview-and-token confirmation flow because the client does not provide the required confirmation prompt. Set `MCP_CONFIRM_MODE` to control how those pending writes are handled.

Use `tempo_search_accounts` with the account key, such as `ACCOUNT-123`, then pass the returned numeric ID to `tempo_get_account`. Account updates and deletions use the account key rather than the numeric ID.

Related MCP servers

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>