A
licenseNot graded
qualityB
maintenanceEnables AI assistants to manage Jira issues and Confluence pages, including creating, updating, searching, commenting, and transitioning work items through natural language.
MIT
tempo-api-mcp
by chrischall
Related Servers
Alternatives to tempo-api-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to search, retrieve, and manage Confluence pages, and generate weekly status drafts from Jira activity.1-
- AlicenseBqualityBmaintenanceEnables AI assistants to access and manage Jira boards, sprints, epics, issues, JQL searches, transitions, comments, worklogs, projects, users, and any REST endpoint across Jira Cloud and Data Center.4348 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to create, search, update, and manage Jira issues and Confluence pages via natural language through the Atlassian Cloud REST APIs.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Jira Cloud issues, supporting create, read, update, delete, search, and transition operations via natural language.15 npmMIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to manage Jira projects, issues, sprints, and boards via natural language.60 npmMIT
TDQS
B3.4/5.0
Scored across 48 tools
Disambiguation3/5
Most tools have clear verb_noun names, but the worklog retrieval family is oversized and overlapping: tempo_get_worklogs already supports filtering by project/issue, making tempo_get_worklogs_by_project and tempo_get_worklogs_by_issue redundant, and tempo_search_worklogs overlaps with both. Descriptions help distinguish the by_team/by_account variants, but an agent could easily misselect.
Naming Consistency4/5
All tools follow a consistent tempo_<verb>_<object> pattern in snake_case, which is strong. Minor deviations like tempo_get_timesheet_approvals_waiting (odd phrasing) and singular/plural inconsistencies (approval vs approvals) prevent a perfect score.
Tool Count2/5
48 tools is far beyond the typical 3-15 for a coherent MCP server and above the 25+ threshold. The worklog retrieval family alone has 7 near-overlapping tools, inflating the count. While Tempo is a broad domain, the surface could be consolidated.
Completeness3/5
The server covers CRUD for worklogs, plans, teams, and accounts, plus a full timesheet approval workflow. However, it provides no way to create, update, or delete team memberships, and only read access to account categories, roles, and periods, which are notable gaps for a supposedly comprehensive Tempo API surface.
Maintenance
ActivityActive
ResponsivenessResponsive