activitywatch-mcp-server
The ActivityWatch MCP Server is designed to integrate ActivityWatch time tracking data with LLMs such as Claude, allowing users to access and query their tracking data seamlessly. It supports a range of functionalities including listing buckets, running queries, retrieving raw events, and accessing configuration settings.
What is the default API endpoint for ActivityWatch?
The server connects to the ActivityWatch API at http://localhost:5600 by default.
What should I do if ActivityWatch is not running?
Ensure that ActivityWatch is running and accessible at http://localhost:5600 to avoid connection errors.
How can I troubleshoot query errors?
Check your query syntax, ensure bucket IDs are correct, verify time periods contain data, and check ActivityWatch logs for more details.
What is a common formatting issue with queries?
A common issue is splitting query statements into separate array elements instead of combining them into a single string within the array.
How can I contribute to the ActivityWatch MCP Server?
Contributions are welcome! Please feel free to submit a Pull Request.