de en es ja ko ru zh

ActivityWatch MCP Server

Name: ActivityWatch MCP Server
Author: 8bitgentleman

by 8bitgentleman

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Servidor MCP de ActivityWatch

Un servidor del Protocolo de Contexto de Modelos (MCP) que se conecta a ActivityWatch, permitiendo que LLMs como Claude interactúen con tus datos de seguimiento de tiempo.

Características

Listar buckets: Ver todos los buckets de ActivityWatch disponibles
Ejecutar consultas: Ejecutar potentes consultas AQL (ActivityWatch Query Language)
Obtener eventos sin procesar: Recuperar eventos directamente de cualquier bucket
Obtener ajustes: Acceder a los ajustes de configuración de ActivityWatch

Related MCP server: Paprika SQL MCP Server

Instalación

Puedes instalar el servidor MCP de ActivityWatch desde npm o compilándolo tú mismo.

Instalación desde npm (próximamente)

# Global installation
npm install -g activitywatch-mcp-server

# Or install locally
npm install activitywatch-mcp-server

Compilación desde el código fuente

Clona este repositorio:

git clone https://github.com/8bitgentleman/activitywatch-mcp-server.git
cd activitywatch-mcp-server

Instala las dependencias:
```
npm install
```
Compila el proyecto:
```
npm run build
```

Requisitos previos

ActivityWatch instalado y en ejecución
Node.js (v14 o superior)
Claude for Desktop (o cualquier otro cliente MCP)

Uso

Uso con Claude for Desktop

Abre tu archivo de configuración de Claude for Desktop:
- Windows: %APPDATA%\Claude\claude_desktop_config.json
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Añade la configuración del servidor MCP:

{
"mcpServers": {
    "activitywatch": {
    "command": "activitywatch-mcp-server",
    "args": []
    }
}
}

Si lo compilaste desde el código fuente, usa:

{
"mcpServers": {
    "activitywatch": {
    "command": "node",
    "args": ["/path/to/activitywatch-mcp-server/dist/index.js"]
    }
}
}

Reinicia Claude for Desktop
Busca el icono de MCP en la interfaz de Claude para confirmar que funciona

Uso de un contenedor podman sin root en Linux con Gemini CLI

Asegúrate de compilar la imagen primero con:

version=$(npm pkg get version | tr -d '"')
podman build . -t activitywatch-mcp-server:${version}

Este ejemplo utiliza la anulación para cuando Activity Watch no está disponible en 127.0.0.1 (ver la siguiente sección). Si no es necesario, puedes omitir la variable de entorno AW_API_BASE.

{
  "mcpServers": {
    "activitywatch-mcp-server": {
      "command": "/usr/bin/podman",
      "args": [
        "run",
        "--rm",
        "--interactive",
        "--userns=keep-id",
        "-e",
        "AW_API_BASE",
        "localhost/activitywatch-mcp-server:1.2.1"
      ],
      "env": {
        "AW_API_BASE": "http://mydesktop.local:5600/api/0"
      }
    }
  }
}

Anular el host/puerto del servidor de ActivityWatch

Si deseas ejecutar este servidor MCP desde dentro del Subsistema de Windows para Linux, por ejemplo dentro de un contenedor, el servidor AW que se ejecuta en Windows no estará disponible en 127.0.0.1. Para anular la conexión local estándar, utiliza la variable de entorno AW_API_BASE o el flag --aw-api-base, como se muestra a continuación:

# Using environment variable
export AW_API_BASE=http://mydesktop.local:5600/api/0
node dist/index.js

# Or using command-line flag
node dist/index.js --aw-api-base=http://mydesktop.local:5600/api/0

NOTA: El servidor AW puede ser exigente con el nombre utilizado para conectarse a él, pero aceptará un nombre que coincida con el nombre del equipo donde se está ejecutando con un sufijo .local.

Ejemplos de consultas

Aquí tienes algunas consultas de ejemplo que puedes probar en Claude:

