Read and edit files in a folder the person chose
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
The named files are read and edited in place, every path stays inside the allowed directories, nothing is written that the person did not ask for, and an edit that cannot apply says so.
Measured, for our own tests: a search over a 100,000-file tree returns or fails within 60 seconds. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: read these files and fix the bug
, refactor using the docs in this folder
, find every file that mentions the old API
, tidy my downloads folder
Does the job, with a limit 2
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Mirage (AgentVFS) B Strukto.AI | DiskVFS checks paths against the root to stop traversal and supports read or write mounts, but grep -r and find stop after 10,000 files, and #16 shows sessions sharing one mount tree so one agent's rm removes another's file. source |
| Filesystem (MCP reference server) B Model Context Protocol, a Series of LF Projects, LLC | Paths resolve against allowed directories including symlinks, --read-only withholds write tools, edit_file errors when oldText fails to match. Cloud folders get a 15-second per-call timeout, but timed-out calls keep running and can still slow the server, as #4162 saw. source |
Doesn't do this job 15
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| ClickHouse MCP Server BB ClickHouse, Inc. | chDB can SELECT from files, but there are no edit or write tools for a folder. source |
| CoinMarketCap x402 API BB CoinMarketCap | No file access. source |
| DBHub BB Bytebase | A database server; it has no file tools. |
| MCP Toolbox for Databases A Google LLC | No local file tools; Cloud Storage tools are object storage. |
| Memory (MCP reference server) B Model Context Protocol, a Series of LF Projects, LLC | Writes only its own JSONL graph file; no tools to read or edit other files. source |
| MongoDB MCP Server A MongoDB, Inc. | No file tools. |
| Nansen x402 API B Nansen | No file access. source |
| Neon MCP Server BB Neon, LLC (subsidiary of Databricks, Inc.) | No file tools. |
| ObsessionDB F Kellerkind UG (haftungsbeschränkt) | No file tools. |
| PlanetScale MCP Server BB PlanetScale, Inc. | No file tools. |
| Postgres MCP Pro F Crystal Corp. | No file tools. |
| Redis MCP C Redis Ltd. | No file tools. |
| ReqRes MCP server D ReqRes | No file tools. |
| Snowflake-managed MCP server C Snowflake Inc. | No local file tools. |
| Supabase API + MCP BB Supabase Pte. Ltd. | No local file tools. |
What stops agents finishing
- search hangs on cloud-provider paths until the client drops the server
- client tool-schema change makes every call fail after an upgrade
- no read-only mode in the server
Around it
Before: chat.user-names-files. After: code.ticket-to-pr.
Where this comes from
Weight 12 of 100 in Databases & files: 5 of 52 accounts on the filesystem reference server and Mirage; the filesystem server appears in most MCP starter guides, so weighted above its count
The same as data: /api/v1/use-cases/data.local-files.json, or the MCP tool get_use_case with id data.local-files. Other jobs in this category: /api/v1/niches?category=data.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.