Self-hostable calendar MCP service for Keeper.sh that lets Claude list calendars and accounts, read events, create or update events, delete events, respond to invites, and retrieve iCal feed URLs through Keeper's API.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
5 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.
Safety & privacy surface
5 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, permissions & scopes, third-party handling.
Disclosure: AGPL-3.0-licensed open-source Keeper.sh project with optional hosted service. The MCP service is source-backed and self-hostable, but it controls sensitive calendar data and should be deployed with production-grade auth and logging.
{
"mcpServers": {
"keeper": {
"type": "http",
"url": "https://<keeper-host>/mcp",
"headers": {
"Authorization": "Bearer <keeper-mcp-token>"
}
}
}
}Keeper.sh MCP Server is the dedicated MCP service in Keeper.sh, an open-source calendar sync platform. It exposes authenticated calendar tools for connected Keeper accounts, letting Claude list calendars and accounts, read events, create or update events, delete events, respond to invitations, and retrieve an iCal feed URL through Keeper's API.
Use it when a team wants a self-hostable calendar MCP service that can sit behind Keeper's auth and connected-provider model rather than relying on a single hosted Google Calendar MCP integration.
These sources were reviewed on 2026-06-06. Prefer the live repository, README, license, MCP package metadata, toolset, handler, context, environment, route, and Dockerfile for current setup and behavior details.
@keeper.sh/mcp service as part of a Keeper
deployment.Deploy Keeper.sh with the MCP service, set the required MCP environment variables, and expose the MCP route through the same trusted Keeper deployment:
BETTER_AUTH_URL=https://<keeper-host>
MCP_PUBLIC_URL=https://<keeper-host>/mcp
MCP_PORT=3002
Then configure an MCP client with the Keeper MCP endpoint and an authorized bearer token:
{
"mcpServers": {
"keeper": {
"type": "http",
"url": "https://<keeper-host>/mcp",
"headers": {
"Authorization": "Bearer <keeper-mcp-token>"
}
}
}
}
Keep the MCP service behind TLS and the same access controls used for the Keeper web and API services.
Keeper's MCP service can read and mutate calendar data. Require explicit approval before event creation, updates, deletes, or RSVP changes, and keep tool requests bounded to specific calendars and date ranges where possible. A bearer token used by the MCP client should be treated like calendar account access.
Calendar data is highly personal and operationally sensitive. Event titles, descriptions, locations, free/busy status, account names, calendar names, feed URLs, OAuth tokens, CalDAV credentials, database URLs, auth secrets, logs, and MCP transcripts can expose private schedules or credentials. Use TLS, least-privilege tokens, encryption keys, audit logs, backups, and redaction before sharing any troubleshooting material.
No ridafkih/keeper.sh, Keeper.sh MCP, Keeper calendar MCP, self-hosted
calendar MCP, CalDAV MCP, or matching source URL entry was found in
content/mcp or README.md. The existing CalendarMCP entry covers a hosted
Google Calendar service; it does not cover Keeper's self-hostable multi-provider
calendar sync platform and dedicated MCP service.
Show that Keeper.sh MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/keeper-sh-mcp-server)Keeper.sh MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Self-hostable calendar MCP service for Keeper.sh that lets Claude list calendars and accounts, read events, create or update events, delete events, respond to invites, and retrieve iCal feed URLs through Keeper's API. Open dossier | MCP server for Coolify infrastructure management, diagnostics, deployments, logs, projects, environments, applications, databases, services, env vars, storage, scheduled tasks, private keys, cloud tokens, teams, and docs search. Open dossier | Official freee MCP server for connecting Claude to freee accounting, HR, invoices, project time, sales, IT management, and e-signature APIs. Open dossier | macOS app and bundled stdio MCP server that lets Claude access selected local services such as Calendar, Contacts, Messages, Location, Maps, Reminders, camera, microphone, screenshots, Shortcuts, utilities, and Weather. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | Not reviewed | Not reviewed | Not reviewed | Not reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| Submitter | oktofeesh1 | oktofeesh1 | oktofeesh1 | oktofeesh1 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | ||||
| Category | mcp | mcp | mcp | mcp |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | ridafkih | Stuart Mason | freee | Mattt |
| Added | 2026-06-06 | 2026-06-06 | 2026-06-06 | 2026-06-06 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓Keeper's MCP tools can read calendar data and perform write operations including event creation, event updates, event deletion, and RSVP changes. The MCP handler requires an authenticated bearer token and checks for the Keeper MCP read scope before exposing tools. Tool calls proxy to Keeper API endpoints with the caller's bearer token, so the MCP client inherits the user's connected calendar permissions. Start by listing calendars and reading bounded date ranges; require human confirmation before modifying or deleting events. Review Google, Microsoft, iCloud, CalDAV, ICS, and self-hosted calendar account permissions before exposing them to an agent. | ✓Coolify MCP Server can start, stop, restart, redeploy, cancel deployments, update env vars, create or delete projects, environments, applications, databases, services, backups, storages, scheduled tasks, private keys, GitHub apps, and cloud tokens depending on API permissions. Batch tools such as `restart_project_apps`, `bulk_env_update`, `stop_all_apps`, and `redeploy_project` can affect multiple production services at once. Deployment, control, backup, storage, private key, cloud token, GitHub app, and scheduled-task operations should require explicit confirmation. Custom `--header` values may carry auth-proxy secrets; never let an agent invent, log, or modify them casually. Test on non-production projects or staging resources before allowing Claude to operate live Coolify infrastructure. | ✓freee MCP can perform GET, POST, PUT, PATCH, and DELETE requests against supported freee APIs after OAuth authorization. Write and delete operations can create, update, or remove accounting deals, expense applications, invoices, quotations, payment requests, HR records, attendance data, project time, sales records, IT assets, and e-signature documents. The server validates API paths against OpenAPI schemas and checks company ID consistency, but users must still confirm business, accounting, payroll, and legal actions before execution. OAuth tokens, client secrets, selected company IDs, and request payloads should be protected in configs, local storage, logs, and screenshots. Use the official Remote MCP URL only; do not connect clients to unofficial endpoints that claim to be freee. | ✓iMCP can expose highly sensitive personal macOS services to Claude through MCP tools. Calendar, Contacts, Reminders, and Shortcuts tools can create, update, or run actions, not only read data. Capture tools can take pictures, record microphone audio, and capture screenshots when the corresponding service is enabled and macOS permission is granted. Messages access can read local message history after the user grants access to the Messages database. The app can add or update the iMCP entry in Claude Desktop MCP configuration while preserving other server entries. Enable only the services needed for a task and do not mark clients as trusted unless you want repeated connections to bypass prompts. |
| Privacy notes | ✓Calendar events can expose titles, descriptions, locations, free/busy status, account names, provider names, calendar names, calendar URLs, and iCal feed URLs. OAuth tokens, CalDAV credentials, session tokens, bearer tokens, auth secrets, encryption keys, database URLs, and MCP URLs are sensitive deployment data. Keeper stores and syncs calendar data across connected providers; logs, MCP transcripts, API responses, and monitoring traces can include private schedule details. Redact event ids, calendar ids, account names, feed URLs, bearer tokens, event text, locations, and provider details before sharing debug output. | ✓Coolify access tokens, base URLs, custom headers, application UUIDs, server IPs, domains, logs, env vars, deployment logs, private keys, cloud-provider tokens, GitHub app data, team membership, backups, database metadata, and service configuration can be exposed to the MCP client. Application and deployment logs may contain secrets, customer data, build output, container metadata, private repository details, and runtime errors. Environment variable and cloud-token tools can reveal or mutate sensitive infrastructure credentials. Documentation search is local to the server, but Coolify API calls contact the configured Coolify instance. Keep tokens and auth-proxy headers in local MCP client configuration only, and avoid sharing transcripts that include infrastructure identifiers or logs. | ✓Tool calls can expose company IDs, user details, accounting transactions, bank and wallet metadata, invoices, receipts, expense applications, payroll and HR records, attendance data, employee profiles, project workloads, customer and partner data, IT assets, and e-signature documents. freee receives API requests, OAuth tokens, request parameters, uploaded files, and business data according to the user's freee account, API scopes, and selected company. Local mode stores OAuth configuration and tokens on the user's machine; remote mode authenticates through freee's hosted MCP flow. Generated reports, request errors, API responses, and skill references can enter MCP client context and model logs. | ✓Tool calls can expose contacts, phone numbers, email addresses, calendars, event details, reminders, message text, participants, location, routes, map queries, screenshots, camera images, audio snippets, shortcut names, and weather/location context. iMCP's README states that iMCP does not collect or store user data, but MCP clients and model providers can receive tool-call data as part of the conversation. Local logs, screenshots, approval dialogs, MCP transcripts, Claude Desktop config, and trusted-client settings may reveal private service access and personal-data context. Review every service toggle and macOS permission before enabling iMCP for personal accounts, shared machines, work devices, or regulated data. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Connect Claude to Coolify for supervised self-hosted PaaS diagnostics, deployments, resource management, logs, env vars, cloud tokens, and docs.
Use freee's official Remote MCP or local npm server for OAuth-backed business operations across accounting, HR, invoices, sales, IT, and signing workflows.
Source-backed guides for putting this to work.
Run AI dev tools, MCP servers, models, and memory on infrastructure you own.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.