Listar todos tus buckets: "¿Qué buckets de ActivityWatch tengo?"
Obtener resumen de uso de aplicaciones: "¿Puedes mostrarme qué aplicaciones he usado más hoy?"
Ver historial de navegación: "¿Qué sitios web he visitado más hoy?"
Comprobar productividad: "¿Cuánto tiempo he pasado en aplicaciones de productividad hoy?"
Ver ajustes: "¿Cuáles son mis ajustes de ActivityWatch?" o "¿Puedes comprobar un ajuste específico en ActivityWatch?"

Herramientas disponibles

list-buckets

Lista todos los buckets de ActivityWatch disponibles con filtrado de tipo opcional.

Parámetros:

type (opcional): Filtrar buckets por tipo (ej. "window", "web", "afk")
includeData (opcional): Incluir datos del bucket en la respuesta

run-query

Ejecuta una consulta en el lenguaje de consulta de ActivityWatch (AQL).

Parámetros:

timeperiods: Periodo(s) de tiempo a consultar formateado como una matriz de cadenas. Para rangos de fechas, usa el formato: ["2024-10-28/2024-10-29"]
query: Matriz de sentencias de consulta en el lenguaje de consulta de ActivityWatch, donde cada elemento es una consulta completa con sentencias separadas por puntos y coma
name (opcional): Nombre para la consulta (usado para caché)

IMPORTANTE: Cada cadena de consulta debe contener una consulta completa con múltiples sentencias separadas por puntos y coma.

Formato de solicitud de ejemplo:

{
  "timeperiods": ["2024-10-28/2024-10-29"],
  "query": ["events = query_bucket('aw-watcher-window_UNI-qUxy6XHnLkk'); RETURN = events;"]
}

Ten en cuenta que:

timeperiods debe tener rangos de fechas preformateados con barras diagonales
Cada elemento en la matriz query es una consulta completa con todas las sentencias

get-events

Obtener eventos sin procesar de un bucket de ActivityWatch.

Parámetros:

bucketId: ID del bucket del cual obtener eventos
start (opcional): Fecha/hora de inicio en formato ISO
end (opcional): Fecha/hora de fin en formato ISO
limit (opcional): Número máximo de eventos a devolver

get-settings

Obtener ajustes de ActivityWatch desde el servidor.

Parámetros:

key (opcional): Obtener una clave de ajuste específica en lugar de todos los ajustes

Ejemplos de lenguaje de consulta

ActivityWatch utiliza un lenguaje de consulta sencillo. Aquí hay algunos patrones comunes:

// Get window events
window_events = query_bucket(find_bucket("aw-watcher-window_"));
RETURN = window_events;

// Get only when not AFK
afk_events = query_bucket(find_bucket("aw-watcher-afk_"));
not_afk = filter_keyvals(afk_events, "status", ["not-afk"]);
window_events = filter_period_intersect(window_events, not_afk);
RETURN = window_events;

// Group by app
window_events = query_bucket(find_bucket("aw-watcher-window_"));
events_by_app = merge_events_by_keys(window_events, ["app"]);
RETURN = sort_by_duration(events_by_app);

// Filter by app name
window_events = query_bucket(find_bucket("aw-watcher-window_"));
code_events = filter_keyvals(window_events, "app", ["Code"]);
RETURN = code_events;

Configuración

El servidor se conecta a la API de ActivityWatch en http://localhost:5600 por defecto. Si tu instancia de ActivityWatch se ejecuta en un host o puerto diferente, puedes anularlo como se describe en la sección Anular el host/puerto del servidor de ActivityWatch anterior.

Solución de problemas

ActivityWatch no está en ejecución

