What's new in Keeper.sh

A new Disable Reminders setting on a source calendar stops the copies Keeper.sh makes from it from firing reminders of their own. The original event still reminds you as usual, and its copies hold the time without alerting you again.

Before this release, an event copied into two or three other calendars could set off a reminder from each of them a few minutes before it started. With Disable Reminders on, you hear about the event once, from the calendar it came from.

The setting applies to copies on Google Calendar and Outlook. On Google Calendar, copies opt out of the calendar's default reminders, and on Outlook they are saved with the reminder turned off. Turning the setting on or off updates copies that already exist on the next sync.

Disable Reminders sits with Mark Events as Private in a source calendar's sync settings, and like the other event filters it is part of Pro.

What a copied event shows lists the other settings that shape a copy.

Signing up for Keeper.sh now leads into a guided setup that ends with your events copied. It has three steps: connect a calendar, add the calendar where your busy time should show, and start syncing.

Before you start, Keeper.sh says in plain words what the sync will do, for example that your work calendar will show you as busy whenever your personal calendar has an event. Once you start, it reads your calendars at once and shows the copying as it happens, with an estimate of the time left. When it finishes, you see the events that were copied, and you can add a test event to watch one arrive.

The setup also handles the problems people hit most when connecting a calendar. A work or school Microsoft account that only allows apps its IT admin has approved gets an approval link you can copy or email to your admin, and the setup carries on once they accept. iCloud and Fastmail say when they need an app password instead of your account password, and point you to where to generate one. A calendar link that does not work says why, and one that works is named after the calendar it carries.

Each other connection failure now gets its own message instead of a general error, and the dashboard holds back its upgrade offer until you have a sync running.

Linked accounts and calendars covers connecting each kind of calendar.

An account's refresh action now works for iCloud, Fastmail and other CalDAV accounts. It rechecks the server for calendars added or deleted since you connected, the same way it already did for Google and Outlook.

Connecting a CalDAV calendar that another of your accounts already holds now says it is already connected, instead of importing a second copy of the same calendar.

Keeper.sh also stops sending copies to a Google calendar your account can only read, such as a shared calendar where you were not given permission to make changes. Before this release, it kept retrying those calendars on every sync. A destination calendar that times out is now retried less often until it responds, so it does not hold up your other calendars.

Event times also resolve the same way everywhere Keeper.sh reads or writes them: CalDAV calendars, calendar links, repeating events, Outlook copies, all-day events and the free-time answers given to assistants.

Linked accounts and calendars explains what you can do with each calendar on an account.

Keeper.sh now uses the latest time-zone rules when it copies an event. After Alberta stopped changing its clocks on 1 November 2026, copies of events in affected zones could land an hour early in the other calendar. They now land at the time the original shows.

The update covers Windows' new names for the Alberta, British Columbia and Manitoba zones, which Outlook and Microsoft 365 calendars use, so events from those calendars resolve to the right zone too.

A second fix covers calendars that describe a zone's later clock changes as a list of dates rather than a repeating rule, as some calendars do for Asia/Manila. Keeper.sh now reads those zones by the official rules, so their copies land at the right time as well.

An event has not arrived in the other calendar covers what to check when a copy looks wrong.

When Keeper.sh removes one of its own copies from an Outlook or Microsoft 365 calendar, the copy is now deleted outright. Before this release, each removed copy went to the account's Deleted Items folder, the same as an event you delete by hand.

Copies are removed whenever the original is deleted, moves out of the sync window or stops matching your filters. On a busy calendar, those removals could fill Deleted Items with thousands of old copies.

Only copies Keeper.sh created are deleted this way. Events you delete yourself, and every event in your source calendars, follow Outlook's usual rules.

How a copy follows the original explains when Keeper.sh updates or removes a copy.

You can now remove a calendar from Keeper.sh after it has been deleted at the provider, including a calendar Keeper.sh writes into. Before this release, the dashboard hid the remove option for any calendar Keeper.sh writes into, so a deleted one stayed listed.

Keeper.sh still keeps you from removing a destination calendar that exists, because removing it could strand the copies it holds. That protection lifts once a refresh or the scheduled recheck finds the calendar is gone at the provider.

A removed calendar stays removed, and later refreshes do not bring it back. Keeper.sh also stops asking for change notifications from calendars that are gone.

Removing an account explains what happens to copies when you disconnect a calendar service.

