timetree-worklog-mcp
Related Servers
Alternatives to timetree-worklog-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables local-first logging of daily activities and generation of daily summaries, weekly article ideas, and platform-specific social posts via Claude, storing everything in a single SQLite file.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables developers to maintain a local engineering journal, log work manually or from git history, and let AI assistants query, summarize, and draft standup updates, changelogs, and retro notes.MIT
- 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.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to maintain a persistent developer logbook with notes, TODOs, reminders, code TODO scanning, and full-text search, while keeping all data local and optionally syncing with Obsidian.190 npm1MIT
- FlicenseNot gradedqualityCmaintenanceLogs work entries to daily Markdown files and sends summaries to Telegram automatically at 11 PM or on demand.-

workhorse-ai-mcpofficial
AlicenseNot gradedqualityBmaintenanceProvides an append-only SQLite journal for orchestrator/worker AI workflows, enabling delegation, reporting, verification, and tracking of tasks with built-in search and optional cloud sync.106 npmMIT
TDQS
Scored across 9 tools
Each tool maps to a distinct stage of the worklog lifecycle (preview, save, get, search, publish, sync status, retry), and descriptions clarify the read-only vs remote-write boundaries. Minor overlap between preview_daily_worklog and save_worklog, and between get_sync_status and search_worklogs' sync-state filtering, but the descriptions disambiguate well.
All tools use snake_case verb_noun patterns consistently (list_calendars, save_worklog, publish_worklog, retry_pending_sync). Minor deviation: 'daily' appears in preview_daily_worklog and get_daily_worklog but not in save_worklog, slightly breaking the resource-naming symmetry.
Nine tools form a tight, well-scoped set covering the full local-to-remote worklog flow. Every tool has a clear, non-redundant role with no filler.
Covers calendar discovery, local preview/save/read/search, reporting, publishing, sync status and retry — strong lifecycle coverage. Gaps exist (no delete/archive removal for local worklogs, no unpublish or update of published memos), but these appear to be intentional safety omissions rather than dead ends.