fanchenggang/Davflare

Self-hosted cloud drive on Cloudflare R2 — web file manager + WebDAV, with chunked uploads, expiring share links, trash, thumbnails, search & API keys. | A free private cloud drive based on Cloudflare R2: web file management + WebDAV service, fully serverless deployment with Pages & Workers, chunked uploads for large files, share links with optional expiration, trash, thumbnails, search, and an open API

100Stars on the repository
6Mods indexed here, across every type
yesterdayLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

hello-site

01

fanchenggang/Davflare

Skill Claude CodeCodex

Reproduce a Davflare static site with existing MCP tools only (publishsite / imageupload). Use when onboarding or demoing “chat → site”.

not rated 100 +4 yesterday A SkillSpector: pass 33 tokens original MIT

obsidian-sync

02

fanchenggang/Davflare

Skill Claude CodeCodex

Set up and verify free Obsidian sync (Remotely Save plugin → Davflare WebDAV). Use when a user asks to sync an Obsidian vault to their Davflare drive.

not rated 100 +4 yesterday A 43 tokens original MIT

mcp-export

03

fanchenggang/Davflare

Skill Claude CodeCodex

Use when the user wants Cursor or Claude Desktop to call Davflare tools over /mcp.

not rated 100 +4 yesterday B 0 tokens original MIT

fanchenggang/Davflare

Skill Claude CodeCodex

Install the official Davflare agent skill from this repo. Prefer skills/davflare/SKILL.md via npx skills add.

not rated 100 +4 yesterday A 32 tokens original MIT

davflare

05

fanchenggang/Davflare

Skill Claude CodeCodex

Use Davflare (Cloudflare Pages + R2 self-hosted drive) via same-origin MCP /mcp (25 tools) and Open API — upload/download, shares, trash, publishsite to sites/{slug}/, image host. Use when the user mentions Davflare, FlareDrive, R2 drive MCP, static sites on SITESHOST, or connecting Cursor/Claude to a personal drive.

not rated 100 +4 yesterday B 85 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: