dufs-mcp-server
Provides an MCP (Model Context Protocol) server that wraps the dufs API to perform file operations (upload, download, list/search, delete, create directory, move/rename, compute SHA256, and download a folder as a ZIP) using either stdio (MCP-native) or HTTP/SSE endpoints. Supports Basic Auth and configuration via environment variables.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Security guidance is limited in the README. TLS enforcement is not explicitly stated; HTTP mode is described, so it may rely on deployment configuration. Basic Auth is supported but appears coarse-grained (no scopes described). No information is provided about password storage/logging or transport-layer security, so scores assume typical environment-variable handling but cannot verify. Dependencies are claimed to be Go standard library only, which is a positive signal for dependency hygiene.
⚡ Reliability
Best When
You want a lightweight Go-based MCP wrapper around an internal dufs server and your MCP client can connect via stdio or HTTP/SSE.
Avoid When
You need strong auth (beyond Basic Auth) or strong operational guarantees (documented SLAs, retry/idempotency semantics, and comprehensive error taxonomy) for critical production automation.
Use Cases
- • Integrate dufs-backed file management into MCP-capable AI agents (e.g., for uploading/downloading artifacts).
- • Automate remote file browsing and retrieval (list/search, hash verification).
- • Perform file lifecycle operations (create/move/delete) from an agent workflow.
- • Batch uploads with asynchronous status polling via MCP tools.
- • Package remote directories as ZIP for download.
Not For
- • High-security, public-facing deployments without additional network controls (e.g., direct internet exposure).
- • Environments requiring fine-grained authorization beyond Basic Auth or requiring OAuth/SSO.
- • Use cases needing a standardized REST/SDK contract for third-party developers (MCP tools are the primary interface).
Interface
Authentication
README indicates Basic Auth support via DUFS_USERNAME/DUFS_PASSWORD. No scope model is described.
Pricing
Agent Metadata
Known Gotchas
- ⚠ HTTP/SSE mode exists, but the primary/recommended path is stdio; some MCP clients may require specific transport configuration.
- ⚠ Batch upload returns a job_id and requires follow-up status polling; agents must implement that second step to obtain results.
- ⚠ No documented rate-limit or retry/backoff guidance; agents should be cautious with repeated calls, especially for delete/move operations.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for dufs-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.