Keeper.sh now has a support page that collects how to get help in one place: the address to email with a question, and where to file bugs and feature requests on GitHub.

It answers common questions directly: how often calendars update on each plan, what to do when an event has not arrived, what colleagues can see of your personal events, and which calendars Keeper.sh works with.

Its plans and billing section covers what Free and Pro include, how to change or cancel your plan from the dashboard, and that you keep Pro until the end of the period you paid for. The account section explains how to delete your account and how to request your data.

The troubleshooting guides each start from a problem you can see in your calendar.

The Keeper.sh MCP server is now listed in the official MCP Registry. MCP clients that look servers up in the registry can find Keeper.sh there and connect to it at https://www.keeper.sh/mcp.

Connecting works the same way as adding the server by hand. You approve the connection in your browser, and the assistant can then read your synced calendars and, with your permission, make changes.

The MCP server docs list every tool an assistant can use and how to connect one.

Keeper.sh now gives every source calendar its own due time for its next read. Before this release, calendars were read in shared passes, and accounts that kept failing could take up the capacity that working calendars needed.

Each read now sets the next one. A calendar that reads successfully is due again after its plan's interval, and one that fails backs off and is retried later without holding up anything else. A change notification from Google or Outlook, a newly connected calendar and a reconnected account are all read at once.

The plan timings are unchanged: on Free, your calendars are checked every minute and changes are copied every 30 minutes, and on Pro, Google and Outlook changes land within seconds and iCloud, Fastmail and other CalDAV calendars update every minute.

An event has not arrived in the other calendar covers what to check when a copy is late.

Two new settings in a source calendar's Exclusions section keep events from being copied. Exclude by Status skips events marked Busy, Free or Tentative, whichever you select. Exclude Titles Containing skips events whose title contains any of the words you list, ignoring case.

They suit events that should not block time elsewhere: a standing placeholder invite, a hold marked Free, or a meeting you have only tentatively accepted. Tentative is offered for Outlook calendars and for iCal links published by Outlook, the sources that report it.

Both settings are part of Pro, like the other event filters. Copies of events that match are removed on the next sync.

What a copied event shows lists the other exclusions.

An assistant connected to Keeper.sh can now edit and delete events on your connected Google Calendar, Outlook and CalDAV calendars, not only the events it created itself. The change is written to the original calendar, and Keeper.sh then updates the copies on your other calendars.

The same applies to the REST API: updating or deleting an event now works for events from your connected calendars.

Some edits are still refused, with an error that says why. Repeating events are left alone, because an edit to one occurrence could rewrite the whole series. Copies Keeper.sh made are refused too, since the next sync would overwrite them, so edit the original instead. Calendars added from an iCal link are read-only.

What an AI agent can do with your calendar covers the other actions an assistant can take.

The Keeper.sh dashboard now includes a calendar with month and week views, beside the sidebar on desktop. Your events appear in it in the same card style as the events list.

The week view marks the current time with a line across the grid, and each day in its header shows how busy it is. Selecting an event opens its details in a popover.

The sidebar's event graph and the week view are linked: hovering a day in one highlights it in the other, and clicking a bar in the graph opens that day in week view.

Seeing all your calendars in one app shows how to get the same combined view in the calendar app you already use.

When a connected account loses access, for example after you change your iCloud password or revoke access at the provider, the Keeper.sh dashboard now says so and takes you straight to reconnecting it.

A Reconnect notice in the sidebar lists every account that needs attention, with each provider's icon, and the calendar view shows the same notice above the grid. Choosing an account opens its reconnect screen.

Once you reconnect an account, Keeper.sh syncs it again.

Copied events have disappeared covers what happens to copies when an account loses access.

A new Mark Events as Private setting on a source calendar marks every event Keeper.sh copies from it as private in the destination. People who can see the destination calendar, such as colleagues on a work calendar, see that the time is taken without seeing the event's details.

Keeper.sh uses each provider's own private flag: private visibility on Google Calendar, private sensitivity on Outlook, and the private class on iCloud, Fastmail and other CalDAV calendars. The destination calendar then hides the details the way it does for any private event.

The setting is part of Pro, alongside the other event filters. It suits a personal calendar copied into a work one, where the copies should hold the time and show nothing else.

Keep personal details out of your work calendar shows a full setup.

