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.
Everything that claims your time is a commitment, and Calendrome budgets them the way YNAB budgets dollars — envelope budgeting, the same idea that works for money, applied to the actually-finite resource.
Ship the login spec. An estimate and a definitive finish line. Its blocks float wherever they fit.
Stretch, daily, 15 minutes — or work out 4×/week, any days. Done or skipped per instance. You can't do the week's stretching in one sitting; the spreading-out is the commitment.
Ten hours of prospecting before launch, or 3h of Spanish a week, forever. A bucket of hours — big chunks welcome, and the weekly ask re-paces itself when you fall behind.
The standup. Owned by an external calendar. It just takes hours off the week's supply.
Calendrome computes what a week actually holds — your working windows, minus meetings, minus time you've blocked off. You assign that supply to envelopes: client caps that warn when you run over, goal floors that nag when you're falling short.
When something needs more than its envelope — the beautiful day, the client fire — you don't silently absorb it. You pull hours from another envelope, zero-sum, and the tradeoff gets named. Caps stay soft: warn loudly, never block. But drift can no longer happen unconsciously.
{
"week_start": "2026-07-13",
"from": { "type": "project", "id": "hobby" },
"to": { "type": "project", "id": "acme" },
"minutes": 120,
"note": "trail afternoon"
}
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.
Recommended: install the Claude Code plugin and let /calendrome:onboard walk you through MCP setup. Plugin install ↓ · Manual MCP-only install ↓
Two commands — works from any directory.
claude plugin marketplace add mklute101/calendrome claude plugin install calendrome
This is a self-hosted, GitHub-based marketplace. Calendrome is in beta and is not on the Anthropic official marketplace.
/calendrome:onboardFrom any Claude Code session. Onboard handles the rest — clones the calendrome repo, builds the MCP server, registers it with Claude Code, and walks you through your first projects and budgets.
$ /calendrome:onboard Where would you like to install calendrome? [default: ~/dev/tools/calendrome]
Restart Claude Code when onboard tells you to. Then try the /calendrome:week skill — or just say "create an ACME project, 20 hours a week".
$ /calendrome:week Pulling Jira tickets… Reading your calendar… Here's a draft for 2026-05-11 → 2026-05-17.
Skip the plugin and just register the MCP server. You'll have raw mcp__calendrome__* tools available but no /calendrome:* slash commands.
Requires Node 20+ and npm.
git clone https://github.com/mklute101/calendrome.git cd calendrome npm install npm run build
From inside the cloned calendrome/ folder, one command:
claude mcp add calendrome \ --env CALENDROME_DB="$PWD/calendrome.db" \ -- node "$PWD/dist/src/mcp/server.js"
$PWD resolves to your current directory, so the absolute paths get filled in automatically. Verify with claude mcp list.
Restart Claude Code. Calendrome's MCP tools are now available — call them directly, or just say "create an ACME project, 20 hours a week" and Claude will pick the right tool.
Optional dashboard: npm run gui opens the interactive weekly planner at localhost:3737 — drag blocks to reschedule, complete and snooze tasks inline. Same design system as this page — because they're the same product.