MCPIgnore Filesystem is a security-focused filesystem MCP server that restricts what files and directories an MCP client (Claude, Cline, Cursor) can read, write, or modify, using .mcpignore files with the same pattern syntax as .gitignore. It provides standard filesystem operations while enforcing these access restrictions on every call.

Use it when you want to give an AI assistant filesystem access to a project or directory while explicitly excluding sensitive paths - secrets, credentials, .env files, or other data you don't want exposed to the model. Create a .mcpignore file in each allowed directory using .gitignore-style patterns to define what's off-limits. Do not use it if you need unrestricted filesystem access with no exclusion layer - a plain filesystem MCP server would suffice in that case; this server exists specifically to add a protective boundary.

• read_file, read_multiple_files, write_file, edit_file, create_directory, list_directory, move_file, get_file_info - all blocked for any path matching .mcpignore rules.
• directory_tree and search_files - allowed, but restricted to returning file names only, without exposing file content for ignored paths.
• list_allowed_directories - lists the directories the server is configured to operate within.

npx -y @cyberhaven/mcpignore-filesystem /Users/<username>/Desktop /path/to/other/allowed/dir

Register with an MCP client (Claude, Cline, Cursor):

{
  "mcpServers": {
    "mcpignore-filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@cyberhaven/mcpignore-filesystem",
        "/Users/<username>/Desktop",
        "/path/to/other/allowed/dir"
      ]
    }
  }
}

Create a .mcpignore file (using .gitignore syntax) inside each allowed directory to define which files and subpaths are blocked from the MCP client.

Developers and security-conscious teams who want to grant an AI assistant filesystem access to a project directory while guaranteeing sensitive files (secrets, credentials, private data) stay out of reach.