Tempo MCP Server

@ivelin-web

Repository

Basic information

About Tempo MCP Server

MCP server for managing Tempo worklogs in Jira

#npm #automation #jira #typescript #js #mcp #ts #cursor #tempo#worklogs#mcp-server #mcp-tools #vibe-coding

Tempo MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "tempo-mcp-server": {
      "command": "npx",
      "args": [
        "wrangler",
        "login"
      ]
    }
  }
}

Tempo MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is Tempo MCP Server?

An MCP server for managing Tempo worklogs in Jira. It provides tools to track time and manage worklogs through Tempo’s API, accessible via Claude, Cursor, and other MCP-compatible clients.

How to use Tempo MCP Server?

Use one of three modes: deploy remotely on Cloudflare Workers (no install, each user gets a personal URL), run directly with npx, or clone the repository locally. Configure environment variables TEMPO_API_TOKEN, JIRA_API_TOKEN, JIRA_EMAIL, and JIRA_BASE_URL.

Key features of Tempo MCP Server

Retrieve worklogs for a date range
Create, edit, and delete worklogs
Bulk create multiple worklogs in one operation
Missing days report (respects holidays via Tempo user-schedule)
Worklog analytics aggregated by issue, account, day, week, or month

Use cases of Tempo MCP Server

Log time against Jira issues directly from Claude conversations
Generate missing worklog reports to find under-logged working days
Analyze time distribution across projects and accounts
Automate bulk worklog creation for repeated time entries

Frequently asked questions

What authentication methods does Tempo MCP Server support?

Basic auth (classic API token + email) is used for remote/Cloudflare deployment; OAuth 2.0 PKCE is supported only in stdio (local) modes.

What are the runtime requirements?

Node.js 18+ (LTS recommended) for local stdio modes. Remote mode runs on Cloudflare Workers with no Node dependency at runtime.

Where are user credentials stored in remote mode?

Credentials are AES-GCM encrypted with an `ENCRYPTION_KEY` and stored in Cloudflare KV under per-user keys. The personal MCP URL carries the credential — treat it like a password.

Can I host this server myself?

Yes. Fork the repository and deploy to Cloudflare Workers. Free-tier Workers (100k requests/day) and KV (100k reads/day) are sufficient.

Are there known transport or rate limits?

Remote mode uses Cloudflare’s native Rate Limiting binding (5 POST/min on `/setup`). Per-IP rate limits apply. The free Workers plan has a 50ms CPU limit per request but is I/O‑bound, so it works comfortably.

Comments

More Other MCP servers

Handl

Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.

YOUB

Connect your AI assistant to your own YOUB endurance training account. Read recorded activities with full analysis, planned sessions, race goals, wellness (HRV, sleep, resting HR) and your athletic profile. Create or mov

PickFu MCP

PickFu MCP is a Model Context Protocol (MCP) server that connects AI assistants, developers, marketers, product managers, and AI agents to PickFu's consumer research platform. It enables users to create surveys, conduct

🚀 Model Context Protocol (MCP) Curriculum for Beginners

microsoft

This open-source curriculum introduces the fundamentals of Model Context Protocol (MCP) through real-world, cross-language examples in .NET, Java, TypeScript, JavaScript, Rust and Python. Designed for developers, it focuses on practical techniques for building modular, scalable,

16.7K

Codelf

unbug

A search tool helps dev to solve the naming things problem.

14.2K