MCPs for reading, writing, and manipulating files
File operations MCP servers expose filesystem tools — read, write, search, move, diff — to AI agents. They are the prerequisite for any coding agent. Claude Code, Cursor, and Windsurf all build on file-operations MCPs for editing source code.
File operations MCPs expose filesystem primitives (read, write, move, search) to agents. They're the foundation for every coding agent — without them, an agent can't edit code, manage configs, or organize documents.
Every push to main triggers a Supabase migration automatically. Schema diffs are committed and applied with zero manual steps.
SonarQube analyzes every PR for code smells, coverage drops, and security hotspots. PRs below the quality gate are blocked.
Query Parquet files directly from S3 using DuckDB without any ETL. Results are returned in seconds for ad-hoc analytics.
MCP adds a permission layer (you can whitelist specific directories), audit trail, and cross-platform abstraction — Claude Code uses an MCP internally for this reason.
Yes — every file MCP supports path allowlists and denylists. This is critical for security when agents run in production.
File MCPs support streaming reads/writes and chunked uploads for large files (>10MB). S3 and Google Drive MCPs use multipart upload for very large files.
Yes — most file MCPs expose `search` or `grep` tools that return matches with line numbers. Pair with embedding MCPs for semantic search.
Browse the full marketplace or explore all tags to find the right MCPs for your stack.