Calendrome is a local-first scheduling engine for people who plan their week by talking to an AI. Hours are budgeted, time is tracked, and every adjustment is one sentence away.
This is an early beta. You install it locally, it spins up a SQLite file on your machine, and you experiment with it from Claude Code. Nothing leaves your laptop. Things will change. Bugs are expected. Feedback is welcome.
Every other weekly planner pretends to solve scheduling with checkboxes and reminders. Calendrome takes the opposite bet: real time, real budgets, real conversations.
You can talk about needing to do something. You can list it. You can intend it. But until time is actually allocated for it, it won't happen.
Calendrome makes the gap between "I should do this" and "two hours blocked Tuesday" as small as possible.
Even when client work drops, it still somehow takes all week — unless you budget deliberately. Without explicit hour caps, low-priority work absorbs every gap.
Calendrome makes hour budgets visible so you can see the drift and push back.
Budget bars from the actual GUI — over budget glows red, under glows muted.
The thing every other tool gets wrong is making "Tuesday night I'm doing nothing" into a settings exercise — recurring rules, calendar overlays, working hours panels.
In Calendrome that's one MCP call from a single conversational sentence. Same for reopening time.
{
"category_id": "work",
"start": "2026-05-12T18:00:00",
"end": "2026-05-12T23:00:00",
"reason": "off"
}
Calendrome doesn't reach out to anything on its own. It's a quiet local SQLite database with an MCP interface. Claude Code is what stitches it together with the rest of your stack.
Tasks, projects, weekly hour budgets, time logs, availability windows, habit instances. The single source of truth for what you actually intend to do this week — stored in a SQLite file on your laptop you can rm any time.
Pulls Jira tickets, places events on Google Calendar, pushes time logs to Harvest. Calendrome stays local and dumb on purpose — Claude is the smart, networked, reasoning part that ties everything together.
Calendrome is a local MCP server. No accounts. No cloud. The database is one SQLite file on your machine that you can delete whenever you're done experimenting.
Requires Node 20+ and npm.
git clone https://github.com/mklute101/calendrome.git cd calendrome npm install npm run build
Add to ~/.claude/settings.json (or a project-level .claude/settings.json):
{
"mcpServers": {
"calendrome": {
"command": "node",
"args": ["/path/to/calendrome/dist/src/mcp/server.js"],
"env": { "CALENDROME_DB": "/path/to/calendrome.db" }
}
}
}
Restart Claude Code, then try the /week skill — or just say "create an ACME project, 20 hours a week".
$ /week Pulling Jira tickets… Reading your calendar… Here's a draft for 2026-05-11 → 2026-05-17.
Optional dashboard: npm run gui opens a read-only weekly view at localhost:3000. Same design system as this page — because they're the same product.