Blackout vs Filesystem

A side-by-side look at the Blackout and Filesystem MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Blackout logoBlackoutFile Systems · Local subprocess (stdio)Permanent local PDF redaction: text is removed and verified gone, not covered. No uploads.37FairAuth: not declaredFilesystem logoFilesystemFile Systems · Local subprocess (stdio)Secure file operations with configurable access controls.85ExcellentAuth: no auth required

Verdict: choose Blackout for file systems work as a local process; choose Filesystem for file systems as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Blackout logoChoose Blackout when

  • You need dedicated capabilities in the File Systems domain.
  • You prefer a local stdio subprocess transport.
Explore Blackout

Filesystem logoChoose Filesystem when

  • You need dedicated capabilities in the File Systems domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like path, head, tail.
Explore Filesystem

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBlackout logoBlackoutFilesystem logoFilesystem
CategoryFile SystemsFile Systems
Quality signal37/100 · Fair85/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars091,526
Directory activity 0 views 0 installs 0 upvotes 11 views 0 installs 0 upvotes
ToolsNot listed17

Tools & capabilities

Blackout tools

No tool names declared yet. Check the project README from the listing page.

Filesystem tools 17

  • path
  • head
  • tail
  • paths
  • content
  • edits
  • oldText
  • newText
  • dryRun
  • sortBy
  • source
  • destination
  • +5 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Blackout

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "blackout": {
      "command": "npx",
      "args": [
        "-y",
        "@thrain/blackout"
      ]
    }
  }
}

Filesystem

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem"
      ]
    }
  }
}

Frequently asked questions

Blackout is categorized under File Systems and uses a local stdio subprocess. Filesystem belongs to File Systems and uses a local stdio subprocess. Pick Blackout for file systems work and Filesystem for file systems.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Blackout has no declared pricing — check the project's own site. Filesystem is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add blackout and filesystem as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Blackout has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Filesystem has 85/100 (Excellent) with 11 views, 0 installs and 91,526 GitHub stars.