Muse Proxy
Let Muse reach your self-hosted calendars without ever seeing your passwords
- What
- Let Muse reach your self-hosted calendars without ever seeing your passwords
- Cost
- Free
- Needs
- A Cloudflare account and a CalDAV/CardDAV account (Google, iCloud, Fastmail, Nextcloud…). You'll deploy the Worker on your own Cloudflare account.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Muse Proxy is a Cloudflare Worker gateway for services that normally need a username and password. Store your CalDAV/CardDAV credentials once, hand your Muse scoped API keys, and let it read or edit your self-hosted calendars — your passwords stay on the server, never in the agent's hands. One-click deploy; your Muse configures itself by reading the gateway's own docs. Honest heads-up from the author: the repo is ‘written by agents, for agents’ and lightly reviewed.
Curated by Skill Harbor — free, open-source build (MIT) by @NeedsChloesure.
Version: 1.0.0
Quick answer
Muse Proxy is a free Muse skill that lets Muse reach your self-hosted calendars without ever seeing your passwords. It is a Cloudflare Worker gateway: store your CalDAV and CardDAV credentials once, hand your Muse scoped API keys, and let it read or edit your calendars and contacts through the gateway, while your real passwords stay out of reach.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 13428b5Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: A Cloudflare account and a CalDAV/CardDAV account (Google, iCloud, Fastmail, Nextcloud…). You'll deploy the Worker on your own Cloudflare account. No GitHub account needed unless listed here. Install "Muse Proxy" for me. A Cloudflare Worker gateway that gives your Muse access to your own calendars and contacts via CalDAV/CardDAV. Repository: https://github.com/needschloesure/muse-proxy Pinned version: install the code at commit 13428b5e216fded47db54181975d0388872518e9 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone the repo into a temporary folder (public HTTPS clone — no account needed) and look inside. 2. Safety check: briefly review any scripts for anything suspicious (network calls to unexpected hosts, shell commands, credential harvesting). It will store your calendar credentials and mint a scoped API key for your Muse — that's by design. Never paste passwords into chat; use the secure credential flow. If you see a red flag, stop and tell me before going further. 3. Set up everything you can: install dependencies and configure the non-secret parts. Then give me the exact remaining manual steps (usually: I create the account myself, deploy, and provide keys through my secure credential flow — never ask me to paste secrets into chat). 4. Verify without network calls: everything doable locally is done; clearly list what's left for me. 5. Report: what you installed, where, and anything still left for me to do myself (or confirm there's nothing left). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it (e.g. authenticated clone); otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
- It works with an API key or a token that you provide.
What the scan found — excerpts from the install prompt
- uses API keys or tokens — 2. Safety check: briefly review any scripts for anything suspicious (network calls to unexpected hosts, shell · 2. Contrôle de sécurité : passe brièvement en revue les scripts pour repérer tout comportement suspect (appels
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 13428b5 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Install prompt analysis
- 2026-10-13 : uses API keys or tokens
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.