Win-10-MCP-Server---Simple-persistant-logging

@trevorwilkerson

Repository

About Win-10-MCP-Server---Simple-persistant-logging

No overview available yet

#logging #file-management #backup

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Win-10-MCP-Server---Simple-persistant-logging?

A customized version of the official @modelcontextprotocol/server-filesystem MCP server that adds persistent logging and automatic file backups. Created to combat Claude Desktop’s tendency to write incomplete files, it logs all write_file operations and creates timestamped backups before overwriting existing files.

How to use Win-10-MCP-Server---Simple-persistant-logging?

Replace the standard index.js inside server-filesystem/dist with the provided modified version and place logger.mjs in your project root. The server will then log all write_file calls to logs/KAN_server.log and create a backup of any existing target file with a .MMDDYY_HH_MM__CLDBak suffix before writing.

Key features of Win-10-MCP-Server---Simple-persistant-logging

Creates a timestamped backup of the target file before every write_file call
Logs all file operations to a persistent logs/KAN_server.log file
Returns the backup filename in the response for immediate user notification
Validates file paths to restrict writing to a controlled directory
Runs on Node.js without any additional dependencies

Use cases of Win-10-MCP-Server---Simple-persistant-logging

Recovering when Claude Desktop writes incomplete files due to lazy output
Auditing file change history for MCP-driven file editing sessions
Providing a simple diff-based workflow to verify and fix Claude’s changes

FAQ from Win-10-MCP-Server---Simple-persistant-logging

Does this work with the official @modelcontextprotocol/server-filesystem?

Yes, it is a direct modification of that server’s index.js (found at C:\Users\TrevorW\AppData\Roaming\npm\node_modules\@modelcontextprotocol\server-filesystem\dist on Windows).

What are the runtime requirements?

Node.js with the @modelcontextprotocol/server-filesystem npm package installed globally.

Where are logs and backups stored?

Logs are written to logs/KAN_server.log in the project root. Backups are saved in the same directory as the target file with a .MMDDYY_HH_MM__CLDBak suffix.

Are there any known limitations?

The modified code restricts writes to a base directory called Control_Charts (relative to the current working directory). Other paths are rejected.

Does this change the MCP transport or authentication?

No, it only modifies the write_file handler’s logic. Transport, authentication, and all other MCP protocol features remain unchanged from the official server.

Frequently asked questions

Does this work with the official @modelcontextprotocol/server-filesystem?

Yes, it is a direct modification of that server’s `index.js` (found at `C:\Users\TrevorW\AppData\Roaming\npm\node_modules\@modelcontextprotocol\server-filesystem\dist` on Windows).

What are the runtime requirements?

Node.js with the `@modelcontextprotocol/server-filesystem` npm package installed globally.

Where are logs and backups stored?

Logs are written to `logs/KAN_server.log` in the project root. Backups are saved in the same directory as the target file with a `.MMDDYY_HH_MM__CLDBak` suffix.

Are there any known limitations?

The modified code restricts writes to a base directory called `Control_Charts` (relative to the current working directory). Other paths are rejected.

Does this change the MCP transport or authentication?

No, it only modifies the `write_file` handler’s logic. Transport, authentication, and all other MCP protocol features remain unchanged from the official server.