timescribe-mcp
Related Servers
Alternatives to timescribe-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables logging, listing, updating, deleting, and summarizing timesheet entries, starting and stopping timers, checking timer status, and exporting time data through natural language, backed by a local SQLite database.7 npmMIT
- AlicenseAqualityDmaintenanceProvides Claude with read-only access to local development databases (Postgres, MySQL, SQLite) to inspect schemas, run SELECT queries, and explain query plans without leaving the conversation.5MIT
- AlicenseAqualityAmaintenanceProvides Claude access to RescueTime productivity data, enabling users to query daily summaries, top activities, category breakdowns, and productivity trends through natural language.5MIT
- AlicenseNot gradedqualityDmaintenanceEnables natural language interaction with local SQLite databases through Claude Desktop, translating plain English queries into SQL for data analysis and exploration.3MIT
- -licenseAqualityNot gradedmaintenanceEnables natural language time tracking through Claude with markdown file storage. Supports multi-company tracking, flexible time parsing, auto-calculated summaries, and commitment warnings all through conversational input.1-
- AlicenseAqualityCmaintenanceEnables Claude Desktop and Claude Code to read locally synced Fitbit Air health data — scores, trends, sleep, activity, running and body age — run read-only SQL against it, and keep a journal and coach notes on the user's Mac. It also offers profile edits, a refresh tool, and guided prompts such as morning check-ins, weekly reviews, race planning and score explanations.172Apache 2.0
TDQS
Scored across 3 tools
Each tool targets a distinct level of the domain: projects, individual entries, and aggregated summaries. The descriptions explicitly disambiguate by telling the agent when to use list_entries vs get_time_summary, eliminating overlap.
All three names follow a clean snake_case verb_noun pattern (list_projects, list_entries, get_time_summary), with list_* for collections and get_* for a computed value used predictably.
Three tools is at the low end but each earns its place and maps to a genuinely different question (what projects exist, what happened in detail, what the totals are). A read-only analytics surface this tight is defensible, though it leaves little room for growth.
The set covers the read/analysis lifecycle well but is entirely read-only: there is no way to create, edit, or delete entries, manage projects, or start/stop the running timer that get_time_summary reports. Notable gaps if the agent is expected to do more than report on time data.