MCP serverValidated

Filesystem MCP — scoped file access outside the repo

The reference filesystem server: read/write access confined to directories you list explicitly — the clean way to give an agent a docs folder or a data directory without handing over your home directory.

io.modelcontextprotocol/server-filesystemOfficial docs →

A vetted listing, not an install — add the config to your MCP client yourself. CoSquared never writes MCP config.

Why this one

The reference implementation with the simplest security model in the ecosystem: access is exactly the allowlisted directories, nothing else.

How to use it

  1. 1List the narrowest directories that cover the task
  2. 2Never allowlist $HOME or a directory containing credentials

Client config

Placeholders only — bring your own values

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "YOUR_ALLOWED_DIRECTORY"
      ]
    }
  }
}

Security notes

Everything under the allowlisted directories is readable and writable by the agent. Dotfiles, .env files, and key material inside those paths are exposed — allowlist specific project/data folders, never a directory that contains secrets.