Calendrome — Agendador de Tarefas por Projeto
mklute101/calendrome
Planejador local de tarefas com integração Google Calendar e orçamentos por projeto
Ver no GitHubMotor de agendamento de tarefas baseado em projetos, exposto como MCP server, que substitui localmente ferramentas como Reclaim.ai. Integra-se com Google Calendar e permite rastreamento de tempo, orçamentos semanais e disponibilidade de agendamento via Claude.
Instalação
npx convez-ai mklute101/calendrome1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Planejar semana com alocação de tempo por projeto
- Sincronizar tarefas de Jira/backlog com calendário Google
- Rastrear tempo gasto e comparar com orçamento semanal
- Gerenciar bloqueios de tempo e disponibilidade customizada
- Exportar timesheets e relatórios de produtividade
Veredito

Solução sólida e pragmática para quem precisa de agendamento local com rastreamento de tempo. Bem estruturada como MCP server (110+ testes), integra-se bem com Claude e Google Calendar, mas exige setup manual e é voltada para power users que dominam fluxos de CLI/programáticos.
README
A tradução para o português deste README ainda está na fila.
Calendrome
A local, project-based task scheduling engine exposed as an MCP server. Designed to replace Reclaim.ai with a simpler model: you (via Claude planner skills) decide what goes where, calendrome tracks the tasks, budgets, habits, and time.
Quick start
npm install
npm run build
npm test # 110+ tests, all should pass
Run as an MCP server
# Default DB path: ./calendrome.db (created on first run)
npm start
# Or specify a custom DB path:
CALENDROME_DB=~/my-tasks.db npm start
The server uses stdio transport — it reads JSON-RPC from stdin and writes to stdout. This is the standard MCP protocol.
Add to Claude Code
In your Claude Code settings (~/.claude/settings.json or project-level
.claude/settings.json), add:
{
"mcpServers": {
"calendrome": {
"command": "node",
"args": ["/path/to/calendrome/dist/src/mcp/server.js"],
"env": {
"CALENDROME_DB": "/path/to/calendrome.db"
}
}
}
}
Restart Claude Code. You should see calendrome tools in your tool list.
Demo: weekly planning flow
With both calendrome and Google Calendar MCP servers connected, plus a Jira MCP:
-
Set up projects (one-time):
create_project { id: "acme", name: "Acme Corp", prefix: "ACME", weekly_budget_minutes: 1200 } -
Pull Jira tickets → create tasks:
create_task { project_id: "acme", title: "ACME-123: Fix login bug", priority: "HIGH", duration_minutes: 120 } -
Check budgets:
get_all_budgets { week_start: "2026-04-13" } → ACME: 0h spent / 20h allocated -
Place on calendar (via Google Calendar MCP):
# Create the calendar event create_event { summary: "ACME Fix login bug", start: "2026-04-14T09:00:00", end: "2026-04-14T11:00:00", calendarId: "primary" } # Link the event to the task update_task { id: 1, calendar_event_id: "evt-abc123" } -
Track time (when you start working):
start_task { id: 1 } ... work ... stop_task { id: 1 } -
Export timesheet:
export_timesheet { from: "2026-04-13", to: "2026-04-19", format: "markdown" }
Available MCP tools
Projects
create_project— create a project with prefix and weekly budget.category_iddefaults towork.list_projects— list projects (filter byactive, bycategory_idfor the work/personal split)update_project— update project settings (includingcategory_id)
Categories & availability
Every project belongs to a category (work, personal, …) that owns a default
scheduling window. The GUI defaults to the work view so casual screen-shares
never leak personal stuff. Availability overrides are the frictionless answer
to "Tuesday night I'm not doing anything" — one MCP call from a single
sentence to Claude.
list_categories— all categories with their default windowscreate_category— define a new category with a windowupdate_category— change the window or renameblock_time— reserve a slot so the planner won't schedule into itopen_time— carve out an extra slot inside a normally-blocked windowlist_availability— overrides intersecting a date rangedelete_availability/clear_availability— remove individually or by range
Tasks
create_task— create a task in a projectupdate_task— update task fieldslist_tasks— list with filters (project, status, due_before)search_tasks— full-text search titles and notesstart_task— start the timerstop_task— stop the timercomplete_task— mark done
Inbox
inbox_add— quick captureinbox_list— unprocessed itemsinbox_next— oldest unprocessedinbox_process— convert to task in a project
Habits
create_habit— recurring time blocklist_habits— active habitsgenerate_habit_instances— materialize instances for a date range
Budgets
get_project_budget— allocated/spent/scheduled/remaining for one projectget_all_budgets— same, for every active project
Calendar placement
place_task— create a calendar event for a task (requires calendar client)unplace_task— remove the calendar event
Timesheet
export_timesheet— CSV or markdown, with optional totalsget_timesheet_summary— structured data for programmatic consumers
Layout
get_week_layout— tasks + habits + events for a date range, by day