Si ActivityWatch no está en ejecución, el servidor mostrará errores de conexión. Asegúrate de que ActivityWatch esté en ejecución y accesible en la dirección de host/puerto especificada (http://localhost:5600 a menos que lo hayas anulado).

Errores de consulta

Si encuentras errores de consulta:

Comprueba la sintaxis de tu consulta
Asegúrate de que los IDs de los buckets sean correctos
Verifica que los periodos de tiempo contengan datos
Comprueba los registros de ActivityWatch para más detalles

Problemas de formato de consulta en Claude/MCP

Si Claude informa de errores al ejecutar consultas a través de este servidor MCP, probablemente se deba a problemas de formato. Asegúrate de que tu consulta siga este formato exacto en tus prompts:

{
  "timeperiods": ["2024-10-28/2024-10-29"],
  "query": ["events = query_bucket('aw-watcher-window_UNI-qUxy6XHnLkk'); RETURN = events;"]
}

Problemas comunes:

Periodos de tiempo no formateados correctamente (debería ser "inicio/fin" en una sola cadena dentro de una matriz)
Sentencias de consulta divididas en elementos de matriz separados en lugar de combinarse en una sola cadena

El problema de formato más común

El error más frecuente es cuando Claude divide cada sentencia de consulta en su propio elemento de matriz como este:

{
  "query": [
    "browser_events = query_bucket('aw-watcher-web');",
    "afk_events = query_bucket('aw-watcher-afk');",
    "RETURN = events;"
  ],
  "timeperiods": ["2024-10-28/2024-10-29"]
}

Esto es INCORRECTO. En su lugar, todas las sentencias deben estar en una sola cadena dentro de la matriz:

{
  "timeperiods": ["2024-10-28/2024-10-29"],
  "query": ["browser_events = query_bucket('aw-watcher-web'); afk_events = query_bucket('aw-watcher-afk'); RETURN = events;"]
}

Al pedirle cosas a Claude

Cuando le pidas cosas a Claude, sé muy explícito sobre el formato y usa ejemplos. Por ejemplo, di:

"Ejecuta una consulta con timeperiods como ["2024-10-28/2024-10-29"] y query como ["sentencia1; sentencia2; RETURN = resultado;"]. Importante: Asegúrate de que TODAS las sentencias de consulta estén en una sola cadena dentro de la matriz, no divididas en elementos de matriz separados."

Contribución

¡Las contribuciones son bienvenidas! Por favor, siéntete libre de enviar un Pull Request.

Licencia

MIT

Available Tools

5 tools

activitywatch_get_eventsC

Get raw events from an ActivityWatch bucket

ParametersJSON Schema

Name	Required	Description
`bucketId`	Yes	ID of the bucket to fetch events from
`limit`	No	Maximum number of events to return (default: 100)
`start`	No	Start date/time in ISO format (e.g. '2024-02-01T00:00:00Z')
`end`	No	End date/time in ISO format (e.g. '2024-02-28T23:59:59Z')

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It doesn't mention whether this is a read-only operation, if it requires authentication, potential rate limits, error conditions, or what format the 'raw events' are returned in. The description is functionally adequate but lacks important operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise - a single sentence that communicates the essential purpose without any wasted words. It's front-loaded with the core functionality and doesn't include unnecessary elaboration, making it efficient for quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 4 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what 'raw events' means in terms of data structure, doesn't mention any limitations or constraints, and provides no context about the ActivityWatch system. The agent would need to guess about the return format and operational characteristics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the input schema already documents all 4 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline expectation but doesn't provide extra value regarding parameter usage or semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get raw events') and resource ('from an ActivityWatch bucket'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'activitywatch_query_examples' or 'activitywatch_run_query', which might also retrieve event data but with different approaches or formats.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'activitywatch_query_examples' and 'activitywatch_run_query' that might serve similar purposes, there's no indication of when this raw event retrieval is preferred over those query-based approaches, leaving the agent without context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

activitywatch_get_settingsB

Get ActivityWatch settings. Can retrieve all settings or a specific key if provided.

ParametersJSON Schema

Name	Required	Description	Default
`key`	No	Optional: Get a specific settings key instead of all settings

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It states the tool retrieves settings but doesn't disclose behavioral traits such as whether it's read-only (implied by 'Get'), authentication needs, rate limits, error handling, or response format. The description is minimal and lacks necessary context for safe and effective use.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized with two concise sentences that are front-loaded and waste-free. It efficiently communicates the core functionality and parameter usage without unnecessary details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what settings are returned, their structure, or any behavioral aspects like permissions or errors. For a tool with zero annotation coverage, more context is needed for adequate agent understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents the optional 'key' parameter. The description adds marginal value by mentioning 'a specific key if provided,' but doesn't provide additional semantics like key examples, format, or constraints beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('ActivityWatch settings'), and distinguishes between retrieving all settings or a specific key. However, it doesn't explicitly differentiate from sibling tools like 'activitywatch_get_events' or 'activitywatch_list_buckets' beyond the resource name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by mentioning 'all settings or a specific key if provided,' which suggests when to use the optional parameter. However, it lacks explicit guidance on when to choose this tool over siblings (e.g., vs. 'activitywatch_get_events') or any prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

activitywatch_list_bucketsB

List all ActivityWatch buckets with optional type filtering

ParametersJSON Schema

Name	Required	Description	Default
`type`	No	Filter buckets by type
`includeData`	No	Include bucket data in response

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it's a list operation with optional filtering, implying it's likely read-only and non-destructive, but doesn't confirm this or address other behavioral aspects like permissions needed, rate limits, pagination, error handling, or what 'includeData' entails. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose ('List all ActivityWatch buckets') and adds a concise modifier ('with optional type filtering'). There is no wasted verbiage, repetition, or unnecessary elaboration, making it easy to parse and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the basic action and hints at filtering, but lacks details on behavioral traits, usage context, or output expectations. Without annotations or output schema, the agent must infer behavior from the description alone, which is insufficient for confident tool selection in varied scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters ('type' for filtering and 'includeData' for including bucket data). The description adds minimal value by mentioning 'optional type filtering,' which aligns with the schema but doesn't provide additional context like example types or implications of including data. With high schema coverage, the baseline is 3, and the description doesn't significantly enhance parameter understanding beyond what's structured.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List all ActivityWatch buckets') and resource ('ActivityWatch buckets'), making the purpose immediately understandable. It distinguishes itself from siblings like 'activitywatch_get_events' by focusing on buckets rather than events, though it doesn't explicitly contrast with other bucket-related tools (none exist in the sibling list). The optional filtering aspect adds specificity beyond a basic list operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It mentions optional type filtering but doesn't explain scenarios where filtering is beneficial or when to choose this over other tools like 'activitywatch_query_examples' or 'activitywatch_run_query' for bucket-related tasks. There are no prerequisites, exclusions, or contextual recommendations provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

activitywatch_query_examplesB

Get examples of properly formatted queries for the ActivityWatch MCP server

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'gets examples,' implying a read-only operation, but doesn't clarify if this requires authentication, has rate limits, returns structured data, or involves any side effects. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior and constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence: 'Get examples of properly formatted queries for the ActivityWatch MCP server.' It is front-loaded with the core action ('Get examples') and specifies the context ('for the ActivityWatch MCP server'), with zero wasted words. This makes it highly efficient and easy for an agent to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has gaps. It explains what the tool does but lacks behavioral details (e.g., response format, authentication needs) and usage guidelines relative to siblings. Without an output schema, it doesn't describe return values, which could hinder an agent's understanding of how to use the examples provided.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to explain parameters, as there are none. It appropriately focuses on the tool's purpose without redundant parameter details, earning a high baseline score for parameter semantics in this context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get examples of properly formatted queries for the ActivityWatch MCP server.' It uses a specific verb ('Get') and identifies the resource ('examples of properly formatted queries'), making the function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'activitywatch_run_query' or 'activitywatch_get_events,' which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing to understand query syntax before using 'activitywatch_run_query'), exclusions, or contextual cues. Without such information, an agent might struggle to choose between this and sibling tools like 'activitywatch_run_query' or 'activitywatch_get_events.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

activitywatch_run_queryC

Run a query in ActivityWatch's query language

ParametersJSON Schema

Name	Required	Description
`timeperiods`	Yes	Time periods to query. Format: ['2024-10-28/2024-10-29'] where dates are in ISO format and joined with a slash
`query`	Yes	MUST BE A SINGLE STRING containing all query statements separated by semicolons. DO NOT split into multiple strings.
`name`	No	Optional name for the query (used for caching)

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure but only states the basic action. It doesn't mention whether this is a read-only operation, if it requires specific permissions, potential side effects, rate limits, or what the output looks like (especially critical since there's no output schema). This leaves significant gaps for a query execution tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states the core purpose without any wasted words. It's appropriately sized for a tool with well-documented parameters and gets straight to the point, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a query execution tool with no annotations and no output schema, the description is insufficient. It doesn't explain what kind of results to expect, error conditions, or behavioral constraints. Given the complexity of running queries and the lack of structured output documentation, more context about the operation's nature and results is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no parameter information beyond what's already in the schema (which has 100% coverage). While the schema thoroughly documents all three parameters with formats, constraints, and examples, the description doesn't provide additional context about parameter relationships or usage semantics, meeting the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Run a query') and the resource ('in ActivityWatch's query language'), which is specific and unambiguous. However, it doesn't explicitly differentiate this tool from its sibling 'activitywatch_query_examples', which might cause confusion about when to use each.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'activitywatch_get_events' or 'activitywatch_query_examples'. There's no mention of prerequisites, appropriate contexts, or exclusions, leaving the agent to infer usage from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

5 tool updatesv1.0.0Jan 2, 2026
- Addedactivitywatch_get_events
- Addedactivitywatch_get_settings
- Addedactivitywatch_list_buckets
- Addedactivitywatch_query_examples
- Addedactivitywatch_run_query

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored 2026-04-18 11:35 across 5 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Reddit Discussion

Related Servers

Related MCP Connectors

STAS Running Coach for Claude AOAuth
run.stas
Connect Claude to your Intervals.icu watch data for fitness, workout review, and plan writing.
Fitness Tracking Health & Wellness Education & Learning Tools
2
WHOOP — MissingMCPOAuth
com.missingmcp
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
Health & Wellness Fitness Tracking
213
DoneThatOAuth
ai.donethat
Privacy-first work tracking with summaries, reports, coaching, and AI-ready long-term memory.
Project Management Knowledge & Memory Workplace & Productivity
2
hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
238

Related MCP Servers

TripleWhale MCP Serverofficial
E-commerce & Retail Search Databases
Triple-Whale
A
license
Not graded
quality
C
maintenance
An 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.
Updated a year ago (2025-09-30 12:49 UTC)
106 npm
7
MIT
Paprika SQL MCP Server
Databases Developer Tools
jonaheaton
F
license
Not graded
quality
F
maintenance
A Model Context Protocol desktop extension that allows Claude to query and interact with custom SQL databases in real-time during conversations.
Updated a year ago (2025-09-20 04:04 UTC)
1
-
ActivityWatch MCP Server
Monitoring Developer Tools Knowledge & Memory
Auriora
A
license
Not graded
quality
C
maintenance
Enables 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.
Updated 7 months ago (2026-03-17 16:33 UTC)
12
GPL 3.0
ActivityWatch MCP Server
Developer Tools Monitoring
JM-404
F
license
Not graded
quality
F
maintenance
Connects 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.
Updated 6 months ago (2026-04-07 04:31 UTC)
-

Servidor MCP de ActivityWatch

Características

Instalación

Instalación desde npm (próximamente)

Compilación desde el código fuente

Requisitos previos

Uso

Uso con Claude for Desktop

Uso de un contenedor podman sin root en Linux con Gemini CLI

Anular el host/puerto del servidor de ActivityWatch

Ejemplos de consultas

Herramientas disponibles

list-buckets

run-query

get-events

get-settings

Ejemplos de lenguaje de consulta

Configuración

Solución de problemas

ActivityWatch no está en ejecución

Errores de consulta

Problemas de formato de consulta en Claude/MCP

El problema de formato más común

Al pedirle cosas a Claude

Contribución

Licencia

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

TripleWhale MCP Serverofficial

Appeared in Searches