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
Install
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 1. Clone the repo into a temporary folder (public HTTPS clone — no account needed) and look inside. Summarize it for me in one or two sentences. 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. Clone it and 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.
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 “verified” mean?
The product passed our open verification checklist — public repository, clear license, and no secrets or malicious code in the package. The badge is pinned to the exact version you see.