Megfile
Give your coding agent one skill and CLI for reading, writing, and path logic across local disks, S3/OSS, SFTP, WebDAV, HTTP, HDFS, and stdio without rewriting adapters per environment.
Overview
Megfile is a plugin marketplace for the Build phase that adds a Claude Code skill and CLI for unified filesystem operations across local, cloud, and protocol-backed storage.
What is this marketplace?
- Single SmartPath and API surface over local FS, S3/OSS, SFTP, WebDAV, HTTP, HDFS, and stdio
- Megfile CLI plus agent skill for configuration and routine filesystem tasks
- Megvii Research–maintained plugin marketplace with one core megfile plugin bundle
- Reduces bespoke boto/oss/sftp glue when solo builders move artifacts between cloud and laptop
- Marketplace bundles 1 plugin: megfile (unified FS APIs, SmartPath, CLI).
What problem does it solve?
Agents and scripts break when every environment uses a different SDK or URL style for the same read-and-write job.
Who is it for?
Indie builders shipping data-heavy backends, ML-adjacent tooling, or agents that must touch S3/OSS and local trees in one workflow.
Skip if: Teams that only ever read files inside a single git repo on disk and do not need cloud or remote protocols.
What do I get? / Deliverables
After you add the marketplace, Claude can reason about paths and file tasks through megfile’s shared APIs and CLI instead of reinventing per-backend code each session.
- Megfile skill available in Claude Code for filesystem task guidance
- CLI and configuration patterns for cross-backend file operations in your project
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Filesystem and object-store access is where backends, data jobs, and deploy scripts meet external systems—canonical home is Build while integrations are wired. Megfile is an integration layer (SmartPath, unified APIs, CLI), not a UI or test runner; it belongs on the integrations shelf.
How it compares
Filesystem integration toolkit and CLI skill, not an MCP server catalog or project-memory plugin.
Common Questions / FAQ
Who is Megfile for?
Solo and indie developers who use Claude Code and need one skill to handle files on laptops plus S3, OSS, SFTP, WebDAV, HTTP, HDFS, or stdio without swapping libraries every time.
When should I use Megfile?
Use it while building or operating scripts and agent workflows that copy, list, sync, or configure paths across mixed storage backends during integration and deploy work.
How do I add Megfile to my agent?
Register the tianlianghai/Megfile-claude-skill Claude marketplace in Claude Code, install the Megfile plugin from the bundle, configure credentials for your remote backends, then invoke the skill or CLI from your session.