Patch File MCP

Created By
PyneSysa year ago
An MCP Server to patch existing files using block format
Overview

what is Patch File MCP?

Patch File MCP is an MCP Server designed to patch existing files using block format, allowing AI agents to make precise changes to files in projects.

how to use Patch File MCP?

To use Patch File MCP, set up the MCP Client (like Claude Desktop) with the provided configuration, and the server will start automatically based on your settings.

key features of Patch File MCP?

  • Targeted changes to specific parts of files without rewriting the entire content.
  • Supports multiple patches to the same file in a single request.
  • Ensures safety through exact text matching and uniqueness verification.
  • Better alternative to the edit_block tool from desktop-commander for most file editing tasks.

use cases of Patch File MCP?

  1. Modifying configuration files in software projects.
  2. Applying updates to code files without rewriting them entirely.
  3. Assisting AI agents in making precise edits to project files.

FAQ from Patch File MCP?

  • Can Patch File MCP handle multiple edits at once?

Yes! It can apply several changes in a single operation using block format.

  • Is there a safety mechanism in place?

Yes! The tool ensures that search texts appear exactly once in the file to prevent incorrect modifications.

  • What programming language is Patch File MCP written in?

Patch File MCP is written in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
PyneSys
Star
0
Language
Python
License
MIT 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