A
licenseA
qualityB
maintenanceEnables Claude to log, list, and delete Tempo worklogs against Jira issues, with automatic issue key resolution via the Jira REST API.
3
17 npm
MIT
Tempo Timesheet MCP Server
by nbhson
Related Servers
Alternatives to Tempo Timesheet MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables Claude to interact with 7pace Timetracker for Jira, supporting time logging, worklog queries, and summaries.6-
- AlicenseNot gradedqualityCmaintenanceEnables an AI coding agent to scan a day's git commits across work repositories and group them into Jira tickets, creating or updating them with estimates and logged time. It also surfaces actionable, categorized errors so an agent knows what failed and whether to retry.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage Jira Cloud instances, including creating and updating issues, managing sprints and projects, adding comments, tracking worklogs, and searching with presets.7 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with Jira and Confluence on Atlassian Cloud, supporting issue search, creation, updates, transitions, project listing, content search, page management, and comments.247 npm1MIT
- AlicenseBqualityAmaintenanceEnables AI assistants to manage Tempo timesheets and perform write operations such as create, update, delete, submit, approve, reject, reopen, and recall, with user confirmation safeguards.48188 npmMIT
TDQS
A3.7/5.0
Scored across 9 tools
Disambiguation3/5
The read tools (get_worklog, get_worklogs, get_week_summary) are clearly distinct, as are create vs update. However, tempo_preview_worklog is a superset of tempo_validate_worklog and tempo_check_duplicate (it returns validation results, duplicate matches, and the approval token), so three tools circle the same pre-write proposal and an agent can easily pick the wrong one or call validate/check_duplicate and then wrongly assume it is cleared to write.
Naming Consistency5/5
All tools follow a uniform <service>_<verb>_<noun> snake_case pattern (tempo_get_worklog, tempo_create_worklog, jira_search_issues), with the prefix consistently denoting the backing system. Verb choice is predictable across the CRUD/preview lifecycle.
Tool Count5/5
Nine tools is well within a healthy range and each maps to a concrete step: read (single/range/summary), lookup (jira search), pre-write safety (preview/validate/check_duplicate), and write (create/update). No obviously filler tools.
Completeness3/5
Create and update are covered with strong safety rails, and reads cover single, ranged, and aggregated views. The notable gap is deletion (explicitly absent in the MVP), and there is no tool to inspect an existing worklog's issue metadata or list a user's worklogs outside a date range, both of which limit recovery from mistakes.
Maintenance
ActivityMaintained
ResponsivenessNo issues