Keeper.sh now delivers changes to your other calendars sooner. When Google or Outlook notifies Keeper.sh that an event changed, that calendar is read straight away, in its own lane ahead of scheduled checks, instead of waiting behind them.

A newly connected calendar is copied to its destinations at once, instead of on the next scheduled run, and Pro accounts are scheduled first.

The plan timings are unchanged: on Free, your calendars are checked every minute and changes are copied every 30 minutes, and on Pro, Google and Outlook changes land within seconds and iCloud, Fastmail and other CalDAV calendars update every minute.

Keeper.sh pricing compares sync timing on Free and Pro.

When an original event changes, Keeper.sh now updates its copy on an iCloud, Fastmail or other CalDAV calendar in place. Before this release, it deleted the old copy and created a new one.

Deleting and recreating was most visible on shared calendars, where one change could notify everyone sharing the calendar twice. An update in place is a single change, so people see the event change instead of disappearing and coming back.

Google Calendar and Outlook destinations work as before. If a CalDAV server rejects an update, Keeper.sh falls back to replacing the copy, so the destination still ends up matching the original.

How a copy follows the original explains how Keeper.sh keeps copies in step.

Keeper.sh now reads a destination calendar only up to the end of the sync window you set. Events further ahead are left alone: they are not read, updated or removed.

Reading less of each destination makes each sync faster.

How far back and ahead events are copied explains how to set the window.

On Pro, a change on Google Calendar or Outlook now reaches your other calendars within seconds, starting as soon as you connect the account. Google and Outlook notify Keeper.sh when an event changes, so there is no wait for the next scheduled check.

This covers Google Calendar, Outlook and Microsoft 365. iCloud, Fastmail and other CalDAV calendars are still checked on a timer, because Apple offers no way to notify a calendar tool of a change. On Pro, they update every minute.

On Free, your calendars are checked every minute and changes are copied every 30 minutes.

Keeper.sh pricing compares sync timing on Free and Pro.

Keeper.sh now rechecks each connected account for new calendars on a schedule. Before this release, the list of calendars on an account was read once, when you connected it, so a calendar created later only appeared after you disconnected the account and set it up again.

Calendars that appear later are picked up on their own, and calendars that were deleted stop being offered. Your existing connections do not change: the recheck keeps the list of calendars you could sync current, not the syncing itself.

Each account also has a refresh action that rechecks it immediately and tells you what it found. Use it when someone shares a calendar with you and you want it in Keeper.sh straight away.

Linked accounts and calendars explains what you can do with each calendar on an account.

A calendar feed is a link you give to another app, or another person, so they can see when you are busy. Until now you had exactly one, covering everything you had connected, so the link you gave a client showed the same events as the one you subscribed to yourself.

Feeds are now named, and you can keep as many as you need. Each covers the calendars you pick for it and has its own event name settings, so a feed for a client shows only busy blocks while the one you use yourself keeps the real titles. Every feed has its own page and its own link, in a field you can select and copy.

Free accounts keep one feed, and keeping several is part of Pro.

Shareable calendar links covers what a feed carries and how many you get on each plan.

Each connected calendar now has its own sync window, set separately for the past and the future: one week, one month, three months, six months, twelve months or two years. The default is one month back and two years ahead.

Before this release, every calendar copied the same span of time, so a calendar you joined for a single project could drag years of history into the calendar you use every day.

Keeper.sh stops fetching outside the window, so a calendar with years of history syncs faster, and copies that fall outside a narrowed window are removed. Saving a new window requests a sync straight away, so widening it fills in the extra history at once.

How far back and ahead events are copied explains the window and what narrowing it removes.

An assistant connected to Keeper.sh can now find when you are free, start a sync, and pause a calendar.

Finding free time works out the open slots across every calendar you have connected, over a range you give it. It reads availability, not just events: an event marked free or working elsewhere does not block a slot, while busy and out-of-office do. Give it working hours and working days in a named timezone, and "find me an hour on Thursday" stops offering 6am.

Syncing on demand clears the backoff on any source that had been backing off after errors, and queues a push to every calendar you copy into, at most once a minute. Pausing stops a calendar syncing in both directions while leaving it connected with its settings intact. All three actions also work over the REST API.

The MCP server docs list every tool an assistant can use.

Changes to a repeating event now reach the copies on your other calendars. Edit the repeat rule and the copies update, skip a date and that occurrence is removed, and move the series to another timezone and every occurrence moves with it.

