Skip to main content
Glama
modelcontextprotocol

Filesystem MCP Server

Official

Edit File

edit_file
Destructive

Replace exact line sequences in a text file. Returns a git-style diff of changes. Only operates within allowed directories.

Instructions

Make line-based edits to a text file. Each edit replaces exact line sequences with new content. Returns a git-style diff showing the changes made. Only works within allowed directories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
editsYes
dryRunNoPreview changes using git-style diff format

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes

Implementation Reference

  • Registration of the 'edit_file' tool on the MCP server. Defines input schema (path, edits, dryRun) and passes handler to applyFileEdits.
    server.registerTool(
      "edit_file",
      {
        title: "Edit File",
        description:
          "Make line-based edits to a text file. Each edit replaces exact line sequences " +
          "with new content. Returns a git-style diff showing the changes made. " +
          "Only works within allowed directories.",
        inputSchema: {
          path: z.string(),
          edits: z.array(z.object({
            oldText: z.string().describe("Text to search for - must match exactly"),
            newText: z.string().describe("Text to replace with")
          })),
          dryRun: z.boolean().default(false).describe("Preview changes using git-style diff format")
        },
        outputSchema: { content: z.string() },
        annotations: { readOnlyHint: false, idempotentHint: false, destructiveHint: true }
      },
      async (args: z.infer<typeof EditFileArgsSchema>) => {
        const validPath = await validatePath(args.path);
        const result = await applyFileEdits(validPath, args.edits, args.dryRun);
        return {
          content: [{ type: "text" as const, text: result }],
          structuredContent: { content: result }
        };
      }
    );
  • Zod schema definition for EditOperation (oldText/newText) and EditFileArgsSchema (path, edits array, dryRun boolean).
    const EditOperation = z.object({
      oldText: z.string().describe('Text to search for - must match exactly'),
      newText: z.string().describe('Text to replace with')
    });
    
    const EditFileArgsSchema = z.object({
      path: z.string(),
      edits: z.array(EditOperation),
      dryRun: z.boolean().default(false).describe('Preview changes using git-style diff format')
    });
  • Handler function for edit_file tool. Validates path, then delegates to applyFileEdits, returning a git-style diff string.
    async (args: z.infer<typeof EditFileArgsSchema>) => {
      const validPath = await validatePath(args.path);
      const result = await applyFileEdits(validPath, args.edits, args.dryRun);
      return {
        content: [{ type: "text" as const, text: result }],
        structuredContent: { content: result }
      };
    }
  • Core implementation: applyFileEdits reads file, applies replacements (exact match then whitespace-flexible line matching), generates unified diff, and writes back atomically.
    export async function applyFileEdits(
      filePath: string,
      edits: FileEdit[],
      dryRun: boolean = false
    ): Promise<string> {
      // Read file content and normalize line endings
      const content = normalizeLineEndings(await fs.readFile(filePath, 'utf-8'));
    
      // Apply edits sequentially
      let modifiedContent = content;
      for (const edit of edits) {
        const normalizedOld = normalizeLineEndings(edit.oldText);
        const normalizedNew = normalizeLineEndings(edit.newText);
    
        // If exact match exists, use it
        if (modifiedContent.includes(normalizedOld)) {
          modifiedContent = modifiedContent.replace(normalizedOld, normalizedNew);
          continue;
        }
    
        // Otherwise, try line-by-line matching with flexibility for whitespace
        const oldLines = normalizedOld.split('\n');
        const contentLines = modifiedContent.split('\n');
        let matchFound = false;
    
        for (let i = 0; i <= contentLines.length - oldLines.length; i++) {
          const potentialMatch = contentLines.slice(i, i + oldLines.length);
    
          // Compare lines with normalized whitespace
          const isMatch = oldLines.every((oldLine, j) => {
            const contentLine = potentialMatch[j];
            return oldLine.trim() === contentLine.trim();
          });
    
          if (isMatch) {
            // Preserve original indentation of first line
            const originalIndent = contentLines[i].match(/^\s*/)?.[0] || '';
            const newLines = normalizedNew.split('\n').map((line, j) => {
              if (j === 0) return originalIndent + line.trimStart();
              // For subsequent lines, try to preserve relative indentation
              const oldIndent = oldLines[j]?.match(/^\s*/)?.[0] || '';
              const newIndent = line.match(/^\s*/)?.[0] || '';
              if (oldIndent && newIndent) {
                const relativeIndent = newIndent.length - oldIndent.length;
                return originalIndent + ' '.repeat(Math.max(0, relativeIndent)) + line.trimStart();
              }
              return line;
            });
    
            contentLines.splice(i, oldLines.length, ...newLines);
            modifiedContent = contentLines.join('\n');
            matchFound = true;
            break;
          }
        }
    
        if (!matchFound) {
          throw new Error(`Could not find exact match for edit:\n${edit.oldText}`);
        }
      }
    
      // Create unified diff
      const diff = createUnifiedDiff(content, modifiedContent, filePath);
    
      // Format diff with appropriate number of backticks
      let numBackticks = 3;
      while (diff.includes('`'.repeat(numBackticks))) {
        numBackticks++;
      }
      const formattedDiff = `${'`'.repeat(numBackticks)}diff\n${diff}${'`'.repeat(numBackticks)}\n\n`;
    
      if (!dryRun) {
        // Security: Use atomic rename to prevent race conditions where symlinks
        // could be created between validation and write. Rename operations
        // replace the target file atomically and don't follow symlinks.
        const tempPath = `${filePath}.${randomBytes(16).toString('hex')}.tmp`;
        try {
          await fs.writeFile(tempPath, modifiedContent, 'utf-8');
          await fs.rename(tempPath, filePath);
        } catch (error) {
          try {
            await fs.unlink(tempPath);
          } catch {}
          throw error;
        }
      }
    
      return formattedDiff;
    }
  • createUnifiedDiff helper that produces a git-style unified diff between original and modified file content using the 'diff' library.
    export function createUnifiedDiff(originalContent: string, newContent: string, filepath: string = 'file'): string {
      // Ensure consistent line endings for diff
      const normalizedOriginal = normalizeLineEndings(originalContent);
      const normalizedNew = normalizeLineEndings(newContent);
    
      return createTwoFilesPatch(
        filepath,
        filepath,
        normalizedOriginal,
        normalizedNew,
        'original',
        'modified'
      );
    }
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate destructive and non-readOnly. The description adds detail about line-based edits and a git-style diff output, which enhances transparency. It does not contradict annotations but could elaborate on error handling for unmatched oldText.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three concise sentences, front-loading the action and purpose. No redundant information; each sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given moderate complexity (3 params, 2 required) and no output schema, the description covers the main behavior, return value, and constraints. Missing details like partial failure handling or atomicity, but sufficient for typical use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is low (33%: only dryRun has description). The description clarifies that edits replace exact line sequences, adding meaning to oldText/newText beyond the schema. However, path remains unexplained, and dryRun description duplicates schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verbs ('Make line-based edits') and identifies the resource ('text file'), clearly distinguishing from sibling tools like write_file (whole file overwrite) or read_file. It also mentions the return format (git-style diff) and a constraint (allowed directories).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for precise line replacements (not appending or full rewrites) and mentions the directory constraint. However, it does not explicitly contrast with siblings like write_file or provide when-not-to-use scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/modelcontextprotocol/filesystem'

If you have feedback or need assistance with the MCP directory API, please join our Discord server