No user-submitted related servers found.
Scored across 12 tools
Most tools map to a distinct resource or action, but there is some overlap: keeping_add_entry and keeping_start_timer both create time entries, and keeping_timer_status overlaps with keeping_list_entries as a read surface. The detailed descriptions and dry-run gates help an agent disambiguate, but the boundaries are slightly fuzzy.
All tools share a keeping_ prefix and use snake_case, with clear action_object names like add_entry, delete_entry, and stop_timer. The main inconsistency is that resource listers are split between noun-only names (keeping_organisations, keeping_projects, keeping_tasks) and verb-based names (keeping_list_entries), while keeping_timer_status is neither a verb pattern nor a simple resource name.
12 tools is well within the target range and maps cleanly to the server's purpose: identity and org context, resource lookups, time-entry CRUD, and timer lifecycle. Each tool has a clear role, with no obvious filler or redundant duplicates.
The tool surface covers the core Keeping workflows: list/create/update/delete time entries, start/stop/resume timers, and resolve org/project/task context. It also handles feature-fag disables and provides dry-run previews for destuctive and mutating operations, so agents do not hit dead ends. Missing write access to projects/tasks is not an obvious gap for a time-tracking MCP server.