All MCP Servers

No recent activity. No commits in 6 months. It may still work, but issues are unlikely to be fixed. See 4 alternatives.

Dev Tools & GitMCP Registrynpm34 toolsB · 61

mcp-filesystem

io.github.Digital-Defiance · Updated

Advanced filesystem operations with strict security boundaries for AI agents

At a glance

mcp-filesystem is an MCP server in the Dev Tools & Git category. It runs locally over stdio via `npx -y @ai-capabilities-suite/mcp-filesystem`, and needs WORKSPACE_ROOT. It exposes 34 tools, including screenshot_capture_full, screenshot_capture_window and screenshot_capture_region. It scores B (61/100) on the MCP Skills Hub health score as of Oct 27, 2026.

Source 3GitHub stars

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install mcp-filesystem in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install mcp-filesystem in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add mcp-filesystem -e 'WORKSPACE_ROOT=<WORKSPACE_ROOT>' -- npx -y @ai-capabilities-suite/mcp-filesystem
  2. Fill in your credentials

    Replace <WORKSPACE_ROOT> with your real value. Keep secrets out of any config file you commit.

  3. Verify it's connected

    bash
    claude mcp list
  4. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  5. Use it in a session

    Ask Claude to use the tools this server exposes (e.g. screenshot_capture_full, screenshot_capture_window, screenshot_capture_region). It discovers them automatically.

What does mcp-filesystem need from you?

Configuration only — Declares config values but no credentials.

  • WORKSPACE_ROOTrequiredEnvironment variable

    Absolute path to workspace directory (all operations confined here)

Pass secrets through your shell environment rather than committing them into a config file.

What tools does mcp-filesystem expose? (34)

Taken from the project's README — the server itself was not queried, so check its docs for the exact schemas.

What the code can do

Read from the published package source — never executed. Parsed 27 of 27 source files.

This server can read and write files and read your environment variables.

How it was published

  • No provenance attestation — there is nothing linking this published artifact to a specific source commit.
  • 1 npm maintainer — a single point of compromise · last published by jessica-mulein.

Maintainer of this package and think something here is wrong? Tell us and we'll correct it.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
  • Downloads at launch — The package is fetched from its registry each run unless you pin a version.
  • Last commit 6 months ago — No commits in over six months.
  • 3 GitHub stars — Very little community usage so far.
  • Package repo does not match registry entry — The npm package points at Digital-Defiance/mcp-filesystem, while the registry lists Digital-Defiance/ai-capabilities-suite. Worth confirming you are installing what you think you are.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 61

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%75%

    Last commit 202 days ago.

  • Adoption20%18%

    3 stars.

  • Transparency20%100%

    4/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✓ discoverable tool list.

  • Provenance15%0%

    The package's declared repository does not match the registry entry.

  • Packaging15%100%

    Publishes a pinned version (0.1.9).

Documentation

Full README

🚀 AI Capability Extension Suite

What if AI agents could actually _see_, _debug_, and _control_ your development environment?

We've built the most comprehensive suite of MCP servers that give AI agents superpowers they've never had before. This isn't just another tool collection—it's a paradigm shift that transforms AI assistants from code generators into intelligent development partners with runtime visibility, system control, and physical world access.

📝 Note: All packages have been split into individual Git submodules with their own repositories for better maintainability and independent versioning. Each package now has its own dedicated repository under the Digital-Defiance organization.


📦 Quick Index

🐛 MCP ACS Debugger

25+ debugging tools for AI agents | VS Code Extension | NPM | Docker

  • ✅ VS Code Extension with GitHub Copilot integration
  • ✅ 94.53% test coverage, 1,059 tests
  • ✅ Performance profiling, hang detection, advanced breakpoints
  • 🎯 Kiro Superpower in development - Enhanced AI debugging workflows

📸 MCP ACS Screenshot

Visual UI capture and analysis | VS Code Extension | NPM | Docker

  • ✅ Full screen, window, and region capture
  • ✅ PII masking with OCR integration
  • ✅ 267 tests, cross-platform support
  • 🎯 Kiro Superpower in development - AI-powered visual analysis

⚙️ MCP ACS Process

Enterprise-grade process management | VS Code Extension | NPM | Docker

Excerpt — the full document is on GitHub.

Maintain mcp-filesystem? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![mcp-filesystem on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-digital-defiance-mcp-filesystem)](https://mcp-skills-hub.vercel.app/mcps/io-github-digital-defiance-mcp-filesystem)

Catalog data refreshed . Something wrong? Report it.