7Pace-Connector
Related Servers
Alternatives to 7Pace-Connector
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Claude to log, list, and delete Tempo worklogs against Jira issues, with automatic issue key resolution via the Jira REST API.311 npmMIT
- AlicenseAqualityDmaintenanceEnables Claude to interact with Toggl Track for time tracking, including starting/stopping timers, viewing current entries, and summarizing time by project via natural language.713 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables starting and stopping Clockify timers, checking the currently running timer, and viewing recent time entries via Claude.MIT
- FlicenseNot gradedqualityDmaintenanceEnables logging time to Tempo (Jira time tracker) via natural language in Claude Desktop or OpenCode.-
- AlicenseAqualityBmaintenanceEnables Claude to manage ATimeLogger time tracking: start/stop/pause activities, log intervals, and get reports via natural language.1035 npm18MIT
- FlicenseBqualityDmaintenanceConnects Claude to Jira, allowing users to query tasks, log work, add comments, and execute JQL queries through conversational AI.22-
TDQS
Scored across 6 tools
Each tool has a distinct purpose: listing, getting by issue, deleting, creating, updating, and summarizing work logs. There is no ambiguity between them.
Most tools follow a verb_noun pattern (list_worklogs, get_worklog, delete_worklog, update_worklog). 'log_time' and 'summarize_time' use 'time' instead of 'worklog', but the pattern is still consistent and clear.
Six tools cover the essential operations for work log management without being excessive. The count is well-suited to the server's purpose.
CRUD operations are covered (create via log_time, read via list_worklogs and get_worklog, update, delete) plus a summary function. A direct get-by-ID is missing, but list_worklogs and get_worklog cover retrieval adequately.