Before this release, the original series copied correctly, but later changes did not follow. Nothing showed an error, so the two calendars could disagree without warning.

Single occurrences are handled on their own. Moving next Tuesday's instance of a weekly meeting changes next Tuesday's copy, and the rest of the series stays where it is, as it does on the original calendar.

How a copy follows the original explains how Keeper.sh keeps copies in step.

Keeper.sh can now copy a timed event that runs from midnight to midnight as an all-day event. Many subscription links, such as conference schedules, school calendars and sports fixtures, publish a day off that way. It covers the same span of time, but instead of a banner across the top of the day you get a solid 24-hour block.

The setting is per calendar, because the conversion is a judgement: a real event that runs midnight to midnight is rare but possible, and the right answer depends on the calendar you are reading.

Turn it on for a subscription that publishes all-day events as timed blocks, and leave it off for calendars that publish them correctly.

What a copied event shows covers the other per-calendar settings.

Keeper.sh now connects to calendar servers that require digest authentication, a sign-in scheme used by many self-hosted and university CalDAV servers. Before this release, those servers rejected credentials that were correct, because Keeper.sh only used the more common scheme.

Both schemes now work. When a server asks for digest, Keeper.sh completes the exchange with the details you already entered. Nothing about how you enter them changes, and there is no setting to find.

Keeper.sh records which scheme your server wants the first time it says so, and later syncs answer correctly on the first attempt. If a server refused your details at the connect screen before, try connecting again.

What each calendar service asks for lists the details a CalDAV server needs.

Connecting a calendar to Keeper.sh now starts a sync straight away. Events begin arriving while you are still on the page, so you can confirm the setup works, and a mistake in your mapping shows up immediately.

Before this release, nothing happened until the next scheduled run.

The same applies when you change what gets copied. Adjusting which calendars feed a destination requests a sync instead of waiting for the schedule, so you can check the change right away.

An event has not arrived in the other calendar covers what to check when a copy is missing.

An assistant connected to Keeper.sh can now create, edit and delete events, list the invitations waiting for a reply, and RSVP to them. It can also list your connected accounts and fetch the link to your combined calendar feed, which is often what someone asking for your availability needs.

Every one of these actions is also available as a REST API. A new API tokens page under Settings lets you create tokens and revoke each one on its own, so you can cut off a script without disturbing an assistant you still use.

Free accounts include 25 calls a day, shared between assistant and API access. Pro removes the cap on both.

The MCP server docs list every tool an assistant can use.

Keeper.sh can now be added as a connector in Claude and other assistants that support the Model Context Protocol (MCP). Once connected, the assistant can list the calendars you have linked, look up the events in a date range and timezone you give it, and count how many fall inside it, so "what does my Thursday look like" is answered from your actual calendars.

You approve the connection once, on a consent screen in your browser, and the assistant signs in with OAuth instead of holding a password. You can revoke its access at any time, and revoking it does not touch the calendars themselves.

At launch the connector is read-only: the assistant can look at your calendars but cannot change them.

How to give Claude access to your calendar walks through connecting it.

All-day events now stay all-day when Keeper.sh copies them, across Google, Outlook and CalDAV. Before this release, a day marked off for travel arrived as a timed block running midnight to midnight, which made a week look far busier than it was.

Availability travels with each event. An event marked free stays free instead of becoming a solid block, which matters for entries such as a birthday, a deadline or a release date.

Out-of-office and working location entries keep their type too. A week marked out of office arrives as out of office, so the receiving calendar shows it that way and colleagues can tell you are away rather than in back-to-back meetings.

What a copied event shows lists the exclusions for all-day, focus time and out-of-office events.

You can now set the title a copied event carries, per calendar, with a template. By default a copy is named after the calendar it came from, which keeps the original title private but tells you little when three calendars feed the same destination.

The template takes plain text plus two placeholders: the original event's name and the name of its calendar. "Work — {{calendar_name}}" labels every copy so you recognise it at a glance, and "{{event_name}}" passes the real title through for a calendar where privacy is not a concern.

Because the template is set per calendar, one connection can pass full titles through while another shows only a block. A common setup keeps your own calendars readable and reduces the ones other people see to busy time.

What a copied event shows covers the title, description and location settings.

