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 gradedqualityDmaintenanceEnables AI assistants to search, retrieve, and manage Confluence pages, and generate weekly status drafts from Jira activity.1-
- AlicenseBqualityAmaintenanceEnables 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.4355 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.18 npmMIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to manage Jira projects, issues, sprints, and boards via natural language.32 npmMIT
TDQS
B3.4/5.0
Scored across 48 tools
Disambiguation3/5
Most resources (plans, teams, accounts, timesheets) are clearly distinct, and descriptions cross-reference each other well (e.g. get_worklogs pointing to by_team/by_account, and search_accounts explaining key→id resolution). However, there are seven overlapping worklog readers (get_worklogs, by_issue, by_team, by_account, by_project, by_user, search_worklogs) whose boundaries blur, inviting misselection.
Naming Consistency5/5
Tool names uniformly use a tempo_ prefix with a predictable verb_noun pattern (get_, create_, update_, delete_, search_, submit_, approve_). Conventions are consistent throughout, with only the trivial tempo_healthcheck deviating.
Tool Count2/5
48 tools is heavy for the scope, and the count is inflated by the redundant worklog-read cluster and many single-resource getters. While the domain is broad, several tools could be consolidated via filtering parameters rather than dedicated endpoints.
Completeness4/5
Core domains (worklogs, plans, teams, accounts) have full CRUD, and the timesheet approval lifecycle is well-covered end to end (submit/approve/reject/reopen/recall plus status/reviewer/audit reads). Minor gaps remain: projects and account categories are read-only, and periods/work attributes are get-only.
Maintenance
ActivityActive
ResponsivenessResponsive