keeper.sh
Calendar sync tool & universal calendar MCP server. Aggregate, sync and control calendars on Google, Outlook, Office 365, iCloud, CalDAV or ICS.
No outside reports on file
Using this tool requires trusting it with real calendar credentials and accepting that all your event data flows through external services; misconfiguration or an attack could alter your schedule or expose sensitive meeting information.
Based on public adoption and transparency signals as of Oct 22, 2026. Our opinion, not a code audit or security guarantee.
What it can access
- Local filesReads local filesNOTED
- Command executionNo shell command runner notedLOW
- Network reachLocal or standard API callsLOW
- CredentialsRequires API key or tokenREVIEW
- Package sourceGitHub (ridafkih/keeper.sh)PUBLIC
Inferred from this listing’s public package details and description. Check the project’s source before installing.
Install
No npm or PyPI package is listed. Install from source: github.com/ridafkih/keeper.sh ↗
Everything known
We found nothing about this project in the sources we read (last checked 2026-10-30). That does not mean it has no problems.
0 incidents · 0 advisories · 0 news articles · 0 community threads · checked 2026-10-30
Popularity grade: C (from public signals such as stars and downloads, not a code review). Graded 2026-10-22.
Sources we read: OSV, GitHub Advisory Database, CISA Known Exploited Vulnerabilities, 44 security news feeds and our incident library. Last checked 2026-10-30.
About Keeper.sh
This tool connects Claude to your calendar accounts (Google, Outlook, iCloud, CalDAV, and others) so Claude can read, create, and manage events across multiple calendars. It acts as a middleman that aggregates your calendar data into one place and lets Claude interact with it.
Who it’s for
People who use multiple calendar services and want Claude to help organize, sync, or manage their schedules. It's aimed at developers and power users who can set up MCP connectors.
Alternatives
- Built-in calendar integrations in productivity apps (Notion, Zapier) for simpler use cases. - Native Google Calendar or Outlook APIs if you only need one service. - ICAL-based tools like Nextcloud for self-hosted calendar aggregation without AI.
Setup
Check these steps against the project’s own instructions before running anything.
Follow the project's README for installation instructions. The setup likely involves providing calendar credentials and configuring which services to connect.
Why this grade
Signal-based grade (3/7 points): well starred on GitHub, public source code. This reflects adoption and transparency, not a code review.
Popularity and upkeep
- GitHub stars
- 1.4k
- Listing last refreshed
- 2026-10-29
These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.
Risks to watch for
- Calendar credential exposure: You must give this tool access to your Google, Outlook, iCloud, or other calendar accounts; compromised credentials could expose all your events and let attackers create fake meetings. - Malicious event injection: An attacker could craft calendar events with hidden instructions designed to trick Claude into performing unwanted actions. - Data leakage to Claude: Your calendar details (times, attendees, descriptions) get sent to Claude's servers; very sensitive meeting notes could be exposed. - Sync failures or data loss: Bugs in the sync logic could delete events or fail to update calendars correctly, leaving you out of sync with reality. - Wide permission scope: Calendar access often grants permission to create and modify events, not just read them; a bug or attack could modify your schedule without your knowledge.
How to lower the risk
Least-privilege permissions
- Only connect the calendar accounts you actually need Claude to access. - Use service account credentials or app-specific passwords instead of your main account password if possible.
Network isolation
- Run this MCP server on a trusted machine with no public internet exposure. - Keep your calendar service credentials in environment variables, never hardcoded in files.
Monitoring
- Periodically review your calendar accounts' recent access logs for unexpected activity. - Watch for events you didn't create appearing in your calendars.
Red flags to watch for
- Unexpected "read" errors or sync failures that block access to your own calendars. - Claude suggesting it created events you don't remember asking for.
Questions
How do I install Keeper.sh?
Keeper.sh does not publish a standalone npm or PyPI package. Clone or follow the setup instructions in its source repository at github.com/ridafkih/keeper.sh.
Are there security reports about Keeper.sh?
No reports found for this package in our research (last checked 2026-10-30). Keeper.sh currently holds Grade C (Moderate risk signals) based on public adoption and transparency signals. Key risk areas to watch include calendar credential exposure.
Is Keeper.sh actively maintained?
Keeper.sh has 1.4k GitHub stars. Our directory data was last refreshed on 2026-10-29. Check recent commit activity, release tags, and open issues at github.com/ridafkih/keeper.sh before pinning it in production.
What are alternatives to Keeper.sh?
Notable alternatives to Keeper.sh include Built-in calendar integrations in productivity apps. You can also compare Keeper.sh side by side with other MCP servers in the Related tools section on this page.
README badge and team notes
Maintain or use Keeper.sh? Show its live grade in your GitHub README, docs site, or run a check from the terminal before you install.
GitHub README Markdown:
[](https://agentarmorhq.com/skills/ridafkih-keeper-sh)HTML embed:
<a href="https://agentarmorhq.com/skills/ridafkih-keeper-sh"><img src="https://agentarmorhq.com/api/badge/ridafkih-keeper-sh" alt="AgentArmorHQ Risk Grade for Keeper.sh" height="20" /></a>Terminal check:
curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "ridafkih-keeper-sh"Share with your security lead
Need sign-off to use keeper.sh? Copy this note for Slack, a ticket or a pull request.
### AgentArmorHQ Security Review Memo: keeper.sh
- **Listing URL:** https://agentarmorhq.com/skills/ridafkih-keeper-sh
- **Type:** App connector
- **Risk Grade:** Grade C (Moderate risk signals)
- **Outside Security Advisories on File:** 0
- **Public Adoption:** 1.4k GitHub stars
#### Permission & Blast-Radius Signals
- **Local files:** Reads local files
- **Command execution:** No shell command runner noted
- **Network reach:** Local or standard API calls
- **Credentials:** Requires API key or token
- **Package source:** GitHub (ridafkih/keeper.sh)
#### Recommended Hardened Setup
- **Source Repo:** https://github.com/ridafkih/keeper.sh
- **Controls:** Pin an exact version in `.mcp.json`, scope access to a single workspace folder, and use a least-privilege read-only token where supported.
_Based on public adoption and transparency signals as of Oct 22, 2026. Our opinion, not a code audit or security guarantee._Key facts
- Type
- App connector
- Publisher
- ridafkih
- Source code
- github.com/ridafkih/keeper.sh
- Est. context load
- ~1.2k tokens / turn (~7 tool schemas, 0.6% of 200k context)
- Popularity
- 1.4k GitHub stars
- Last updated
- 2026-10-29
- Last graded
- 2026-10-22
Community
Discussions for Keeper.sh
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.
Check before you install, in Claude
Your assistant answers Block, Review or No known issues for any package before it installs it.
Get this check inside Claude