Tasks and calendars in one place, unlimited calendars, a real API, and $0. Also there are cats.
Tell your AI agent to put a task on Thursday at 2 and it lands on the grid, with no inbox and no dragging.
The site has the setup steps too.
Try the demo. Local setup makes a demo account with a sample week already in it. Sign in with demo@meowlendar.com / meowlendar, or click Sign up to make your own. It only exists on your machine, since there's no hosted Meowlendar.
Want the real story? ESSENCE.md is the one-pager. EVOLUTION.md has the best screw-up in the whole collection: 1,255 passing tests on an app where nothing worked.
A calendar and task app you run yourself, with a REST API and an MCP server so your agent can do anything you can do. I don't run a database for anyone, and there's no hosted Meowlendar. You set up your own Supabase and it runs on your machine or wherever you put it. If you want Google sign-in and Google Calendar, you make your own Google Cloud login for it too. Your calendar stays yours, and I never see it.
Your coding agent can do almost all of the setup. There's a paste block below, and the Google part has its own steps after it.
I hate paying for tools. Motion called itself a smart calendar and had no usable API at the time, so my agents couldn't really touch it. Morgen was too expensive for what it was, and it was still missing things. Tasks made through its API landed in the inbox instead of on the calendar, which defeats the entire point.
I wanted tasks plus calendar, unlimited calendars, a link to my 2ndBrain, and a price of $0. Nobody sold that, because nobody can sell $0. So I made my own.
The name is for the brainrot and the meme value. It started as a poop-themed calendar called Poolendar, so really the cats are a step up. And I'm using it as the base for anything else I build that needs a calendar.
Paste this into Claude Code or whatever agent you use. It stops and asks when it needs you.
Set up Meowlendar for me
Self-host Meowlendar on this machine from https://github.com/fidgetcoding/meowlendar. Follow DEPLOY.md in the repo if anything here is unclear. Work in this order and verify each step before moving on. Never print secrets, and never commit apps/web/.env.local or supabase/.env.
Names: the project used to be called Poolendar. @poolendar/* packages are correct. Do not rename them.
DO THESE YOURSELF
1. Check prerequisites: node -v (22 or newer), pnpm -v, supabase --version, docker info. If Docker is not running, start it (colima start, if colima is installed). If a tool is missing, tell me what to install and stop.
2. Clone the repo and run pnpm install.
3. Run pnpm setup:local.
Verify: it exits 0 and apps/web/.env.local exists. If Supabase reports a container as "unhealthy", run it once more. It also creates the demo account demo@meowlendar.com / meowlendar with a sample week. Add --no-demo to skip it.
4. Start pnpm dev in the background.
Verify: curl -s -o /dev/null -w "%{http_code}" http://localhost:3000/login prints 200.
5. Run pnpm --filter meowlendar-mcp build.
Verify: packages/mcp/dist/index.js exists.
STOP AND ASK ME
6. Ask me to open http://localhost:3000 and either sign in with demo@meowlendar.com / meowlendar to see a sample week, or click Sign up to create my own account. Then ask me to go to Settings > API Keys, click Generate, and paste the pk_ key to you.
Verify: curl -s -H "Authorization: Bearer <key>" http://localhost:3000/api/calendars returns JSON containing "local_calendars".
THEN WIRE THE MCP
7. Run, using the absolute path to the clone:
claude mcp add meowlendar -s user --env MEOWLENDAR_API_KEY=<key> --env MEOWLENDAR_API_URL=http://localhost:3000 -- node <clone>/packages/mcp/dist/index.js
Verify: claude mcp list shows meowlendar as Connected. A new session may be needed before its tools appear. Then call create_task with a title, scheduled_start, and scheduled_end, and confirm list_events for that day returns it with kind "task".
ASK ME BEFORE GOOGLE
8. Ask if I want Google sign-in or Google Calendar. If not, stop here. Everything works on the local calendar. The Google sign-in button does not work until the provider is configured.
If yes, follow DEPLOY.md section 2 and walk me through the Google Cloud Console clicks one at a time. You cannot do them for me. Have me download the client JSON locally; read it without printing secrets, add the credentials as that section shows, and restart.
9. Ask me to choose Continue with Google. Google asks for sign-in and calendar access on one screen; let me approve it. The first sync starts on its own. For additional accounts, ask me to use Settings > Calendars > Connect Google Account.
Verify: the MCP list_calendars tool shows the accounts.
Finish by telling me which steps passed, which were skipped, and what is still running.
- Install the tools: Node 22+, pnpm, the Supabase CLI, and Docker Desktop or colima. Start Docker.
docker infoshould print server details. - Get the code:
git clone https://github.com/fidgetcoding/meowlendar && cd meowlendar && pnpm install
- Run
pnpm setup:local. Every line should start withok, and it writesapps/web/.env.local. It also makes the demo account (--no-demoskips it,--reset-demogives it a fresh week). - Run
pnpm devand openhttp://localhost:3000. You should see the sign-in page with a cat asleep on it. - Sign in with
demo@meowlendar.com/meowlendarto look around a sample week, or click Sign up and use any email and password to make your own. No email gets sent locally. You land on the week view, with a local calendar ready. - Connect your agent.
pnpm --filter meowlendar-mcp build- In the app: Settings > API Keys, name a key, Generate, copy it. It's shown once.
- Then, with your key and path:
claude mcp add meowlendar -s user \ --env MEOWLENDAR_API_KEY=pk_your_key \ --env MEOWLENDAR_API_URL=http://localhost:3000 \ -- node /absolute/path/to/meowlendar/packages/mcp/dist/index.js
claude mcp listshould say Connected. Ask for a task with a start and end time, and watch it land.
- Add Google if you want it. The next section has the steps and DEPLOY.md has every click. The setup uses your own Google Cloud OAuth client; Continue with Google requests calendar access in the same consent and starts syncing automatically.
- Host it if you want. DEPLOY.md covers hosted Supabase and Vercel, and I haven't run those yet either. Read SECURITY.md first.
Why do some internals say poolendar? That's the old name. Renaming the rest isn't worth breaking things, so it stays.
Google is optional, but each self-hosted installation needs its own Google Cloud OAuth client if you want the Continue with Google button or Google Calendar sync. The button is not configured by the default local setup; until it is, clicking it just shows a note pointing to Setup step 7. For a local calendar without Google, use Sign up with an email and password instead.
For Google, follow the complete Google setup in DEPLOY.md:
-
Create or choose a Google Cloud project for your installation and enable the Google Calendar API.
-
Configure the OAuth consent screen. For an external app in testing, add each Google account you want to use as a test user.
-
Create a Web application OAuth client. For the default local setup, add
http://localhost:3000as an authorized JavaScript origin and add bothhttp://127.0.0.1:54321/auth/v1/callbackandhttp://localhost:3000/api/google/callbackas authorized redirect URIs. If your Supabase API uses a different port, use its actual API URL for the first callback. -
Download the client JSON. Copy its client ID and secret into the following local files. Keep the secret out of chat, screenshots, logs and Git.
Add to
apps/web/.env.localwithout removing its existing values:GOOGLE_CLIENT_ID=your-client-id GOOGLE_CLIENT_SECRET=your-client-secret
Create
supabase/.envwith the same values:SUPABASE_AUTH_EXTERNAL_GOOGLE_CLIENT_ID=your-client-id SUPABASE_AUTH_EXTERNAL_GOOGLE_SECRET=your-client-secret
In
supabase/config.toml, setenabled = trueunder[auth.external.google]for this installation. Don't commit that local configuration change or either environment file. Protect the secrets withchmod 600 apps/web/.env.local supabase/.env. -
From the project root, stop the app, then restart the local Supabase project and app. Don't use
--no-backup: it deletes the local database volumes.set -a . supabase/.env set +a supabase stop supabase start pnpm dev
The Supabase CLI can print local service keys; don't share its output. If you use a nondefault Supabase project directory, run the commands against that project instead.
-
Open
http://localhost:3000and choose Continue with Google. Google asks for sign-in and calendar access on the same screen. Approve it and Meowlendar starts the first sync by itself. Google may show an unverified-app warning while your app is in testing. If that first sync fails, the app tells you and keeps trying. To connect another account later, use Settings > Calendars > Connect Google Account. An email login works with local calendars and can connect Google later the same way.If Google refuses the calendar sync, check that the Calendar API is enabled in the same Cloud project as your OAuth client, while you're logged in to the Google account that owns that project. The first time, I had the console open in the wrong Google account.
Google's testing mode can expire calendar refresh tokens after seven days; DEPLOY.md explains the publishing and verification trade-offs. Hosted installations use their own domain and Supabase callback URLs.
- Week calendar grid: create by double-click or drag, right-click menus, an edit form. It scrolls through the whole day, a button between the arrows jumps back to today, and the header tells you whether you're looking at this week or next. Event text picks black or white, whichever reads better on that color.
- Tasks on the grid through the API. That's the whole reason this exists.
- Local calendars and recurring events. No Google needed, and you can add as many as you want.
- Kanban board: four columns, drag cards around.
- Routines, tags, subtasks, a command bar and keyboard control.
- Booking pages at
/book/<slug>oryou.example.com/<slug>, with shared availability and approvals. - MCP server with 63 tools. Everything your agent could want, over one API key. You build it from your clone for now.
- 2ndBrain link. Two-way sync between Obsidian Tasks lines and your tasks, as a
meowlendar-vaultCLI and three MCP tools. It always shows a dry run first and backs up before it writes. Details. - Reminders by push, email and Telegram.
- Google Calendar sync, automatic and both ways, across any number of accounts, with a picker per calendar and optional task mirroring. One Google consent signs you in and connects your calendars, and the resync button spins while it works.
- Settings that save themselves, with Sign Out at the bottom of the settings sidebar where you'd look for it.
- Cats.
Every push to main runs CI in two jobs. The first runs lint and types, the unit tests, a dependency audit, and a check that the packed MCP starts from a clean npm cache. The second starts a real local Supabase, runs the integration tests against a production build of the app, then runs the browser tests against the dev server. Google, Telegram, Resend and push are local fakes in there.
The latest run, on 72f1fff (November 5, 2026): 1,664 unit tests, 150 integration tests and 25 browser tests passed, with one browser test needing a retry. The packed MCP listed 63 tools. Browser tests run headless and silent.
Fakes only prove my side works, so on November 5 I connected my own Google account to a local install. One consent screen, then 3 calendars and 30 events came in. Real Google writes and the other providers weren't part of that check.
If you already run an install, apply the new migrations safely before you update; see DEPLOY.md. EVOLUTION.md has the full test log.
MIT. Built by Nate Davidovich. Take it. Build your own calendar on top of it. That's what I'm doing.
