MCP HubMCP Hub
arathald

mcp-editor

by: arathald

Port of Anthropic's file editing tools to an MCP server

6created 31/01/2025
Visit
Anthropic
editing

📌Overview

Purpose: The mcp-editor aims to facilitate filesystem editing through a TypeScript MCP server, inspired by Anthropic's filesystem tools.

Overview: This framework serves as a direct port of Anthropic's filesystem editing capabilities, optimized for a TypeScript environment. Developed by Claude Sonnet 3.5, it allows users to interact with the computer's filesystem while emphasizing the importance of client-side approval for write operations.

Key Features:

  • Seamless Integration: Easily integrates with existing MCP server commands and setups, allowing users to extend functionality and tailor their server environment as needed.

  • Client Approval Mechanism: Relies on client-side mechanisms for approving operations, ensuring a level of security as it does not autonomously approve write actions, preventing unintended filesystem modifications.


mcp-editor

This is a direct port of Anthropic's filesystem editing tools from their computer use demos to a TypeScript MCP server. It was written largely by Claude Sonnet 3.5 on Roo Cline (now Roo Code) with limited direct supervision. The code has been reviewed and the server is used daily, but there may still be mistakes or unexpected AI behavior.

It is recommended to use this server along with mcp-server-commands.

WARNING: This MCP server has NO access controls and relies entirely on your client's approval mechanisms. Use at your own risk. DO NOT automatically approve write operations, as this basically gives the LLM permission to destroy your computer.

WARNING: This MCP server is NOT actively maintained and is provided for reference (for example, for creating your own MCP server with proper access controls). Occasional updates may be made.

Usage

  1. Get the files on your computer.

  2. Run:

    npm install
    npm build
    
  3. If you're using the Claude desktop app, add the following to your config under "mcpServers", editing the path to match where you put mcp-editor:

    {
      "mcpServers":
      ... your existing servers ...
        "mcp-editor": {
          "command": "node",
          "args": ["/absolute/path/to/mcp-editor/dist/server.js"]
        }
      }
    }
    
  4. If you're using MCP Installer, provide your LLM with the path on your disk to mcp-editor.