ActivityWatch MCP Server
Related Servers
Alternatives to ActivityWatch MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol (MCP) server that connects to ActivityWatch, allowing LLMs like Claude to interact with your time tracking data.4MIT
- FlicenseNot gradedqualityFmaintenanceConnects AI assistants to ActivityWatch for real-time computer activity awareness and time tracking analysis. Enables natural language queries about app usage, browsing history, and productivity patterns through high-level tools without requiring AQL syntax knowledge.-
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to query and analyze ActivityWatch time tracking data, including window activity, web browsing, and category management with natural language time periods and automatic data aggregation.12GPL 3.0
- FlicenseDqualityDmaintenanceIntegrates Rize.io's time tracking and productivity analytics with AI assistants via the Model Context Protocol, enabling natural language queries about productivity metrics, focus sessions, and project management.84-
- FlicenseNot gradedqualityFmaintenanceA Model Context Protocol desktop extension that allows Claude to query and interact with custom SQL databases in real-time during conversations.1-
- AlicenseNot gradedqualityCmaintenanceAn implementation of Model Context Protocol (MCP) that allows users to interact with TripleWhale's e-commerce analytics platform using natural language queries through Claude Desktop.106 npm7MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: get_events retrieves raw event data, get_settings accesses configuration, list_buckets enumerates available data containers, query_examples provides documentation, and run_query executes queries. There is no overlap in functionality that would cause agent confusion.
All tools follow a consistent 'activitywatch_verb_noun' pattern with snake_case throughout. The verbs (get, list, run) are appropriately descriptive and maintain a uniform naming convention across all five tools.
With 5 tools, this server is well-scoped for interacting with ActivityWatch data. The count is appropriate for the domain, covering core operations like data retrieval, configuration access, and query execution without being overwhelming or insufficient.
The toolset provides solid coverage for querying and inspecting ActivityWatch data, including examples for guidance. A minor gap exists in write operations (e.g., creating or modifying buckets/events), but the available tools support most common read and query workflows effectively.