@nicola5tor/openproject-timelog
Provides tools for managing time entries locally and synchronizing them with an OpenProject instance via its API, including logging, listing, editing, and uploading time entries, as well as querying projects, work packages, activities, and existing time entries.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@nicola5tor/openproject-timelog Registra 2 horas de hoy arreglando el login, tarea 1234."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@nicola5tor/openproject-timelog
MCP server (Model Context Protocol) for keeping a local time log and syncing it with OpenProject (API v3). Log your work in natural language from Claude Desktop (or another MCP client), review it, and upload it to OpenProject when ready.
Transport: stdio
Local storage:
~/.openproject-timelog/entries.jsonConfig:
OPENPROJECT_URLandOPENPROJECT_API_KEYenvironment variables
Installation
No need to install anything globally: the server runs with npx.
# probarlo directamente
npx @nicola5tor/openproject-timelogOr install it in a project:
npm install @nicola5tor/openproject-timelog
# o
pnpm add @nicola5tor/openproject-timelogRelated MCP server: OpenProject MCP Server
Configuration in Claude Desktop
Edit the configuration file (claude_desktop_config.json) and add the
server under mcpServers:
{
"mcpServers": {
"openproject-timelog": {
"command": "npx",
"args": ["-y", "@nicola5tor/openproject-timelog"],
"env": {
"OPENPROJECT_URL": "https://tu-openproject.example.com",
"OPENPROJECT_API_KEY": "TU_API_KEY"
}
}
}
}Restart Claude Desktop after saving.
How to get your OpenProject API key
In OpenProject: My account → Access tokens → API and generate a key. The
server authenticates with Basic auth using the literal user apikey and your key
as the password.
The local-only tools (
log_entry,list_entries,edit_entry,assign_entry,delete_entry,clear_sent) work even if you don't configure OpenProject. The query and upload tools requireOPENPROJECT_URLandOPENPROJECT_API_KEY.
Tools
Local time log
Tool | Description |
| Logs a time entry. Params: |
| Lists entries by status. Param: |
| Edits a pending entry. Params: |
| Assigns a work package to several entries. Params: |
| Deletes a pending entry. Param: |
| Removes all already-sent ( |
OpenProject query
Tool | Description |
| Lists projects ( |
| Lists tasks. Optional params: |
| Lists time entry activities ( |
| Queries already-logged hours. Optional params: |
Sync
Tool | Description |
| Uploads entries to OpenProject. Optional param |
* = required.
Behavior notes
Local ids are UUID v4. Hours are stored in decimal (
1.5= 1h30m) and converted to ISO 8601 duration (PT1H30M) on upload.The
projectIdof an entry, if not specified, is derived from the work package on upload (an extra call to OpenProject).The JSON file is written atomically (temp file + rename) and operations are serialized to prevent corruption.
Network / credential / permission errors are returned as readable messages in the tool response, without crashing the server.
Conversational usage examples
You: Log 2 hours of today fixing the login, task 1234. Claude: (calls
log_entrywith description="fix login", hours=2, workPackageId=1234)
You: Log 45 minutes of meeting for me, I'll assign the task later. Claude: (
log_entrydescription="meeting", hours=0.75) — stays pending assignment.
You: What do I have pending to upload? Claude: (
list_entriesstatus="pending")
You: Assign task 1234 to those two meetings. Claude: (
assign_entryentryIds=[...], workPackageId=1234)
You: What activities are there? Set "Development" on everything and upload it. Claude: (
get_activities→edit_entry/assignfor activityId →upload_entries)
You: Clean up what was already uploaded. Claude: (
clear_sent)
Development
npm install # instala deps y compila (prepare -> build)
npm run build # compila TypeScript a dist/
npm start # ejecuta dist/index.jsStructure:
openproject-timelog/
├── src/
│ ├── index.ts # entry point, setup MCP y registro de tools
│ ├── store.ts # CRUD bitácora local (JSON atómico)
│ ├── openproject.ts # cliente API OpenProject v3
│ └── types.ts # interfaces/types
├── package.json
├── tsconfig.json
└── README.mdLicense
MIT
Available Tools
16 toolsassign_entryAsignar work package a entriesB
Asigna un workPackageId a una o varias entries pendientes (por sus ids).
Inputs: entryIds (required), workPackageId (required).
clear_sentLimpiar entries enviadasA
Borra de la bitácora local todas las entries con status 'sent'.
Inputs: no named parameters.
delete_entryBorrar una entrada pendienteC
Borra una entry con status 'pending'.
Inputs: id (required).
edit_entryEditar una entrada pendienteC
Edita campos de una entry con status 'pending'. Solo se aplican los campos indicados.
Inputs: id (required), hours, endTime, spentOn, +6 more.
get_activitiesListar actividades de time entryA
Obtiene las actividades disponibles para registrar tiempo. Las actividades son por-proyecto: si pasas workPackageId se listan las de ese contexto; si no, se usa cualquier work package accesible.
Inputs: workPackageId.
get_projectsListar proyectos de OpenProjectB
Obtiene los proyectos disponibles en OpenProject.
Inputs: no named parameters.
get_time_entriesConsultar horas registradas en OpenProjectB
Consulta time entries ya registradas en OpenProject, con filtros opcionales.
Inputs: to, from, projectId, workPackageId.
get_work_packagesListar work packages de OpenProjectB
Obtiene tareas/work packages, opcionalmente filtradas por proyecto, status o assignee.
Inputs: status, assignee, projectId.
list_entriesListar entradas de la bitácoraA
Lista las entries de la bitácora local filtrando por status, opcionalmente agrupadas.
Inputs: status, groupBy, onlyActiveProject.
log_entryRegistrar entrada en la bitácoraB
Registra una entrada de horas en la bitácora local. Si no se indica workPackageId queda pendiente de asignar (con assign_entry).
Inputs: hours (required), description (required), endTime, spentOn, +5 more.
project_createCrear proyecto localA
Crea un proyecto local (workspace) para agrupar horas. Define valores por defecto (proyecto de OpenProject, work package y actividad) que se aplican al registrar horas mientras esté activo. Si es el primer proyecto, queda activo automáticamente. Se comparte entre Claude Code y Claude Desktop.
Inputs: name (required), defaultActivityId, defaultWorkPackageId, openprojectProjectId.
project_deleteBorrar un proyecto localA
Borra un proyecto local. No borra sus entries: solo las desvincula del proyecto.
Inputs: id (required).
project_listListar proyectos localesA
Lista los proyectos locales (workspaces) y marca cuál está activo. Distinto de get_projects, que consulta los proyectos de OpenProject.
Inputs: no named parameters.
project_useActivar un proyecto localA
Marca un proyecto local como activo. Las nuevas horas (log_entry) se crean dentro de él y toman sus valores por defecto.
Inputs: id (required).
render_galleryGenerar galería visual de la bitácoraA
Genera un HTML autocontenido (stats, filtros por grupo y tabla) con las entries de la bitácora y lo escribe en un fichero temporal. Devuelve la ruta del fichero (no el HTML) para publicarla con la tool Artifact, evitando gastar tokens en volcar el HTML en la respuesta.
Inputs: title, status, groupBy.
upload_entriesSubir entries a OpenProjectA
Sube a OpenProject las entries indicadas (o todas las pending con workPackageId si se omite entryIds). Cada entry necesita workPackageId y activityId.
Inputs: entryIds.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 16 tools
Tools are mostly distinct: local entry operations, remote OpenProject reads, upload/reporting, and workspace project management occupy clear separate roles. The get_projects vs project_list pair is the only potential ambiguity, though descriptions explicitly distinguish remote projects from local workspaces.
The majority follow a clear verb_noun snake_case pattern (get_work_packages, log_entry, upload_entries). The project_* group (project_create, project_list, project_use, project_delete) reverses the order to noun_verb, which is internally consistent but a visible deviation.
16 tools is at the upper edge for a focused server, but the scope includes local entries, OpenProject synchronization, remote querying, reporting, and local workspace management. Each tool has an identifiable purpose, so none feels redundant, though the surface is slightly heavy.
The core local-entry lifecycle is complete: create, list, edit, delete, assign, upload, and clean up. Minor gaps such as no way to update local project defaults and no remote time-entry edit/delete are present but don't block the main log-and-upload workflow.
Maintenance
Related MCP Connectors
timesheet.io MCP server - manage timers, projects, tasks and reports
MCP server for MOCO business software: time tracking, projects, budgets, and invoicing via API
MCP server for generating rough-draft project plans from natural-language prompts.
Toggl 2.0 MCP server for tasks, projects, time entries, and workspace operations.
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server for Productive.io that enables users to log time, inspect projects, and manage time entries using natural language commands. It features fuzzy project matching, local caching, and remembers default services per project for streamlined time tracking.14MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for integrating with OpenProject API, enabling AI assistants to manage projects, work packages, time tracking, and users.15 npm2MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI assistants to interact with OpenProject, listing projects and work packages and managing resources through natural language.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that connects Claude Desktop to your OpenProject instance, allowing you to manage projects, tasks, and time entries through natural language.MIT