File Edit Check MCP Server

Created By
punkpeyea year ago
MCP server that enforces pre-read checks and detailed commit documentation
Overview

what is File Edit Check MCP Server?

File Edit Check MCP Server is a server that enforces pre-read checks and detailed commit documentation to prevent blind modifications to files.

how to use File Edit Check MCP Server?

To use the server, install it via npm, build the project, and add it to your MCP settings file to enforce pre-read checks before file modifications.

key features of File Edit Check MCP Server?

  • Enforces pre-read verification before file modifications
  • Prevents blind writes and diffs
  • Provides detailed commit message guidance
  • TypeScript implementation with proper error handling

use cases of File Edit Check MCP Server?

  1. Ensuring that files are read before any modifications are made.
  2. Maintaining detailed commit documentation for better project tracking.
  3. Preventing accidental overwrites in collaborative environments.

FAQ from File Edit Check MCP Server?

  • What is the purpose of pre-read checks?

Pre-read checks ensure that users are aware of the current state of a file before making any changes, preventing blind modifications.

  • Is this server suitable for collaborative projects?

Yes! It is designed to enhance collaboration by enforcing checks and documentation.

  • How do I install the server?

You can install it using npm with the command npm install followed by npm run build.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
punkpeye
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