Muse File API
Let your Muse read and write your own computer's files — through your own tunnel
- What
- Let your Muse read and write your own computer's files — through your own tunnel
- Cost
- Free
- Needs
- Node.js, your own domain name, and a Cloudflare Tunnel.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A dependency-free local HTTP service, exposed via Cloudflare Tunnel, that lets Muse list, read and write files in whitelisted directories — with two-phase writes and an audit log. You run it on your own machine (Node.js only), expose it through your OWN domain and tunnel, and feed the connector brief to Muse through its secure credential flow. Honest heads-up: the project provides no public endpoint — everything is self-hosted; the README is primarily in Chinese.
Curated by Skill Harbor — free, open-source build (MIT) by @star-power0.
Version:
Quick answer
Muse File API is a free Muse skill that lets your Muse read and write your own computer's files, through your own tunnel. Security note: this build exposes your local files and shell commands to your Muse agent, so only expose directories you can afford to share.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 68cab5cStep 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: Node.js, your own domain name, and a Cloudflare Tunnel. No GitHub account needed unless listed here. Install "Muse File API" for me. A local HTTP service that lets your Muse list, read, write and manage files on your own computer, exposed through your own Cloudflare Tunnel. Repository: https://github.com/star-power0/muse-fileapi Pinned version: install the code at commit 68cab5c1176bf1473695a9955e8c8ad6ca8081e8 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). HIGH SENSITIVITY: this exposes YOUR files and can run shell commands on your machine. Keep the token secret, restrict allowedRoots to only folders you're comfortable sharing, and never expose it beyond your own tunnel. 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
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
- 68cab5c · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
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.