A
licenseA
qualityB
maintenanceEnables tracking work time with start/stop timers, logging entries, and generating reports.
4
8 npm
41 PyPI
MIT
berichtsheft-mcp
Related Servers
Alternatives to berichtsheft-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceLogs work entries to daily Markdown files and sends summaries to Telegram automatically at 11 PM or on demand.-
- FlicenseNot gradedqualityBmaintenanceAutomatically collects work data from Git history and Claude Code session logs to generate daily worklog drafts, and registers approved logs to the Waple HR platform.-
- AlicenseBqualityCmaintenanceEnables local engineering workflow management by consolidating tickets, QA evidence, time tracking, root cause investigation, knowledge, and reporting into a single SQLite database, allowing generation of complete ticket packages for handoffs, dailies, or career evidence.233 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables recording, querying, and summarizing daily work entries with tags using a local SQLite database. Supports work logging, search, timeline queries, tag management, and automated reminders for tracking daily tasks.-
- FlicenseNot gradedqualityDmaintenanceEnables adding GPS goals and logging time directly from Claude Desktop, with support for bulk backfill and session management.-
TDQS
A4.1/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct roles: collect_week reads raw session data, while fill_week writes summarized bullet points into the report book. Their inverse read/write purposes are unambiguous and complementary.
Naming Consistency5/5
Both names follow the same verb_noun pattern (collect_week, fill_week) and share the same noun, making the set predictable and easy to scan.
Tool Count3/5
With only 2 tools, the surface feels thin even for a narrow weekly-report workflow; a read/inspect tool for existing entries or an update capability would help justify a slightly larger set.
Completeness3/5
The core collect-then-fill lifecycle is covered, but there is no way to read back what has already been entered, update non-duplicate existing lines, or delete entries. These are notable gaps, though the dry_run and duplicate-skipping behavior partially mitigates them.
Maintenance
ActivityMaintained
ResponsivenessNo issues