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

Created By
trevorwilkersona year ago
Overview

What is Win-10-MCP-Server - Simple Persistent Logging?

Win-10-MCP-Server - Simple Persistent Logging is a project designed to enhance the logging capabilities of MCP Servers by creating persistent logs on the hard drive, addressing issues with incomplete file writes.

How to use Win-10-MCP-Server?

To use this project, modify the index.js file in the specified directory to implement the logging functionality and ensure that the logger.mjs file is created in the project root to handle log file management.

Key features of Win-10-MCP-Server?

  • Automatic backup creation of files before writing new content.
  • Persistent logging of file operations with timestamps.
  • Error handling and logging for file access issues.

Use cases of Win-10-MCP-Server?

  1. Ensuring data integrity by backing up files before modifications.
  2. Monitoring file operations for debugging and auditing purposes.
  3. Providing a reliable logging mechanism for MCP Server operations.

FAQ from Win-10-MCP-Server?

  • Can this project handle all file types?

Yes, it can manage any file type as long as the path is validated.

  • Is there a limit to the number of backups created?

No, backups are created each time a file is modified, but you may want to implement a cleanup mechanism for old backups.

  • How does the logging mechanism work?

The logging mechanism appends log entries to a specified log file, capturing the operation details and any errors encountered.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
trevorwilkerson
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago