weekly-records
Related Servers
Alternatives to weekly-records
No user-submitted related servers found.
Related Servers
- 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.3 npm-
- FlicenseNot gradedqualityDmaintenanceEnables generating a workday schedule and 8-hour timesheet from selected Jira, Outlook, and Teams context via a read-only MCP tool.-
- AlicenseAqualityDmaintenanceEnables employee time tracking with clock-in/out, workday checking, and time log retrieval via MCP tools.41MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying WakaTime coding activity data including summaries, stats, durations, and commits through an MCP server integrated with Pipeworx gateway.MIT
- AlicenseNot gradedqualityAmaintenanceRead-only MCP server for Clockify time tracking, exposing 60 raw read tools and five workflows for status, workspace overview, and review of days/weeks.MIT
- FlicenseNot gradedqualityBmaintenanceA read-only MCP server that lets team members access Simplified HR Work Journal entries and team reports through Claude, with permissions enforced by the existing Work Journal API.-
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or misselection. The tool's purpose is clearly defined and distinct by default.
The single tool name follows a clear verb_noun pattern (get_weekly_records) and is descriptive. Consistency is not an issue with only one tool.
A single tool is too few for a server, even if the scope is narrow. The rubric explicitly marks one tool as too few, and this feels thin for a dedicated 'weekly-records' server.
The tool fully covers the read operation for weekly records, including both week-one and week-two. However, it only retrieves data and does not offer any related operations (e.g., listing weeks, summarizing), though the stated purpose is read-only.