Filesystem

io.github.domdomeggPublished by GitHub account domdomeggv1.3.0Updated Oct 24, 2026

Read, create, and edit files.

VerifiedSTDIODesktop onlyFiles & StorageDeveloper Tools

Overview

AI-generated overview

A local MCP server that lets an assistant read, create, and edit files on your machine, including listing directories and making precise text replacements.

What you can do
Read files and list directories with line numbers using the view tool, so the assistant can inspect content and structure before acting. Create or overwrite files with the create tool. Edit existing files by replacing an exact string with str_replace, or by inserting text at a specific line with insert. Combine these steps for tasks such as updating a config value, renaming a function, writing a report, or saving a timestamped backup copy.
When to use it
Useful when you want the assistant to work directly with local files: inspecting code, making targeted edits, generating and saving reports, or copying files before changes. It fits desktop setups where the assistant should read and write files in your project or notes folders.
Requirements
Runs as a local process over stdio, installed from the npm package filesystem-mcp and started with npx, so Node.js and network access for the package are needed. The MCP_TRANSPORT environment variable is required. Setup is done through the install-mcp instructions for your MCP client. No authentication is declared.
Before you install
The server can create, overwrite, and modify files on your machine, and overwriting is not reversible unless you keep backups. Point it only at folders you are willing to let the assistant change, and review edits before relying on them.

Installation

In SourceWeft

  1. Open Filesystem in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

filesystem-mcp

MCP server for filesystem operations - read, create, and edit files.

Use Cases

Save email attachments: "Download all PDFs from my accountant's emails this month" → searches Gmail for matching emails, extracts attachments, and saves them to a local folder.

Update config files: "Change the API endpoint from staging to production in my config" → finds the config file, replaces the URL, and shows you the diff.

Generate reports: "Create a summary of today's calendar events" → reads your calendar, formats a markdown report, and saves it to your notes folder.

Code refactoring: "Rename the function getData to fetchUserData in src/api.ts" → reads the file, makes the precise replacement, and confirms the change.

Backup before changes: "Save a copy of my .zshrc before I modify it" → reads the current file and writes a timestamped backup.

Setup

Follow the instructions on install-mcp, which generates the right config for your MCP client (Claude Code, Claude Desktop, Cursor, Cline, VS Code, and more).

Tools

ToolDescription
viewRead file contents or list directory (with line numbers)
createCreate or overwrite a file
str_replaceReplace an exact string in a file
insertInsert text at a specific line

Contributing

Pull requests are welcomed on GitHub! To get started:

  1. Install Git and Node.js
  2. Clone the repository
  3. Install dependencies with npm install
  4. Run npm run test to run tests
  5. Build with npm run build

Releases

Versions follow the semantic versioning spec.

To release:

  1. Use npm version <major | minor | patch> to bump the version
  2. Run git push --follow-tags to push with tags
  3. Wait for GitHub Actions to publish to the NPM registry.

Source: README.md at commit 3fa9a0e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.3.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.