tempo-mcp-server MCP Server

A Model Context Protocol (MCP) server for managing Tempo worklogs in Jira. This server provides tools for tracking time and managing worklogs through Tempo's API, making it accessible through Claude, Cursor and other…

Local serverstdioMIT

What is the tempo-mcp-server MCP Server?

tempo-mcp-server source profile. From the maintainer documentation: “A Model Context Protocol (MCP) server for managing Tempo worklogs in Jira. This server provides tools for tracking time and managing worklogs through Tempo's API, making it accessible through Claude, Cursor and other MCP-compatible clients.”

Installation

The documented npm package is @ivelin-web/tempo-mcp-server. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.

Configuration values

The example declares TEMPO_API_TOKEN, JIRA_API_TOKEN, JIRA_EMAIL, JIRA_BASE_URL. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.

Source

Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

Tool	What it does
startDate	String (YYYY-MM-DD)
endDate	String (YYYY-MM-DD)
users	String[] (optional) — emails, display names, or accountIds
program	String (optional) — Tempo Program name or id
team	String (optional) — Tempo Team name or id
issueKey	String (e.g., "PROJECT-123")
timeSpentHours	Number (positive)
date	String (YYYY-MM-DD, optional)
startTime	String (HH:MM format, optional)
worklogEntries	Array of {
worklogId	String
minHoursPerDay	Number (optional) — override the per-day threshold;
groupBy	"issue" \| "account" \| "user" \| "day" \| "week" \| "month" (optional, default "issue")

How to install the tempo-mcp-server MCP Server

{
  "mcpServers": {
    "Jira_Tempo": {
      "command": "npx",
      "args": [
        "-y",
        "@ivelin-web/tempo-mcp-server"
      ],
      "env": {
        "TEMPO_API_TOKEN": "YOUR_TEMPO_API_TOKEN",
        "JIRA_API_TOKEN": "YOUR_JIRA_API_TOKEN",
        "JIRA_EMAIL": "your_email@example.com",
        "JIRA_BASE_URL": "https://your-org.atlassian.net"
      }
    }
  }
}

From the project documentation. Replace placeholders and example paths before connecting.

Configuration

Variable	Description	Required
TEMPO_API_TOKEN	Declared in the maintainer’s client configuration.	Yes
JIRA_API_TOKEN	Declared in the maintainer’s client configuration.	Optional
JIRA_EMAIL	Declared in the maintainer’s client configuration.	Optional
JIRA_BASE_URL	Declared in the maintainer’s client configuration.	Check documentation