Tempo MCP Server

MCP server for managing Tempo worklogs in Jira

Catalog onlyCatalog onlySTDIO

Overview

Tempo MCP Server is a Model Context Protocol (MCP) server designed for managing Tempo worklogs in Jira, providing tools for tracking time and managing worklogs through Tempo's API.

You can use the server via NPX without installation or by cloning the repository for local development. For NPX, run the command with your API tokens and Jira details. For local usage, configure the wrapper script with your credentials and run it.

Retrieve worklogs for specific date ranges - Create, edit, and delete worklogs - Bulk create multiple worklogs in one operation - Integration with MCP-compatible clients like Claude and Cursor

Logging time against Jira issues for project management
Bulk updating worklogs for multiple tasks
Integrating with other tools for enhanced productivity

Add to your AI client

Use these steps to connect Tempo MCP Server in Cursor, Claude, VS Code, and other MCP-compatible apps. The same JSON appears in the Use with menu above for one-click copy.

Cursor

Add this to your .cursor/mcp.json file in your project root, then restart Cursor.

.cursor/mcp.json

{
  "mcpServers": {
    "tempo-mcp-server-ivelin-web": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-tempo-mcp-server-ivelin-web"
      ]
    }
  }
}

Claude Desktop

Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.

~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)

{
  "mcpServers": {
    "tempo-mcp-server-ivelin-web": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-tempo-mcp-server-ivelin-web"
      ]
    }
  }
}

Claude Code

Add this to your project's .mcp.json file. Claude Code will detect it automatically.

.mcp.json (project root)

{
  "mcpServers": {
    "tempo-mcp-server-ivelin-web": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-tempo-mcp-server-ivelin-web"
      ]
    }
  }
}

VS Code (Copilot)

Add this to your .vscode/mcp.json file. Requires the GitHub Copilot extension with MCP support enabled.

.vscode/mcp.json

{
  "servers": {
    "tempo-mcp-server-ivelin-web": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-tempo-mcp-server-ivelin-web"
      ]
    }
  }
}

Windsurf

Add this to your Windsurf MCP config file, then restart Windsurf.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "tempo-mcp-server-ivelin-web": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-tempo-mcp-server-ivelin-web"
      ]
    }
  }
}

Cline

Open Cline settings, navigate to MCP Servers, and add this server configuration.

Cline MCP Settings (via UI)

{
  "mcpServers": {
    "tempo-mcp-server-ivelin-web": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-tempo-mcp-server-ivelin-web"
      ]
    }
  }
}

FAQ

What are the system requirements?

Node.js 18+, a Jira Cloud instance, and API tokens for Tempo and Jira are required.

Is there a recommended way to use the server?

Yes, using NPX is recommended for most users for ease of use.

How can I troubleshoot issues?

Check environment variables, API token permissions, and use the inspector for debugging.

Developer tools