[factspark23-hash]

What

Add a new compare_files tool that compares two files and returns a unified diff.

Why

Currently there is no way to compare two files through MCP. Users often need to:

• Verify an edit was applied correctly
• Understand differences between file versions
• Review changes before committing

Without this tool, agents must read both files entirely and manually diff them, which is inefficient and error-prone.

How

compare_files({
  file1: "path/to/original.ts",
  file2: "path/to/modified.ts",
  contextLines: 3  // optional, default 3
})

Returns unified diff output, or reports files as identical.

Changes

• src/filesystem/index.ts:
  • Added CompareFilesArgsSchema with file1, file2, contextLines params
  • Registered compare_files tool using existing createUnifiedDiff from lib.ts
  • Both files must be within allowed directories

[LuuOW]

Technical audit: Verified MCP server implementation for consistency with current SDK patterns.

[cliffhall]

Thank you for this pull request, and apologies for the long wait for a response.

These servers are reference implementations: they exist to show how each part of MCP is used, not to be general-purpose products, so new features are taken selectively, and this change isn't one the maintainers plan to take. This repository also now accepts issues, not pull requests, from anyone but its maintainers; the policy is in CONTRIBUTING.md.

This is not a judgment on the idea or on you. A server in the MCP Registry may well offer it, and anyone is welcome to build on these servers to do so. If you think we've misread it, please open an issue describing the problem and the expected behavior.

This is part of the backlog triage in #4875.