F
licenseA
qualityC
maintenanceMCP server for logging and checking Jira Cloud worklogs from AI agents such as Claude Code, Claude Desktop, Cursor, or any MCP client that supports stdio.
7
1
-
Tempo MCP Server
by ivelin-web
Related Servers
Alternatives to Tempo MCP Server
No user-submitted related servers found.
Related Servers
Tempo Filler MCP Serverofficial
AlicenseAqualityDmaintenanceA Model Context Protocol server enabling AI assistants to interact with Tempo's time tracking system in JIRA for worklog retrieval, creation, and management.514 npm5ISC- FlicenseNot gradedqualityCmaintenanceMCP Server to log time and view Jira statistics directly from Cursor IDE.-
- AlicenseNot gradedqualityDmaintenanceA Jira and Tempo Cloud MCP server with file-based profiles for multi-site access, enabling natural language interaction with issue tracking, project management, and Tempo worklogs via generic REST tools.9 npmISC
- AlicenseNot gradedqualityDmaintenanceA work management MCP server for Claude Code that integrates with Jira Cloud to handle sprints, tickets, and project tracking via natural language.50 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceAn MCP server that enables interaction with the Jira API to retrieve time-tracking information. It allows users to fetch their logged work hours and specific task details for the current week.9 npm-
TDQS
C2.1/5.0
Scored across 7 tools
Disambiguation2/5
Four of seven tools (bulkCreateWorklogs, createWorklog, deleteWorklog, editWorklog) lack descriptions, making it hard for an agent to distinguish between them. The three described analytical tools are well-differentiated, but the unknown mutation tools create significant ambiguity.
Naming Consistency2/5
Naming is inconsistent: uses both 'get' and 'retrieve' prefixes, and mixes singular 'Worklog' with plural 'Worklogs' (e.g., createWorklog vs bulkCreateWorklogs). This lack of pattern reduces predictability.
Tool Count4/5
With 7 tools, the server covers core CRUD and analytical operations for worklog management. The count is appropriate for the scope, though the missing descriptions for half the tools detract from its usability.
Completeness3/5
Basic CRUD (create single/bulk, delete, edit) and analytics (retrieve, analytics, missing days) are present, suggesting reasonable coverage. However, the lack of descriptions makes it unclear if there are gaps like a 'get by ID' or bulk delete.
Maintenance
ActivityStale
ResponsivenessNo issues