ActivityWatch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| activitywatch_list_bucketsB | List all ActivityWatch buckets with optional type filtering |
| activitywatch_query_examplesB | Get examples of properly formatted queries for the ActivityWatch MCP server |
| activitywatch_run_queryC | Run a query in ActivityWatch's query language |
| activitywatch_get_eventsC | Get raw events from an ActivityWatch bucket |
| activitywatch_get_settingsB | Get ActivityWatch settings. Can retrieve all settings or a specific key if provided. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.