The Keeper.sh website has been rebuilt to answer the common questions before you sign up: which calendars it works with, how quickly changes land, what each plan costs, and what happens to the contents of your events.

There are pages for features and pricing, and the supported providers are named. The privacy behaviour is stated plainly: what a copy carries by default, what a shared link shows, and what is never copied on any plan.

The Free plan's limits are listed next to Pro's, so you can tell which plan a setup needs before you build it.

Keeper.sh pricing compares what Free and Pro include.

The Keeper.sh dashboard has been rebuilt around connections: which calendar copies into which. Each connection shows where events come from, where they land and what is copied, so you can check that your work calendar blocks time on your personal one at a glance.

Each calendar has its own page for the settings that apply to it, instead of every option sitting in one long form.

Sync status is shown, not inferred. You can see when a calendar was last read, whether the last run had a problem, and what that problem was.

What each calendar can do explains the settings on a calendar's page.

You can now connect a Google account to Keeper.sh by signing in, then pick which of its calendars Keeper.sh reads. Before this release, reading a Google calendar meant finding its secret iCal address, a link that is hard to locate, easy to leak, and only revocable by regenerating it.

Signing in lists the calendars on the account by name, so choosing between your own calendar and one shared with you is a matter of ticking the right box.

A calendar can now be both a source and a destination without feeding itself. Keeper.sh recognises the events it created and skips them when reading, so two accounts pointed at each other get one copy in each direction instead of a loop that grows on every run.

The two-way work and personal setup shows how to connect two calendars in both directions.

Keeper.sh can now read an Outlook calendar, not only write to one. Sign in with a Microsoft account, choose the calendar to read, and its busy time reaches every destination you have set up.

Before this release, Outlook could receive your busy time but not supply it, so a work calendar kept in Outlook could not block time anywhere else. One Microsoft account can now be both ends at once: Keeper.sh reads your work calendar and writes your personal one into the same account.

Google and Outlook now share one sync path, so a fix to how repeating events or timezones are handled lands for both providers at the same time.

Syncing Google Calendar and Outlook walks through a setup between the two.

Keeper.sh now connects iCloud, Fastmail and any other calendar that speaks CalDAV, the open standard for calendar access. Google and Outlook sign in directly, and CalDAV covers the Apple calendar on your phone and services such as Fastmail.

Connecting takes your address and an app password: a separate credential you generate for one application and can revoke on its own, without changing the password you sign in with. The connect dialog links to the page where iCloud and Fastmail issue app passwords.

A connected CalDAV calendar works like any other. Keeper.sh reads it on a schedule, sends its busy time to your other calendars, and can write into it as a destination. Any server that follows the standard works, including Nextcloud and Radicale.

What each calendar service asks for lists the details iCloud, Fastmail and CalDAV servers need.

Keeper.sh now imports any calendar from its iCal subscription link. Give the calendar a name, paste the link, and its events start arriving. Added calendars are listed on the integrations page and can be removed at any time.

Some links are not public. When a link asks for credentials, Keeper.sh prompts for a username and password instead of failing, so a work calendar behind basic authentication connects the same way a public one does.

When an import fails, the error names the cause: the link was unreachable, the credentials were refused, or the file was not a calendar. Keeper.sh then refetches each link on a schedule, so what it holds stays in step with the original.

What each calendar service asks for covers connecting every kind of calendar, links included.

Keeper.sh now writes your busy time into a Google calendar you connect. You choose which of your connected calendars feed it, and events from a calendar you have not mapped to that destination are never written.

Each mapping runs one way. A work calendar can feed your personal one without the reverse, and a shared calendar you only read can stay out of both. Set up the reverse connection as well when you want events to travel in both directions.

Keeper.sh tracks every event it creates in the destination. When the original changes or is deleted, the copy is updated or removed to match, so the destination does not fill up with stale blocks.

Sending events to another calendar explains connections, direction and how quickly a change lands.

Keeper.sh now publishes one iCal link that combines every calendar you have connected. Copy it from the integrations page and subscribe to it in any app that accepts a calendar URL: another calendar app, a scheduling tool, or a colleague's calendar.

The subscriber gets your busy time from every source in one subscription, instead of one subscription per calendar and the job of keeping that list current.

The link carries availability, not detail. Someone reading it sees the hours you are unavailable without seeing what you are doing in them, so you can share it with people who have no access to your calendars.

Shareable calendar links covers what a link carries and who can read it.