Vulcan File Ops

io.github.n0zer0d4yPublished by GitHub account n0zer0d4yv1.3.0Updated Oct 24, 2026

MCP server for AI assistants: read, write, edit, and manage files securely on local filesystem.

VerifiedSTDIODesktop onlyFiles & Storage

Overview

AI-generated overview

Local MCP server that lets an AI assistant read, write, edit and manage files on the user's own filesystem.

What you can do
  • Read files from the local filesystem
  • Write new files and edit existing ones
  • Manage files and directories on the local machine
When to use it
Useful when an assistant needs to work with files on your own computer, such as reading project files, creating documents or editing existing content, rather than with remote storage.
Requirements
Runs as a local process over stdio, installed from the npm package @n0zer0d4y/vulcan-file-ops, so Node.js and npm are needed. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Before you install
It can write and modify files on your local filesystem, so scope it to directories you are willing to let the assistant change and keep backups. The description gives no detail on sandboxing or path restrictions, and no README is available to confirm how access is limited.

Installation

In SourceWeft

  1. Open Vulcan File Ops 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.

Tools

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

Version history

2
  1. v1.3.0LatestOct 4, 2026
  2. v1.1.4Sep 16, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.