Tempo MCP Server

MCP server for Tempo — the leading time tracking and resource planning app for Jira. Enables AI agents to log work, query worklogs, analyze time spent on Jira issues, and generate time reports through Tempo's API. Integrates Tempo time tracking into AI-assisted project management and billing workflows.

Evaluated Mar 06, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Productivity tempo jira time-tracking atlassian mcp-server worklogs project-management
⚙ Agent Friendliness
72
/ 100
Can an agent use this?
🔒 Security
82
/ 100
Is it safe for agents?
⚡ Reliability
68
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
68
Documentation
70
Error Messages
68
Auth Simplicity
85
Rate Limits
78

🔒 Security

TLS Enforcement
95
Auth Strength
82
Scope Granularity
75
Dep. Hygiene
72
Secret Handling
82

Employee time and billing data. API token required. Tempo SOC2 compliant. Review agent permissions for worklog creation carefully.

⚡ Reliability

Uptime/SLA
72
Version Stability
68
Breaking Changes
65
Error Recovery
68
AF Security Reliability

Best When

A software team using Jira + Tempo for time tracking wants AI agents to automate worklog entry, queries, and time reporting — reducing manual time logging overhead.

Avoid When

You use native Jira time tracking without Tempo, or use different time tracking tools (Harvest, Toggl, etc.) — Tempo is a specific Jira add-on with its own API.

Use Cases

  • Logging time entries to Jira issues from development workflow agents
  • Querying team worklog summaries for project reporting agents
  • Analyzing time allocation across projects from resource planning agents
  • Generating time reports for billing agents from Tempo worklog data

Not For

  • Teams not using Tempo (Jira-specific time tracking add-on)
  • Basic Jira time tracking without Tempo add-on
  • Non-Atlassian project management platforms

Interface

REST API
Yes
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: api_key
OAuth: No Scopes: No

Tempo API token required. Generated from Tempo app settings. Scoped to the Tempo workspace and user permissions.

Pricing

Model: usage_based
Free tier: No
Requires CC: Yes

Tempo is a paid Jira add-on. MCP server is free open source by ofalvai. Requires active Tempo subscription.

Agent Metadata

Pagination
cursor
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • Tempo requires existing Jira issue keys — agents need Jira context to log time correctly
  • Worklog data may contain billable hours — billing consequences if agents log time incorrectly
  • Tempo API v3 and v4 differ — ensure server uses correct version for your Tempo instance
  • Community server by ofalvai — works well but follows Tempo API updates with some lag

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Tempo MCP Server.

$99

Scores are editorial opinions as of 2026-03-06.

5190
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered