# Read and edit files in a folder the person chose

> Read and edit files in a folder the person chose: 0 companies fully do it, 2 with a limit, 2 carry the tag. Every listing in Databases & files with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/data.local-files/
- Markdown: https://www.anchorterminal.com/niches/data.local-files/index.md (~1,050 tokens)
- Slim: https://www.anchorterminal.com/niches/data.local-files/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/data.local-files/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 2 | 2 | 12 | 5 |

## 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.

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

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.

- **Mirage (AgentVFS) (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.
- **Filesystem (MCP reference server) (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.

- not this job: ClickHouse MCP Server (ClickHouse, Inc.): chDB can SELECT from files, but there are no edit or write tools for a folder.
- not this job: CoinMarketCap x402 API (CoinMarketCap): No file access.
- not this job: DBHub (Bytebase): A database server; it has no file tools.
- not this job: MCP Toolbox for Databases (Google LLC): No local file tools; Cloud Storage tools are object storage.
- not this job: Memory (MCP reference server) (Model Context Protocol, a Series of LF Projects, LLC): Writes only its own JSONL graph file; no tools to read or edit other files.
- not this job: MongoDB MCP Server (MongoDB, Inc.): No file tools.
- not this job: Nansen x402 API (Nansen): No file access.
- not this job: Neon MCP Server (Neon, LLC (subsidiary of Databricks, Inc.)): No file tools.
- not this job: ObsessionDB (Kellerkind UG (haftungsbeschränkt)): No file tools.
- not this job: PlanetScale MCP Server (PlanetScale, Inc.): No file tools.
- not this job: Postgres MCP Pro (Crystal Corp.): No file tools.
- not this job: Redis MCP (Redis Ltd.): No file tools.
- not this job: ReqRes MCP server (ReqRes): No file tools.
- not this job: Snowflake-managed MCP server (Snowflake Inc.): No local file tools.
- not this job: Supabase API + MCP (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

As data: https://www.anchorterminal.com/api/v1/use-cases/data.local-files.json, or the MCP tool get_use_case with id data.local-files. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
