developer-tools Static interface comparison
Filesystem MCP
2.1.0 2.2.0
2 new write capabilities require explicit review.
View the upgrade review as Markdown
A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.
Article What Changed Between Filesystem MCP 2.1.0 and 2.2.0?
INTERFACE DIFF
What changed, tool by tool
- 2Added tools
- 0Removed tools
- 11Modified tools
- 3Input-schema changes
- 0Output-schema changes
- 2Declared authority changes
13 tools with recorded changes
append_fileAddedWhat changed
- New tool append_file, declared with write effect.
Why it could matter
- Agents connected to this release can be offered an operation that changes data, which the earlier release did not expose.
What to verify
- Review whether this operation should be exposed through your agent’s tool configuration.
- Declared effect
- — → write
Input schema
Property Previous (2.1.0) Current (2.2.0) Change (schema root)not present object - Added
contentnot present stringrequired - Added
pathnot present stringrequired - Added
Output schema
Property Previous (2.1.0) Current (2.2.0) Change (schema root)not present object, additionalProperties=false - Added
contentnot present stringrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
copy_fileAddedWhat changed
- New tool copy_file, declared with write effect.
Why it could matter
- Agents connected to this release can be offered an operation that changes data, which the earlier release did not expose.
What to verify
- Review whether this operation should be exposed through your agent’s tool configuration.
- Declared effect
- — → write
Input schema
Property Previous (2.1.0) Current (2.2.0) Change (schema root)not present object - Added
destinationnot present stringrequired - Added
sourcenot present stringrequired - Added
Output schema
Property Previous (2.1.0) Current (2.2.0) Change (schema root)not present object, additionalProperties=false - Added
contentnot present stringrequired - Added
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
directory_treeModifiedWhat changed
- directory_tree — Schema change: input property added: depth.
- directory_tree: description changed.
- directory_tree: declared metadata changed (declared idempotent: false → true).
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Models choose and call tools partly from their descriptions.
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Spot-check that agents still select this tool as intended.
- Confirm any client logic that relies on these annotations.
- Declared effect
- read → read
- Description
- PreviousGet a recursive tree view of files and directories as a JSON structure. Each entry includes 'name', 'type' (file/directory), and 'children' for directories. Files have no children array, while directories always have a children array (which may be empty). The output is formatted with 2-space indentation for readability. Only works within allowed directories.
- CurrentGet a recursive tree view of files and directories as a JSON structure. Each entry includes 'name', 'type' (file/directory), and 'children' for directories. Files have no children array, while directories always have a children array (which may be empty), except at the last level when 'depth' limits the tree: those directories are not read and have no children array. The output is formatted with 2-space indentation for readability. Only works within allowed directories.
Input schema
Property Previous (2.1.0) Current (2.2.0) Change depthnot present integer, exclusiveMinimum=0, maximum=9007199254740991optional - Added
4 unchanged entries
(schema root)excludePatternsexcludePatterns › [items]path
Output schema
Output schema unchanged.
2 unchanged entries
(schema root)content
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
edit_fileModifiedWhat changed
- edit_file: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- write → write
- Description
- PreviousMake 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.
- CurrentMake line-based edits to a text file. Edits apply in order, each to the result of the ones before it, and each replaces the first match of its oldText with newText. oldText must match the file's text exactly, except that line endings (LF or CRLF) never matter and, when there is no exact match, a run of whole lines matches if each line is equal once leading and trailing whitespace is ignored (newText then takes the file's indentation). Whitespace inside a line must match. If any edit has no match, nothing is written and the error shows the closest lines of the file, numbered, to copy oldText from. Returns a git-style diff showing the changes made. Only works within allowed directories.
Input schema
Input schema unchanged.
7 unchanged entries
(schema root)dryRuneditsedits › [items]edits › [items] › newTextedits › [items] › oldTextpath
Output schema
Output schema unchanged.
2 unchanged entries
(schema root)content
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
get_file_infoModifiedWhat changed
- get_file_info: declared metadata changed (declared idempotent: false → true).
Why it could matter
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Confirm any client logic that relies on these annotations.
- Declared effect
- read → read
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)path
Output schema
Output schema unchanged.
2 unchanged entries
(schema root)content
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
list_allowed_directoriesModifiedWhat changed
- list_allowed_directories: declared metadata changed (declared idempotent: false → true).
Why it could matter
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Confirm any client logic that relies on these annotations.
- Declared effect
- read → read
Input schema
Input schema unchanged.
1 unchanged entry
(schema root)
Output schema
Output schema unchanged.
2 unchanged entries
(schema root)content
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
list_directoryModifiedWhat changed
- list_directory: declared metadata changed (declared idempotent: false → true).
Why it could matter
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Confirm any client logic that relies on these annotations.
- Declared effect
- read → read
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)path
Output schema
Output schema unchanged.
2 unchanged entries
(schema root)content
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
list_directory_with_sizesModifiedWhat changed
- list_directory_with_sizes: declared metadata changed (declared idempotent: false → true).
Why it could matter
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Confirm any client logic that relies on these annotations.
- Declared effect
- read → read
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)pathsortBy
Output schema
Output schema unchanged.
2 unchanged entries
(schema root)content
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
read_fileModifiedWhat changed
- read_file — Input type change: property head changed: +maximum=9007199254740991, +minimum=0, type "number" → "integer".
- read_file — Input type change: property tail changed: +maximum=9007199254740991, +minimum=0, type "number" → "integer".
- read_file: declared metadata changed (declared idempotent: false → true).
Why it could matter
- Arguments of the old type may no longer validate against the new schema.
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Confirm any client logic that relies on these annotations.
- Declared effect
- read → read
Input schema
Property Previous (2.1.0) Current (2.2.0) Change headnumberoptional integer, maximum=9007199254740991, minimum=0optional - Constraint: maximum
- Constraint: minimum
- Type changed
maximum: — → 9007199254740991minimum: — → 0type: "number" → "integer"tailnumberoptional integer, maximum=9007199254740991, minimum=0optional - Constraint: maximum
- Constraint: minimum
- Type changed
maximum: — → 9007199254740991minimum: — → 0type: "number" → "integer"2 unchanged entries
(schema root)path
Output schema
Output schema unchanged.
2 unchanged entries
(schema root)content
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
read_media_fileModifiedWhat changed
- read_media_file: declared metadata changed (declared idempotent: false → true).
Why it could matter
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Confirm any client logic that relies on these annotations.
- Declared effect
- read → read
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)path
Output schema
Output schema unchanged.
3 unchanged entries
(schema root)contentcontent › [items]
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
read_multiple_filesModifiedWhat changed
- read_multiple_files: declared metadata changed (declared idempotent: false → true).
Why it could matter
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Confirm any client logic that relies on these annotations.
- Declared effect
- read → read
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)pathspaths › [items]
Output schema
Output schema unchanged.
2 unchanged entries
(schema root)content
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
read_text_fileModifiedWhat changed
- read_text_file — Input type change: property head changed: +maximum=9007199254740991, +minimum=0, type "number" → "integer".
- read_text_file — Input type change: property tail changed: +maximum=9007199254740991, +minimum=0, type "number" → "integer".
- read_text_file: declared metadata changed (declared idempotent: false → true).
Why it could matter
- Arguments of the old type may no longer validate against the new schema.
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Confirm any client logic that relies on these annotations.
- Declared effect
- read → read
Input schema
Property Previous (2.1.0) Current (2.2.0) Change headnumberoptional integer, maximum=9007199254740991, minimum=0optional - Constraint: maximum
- Constraint: minimum
- Type changed
maximum: — → 9007199254740991minimum: — → 0type: "number" → "integer"tailnumberoptional integer, maximum=9007199254740991, minimum=0optional - Constraint: maximum
- Constraint: minimum
- Type changed
maximum: — → 9007199254740991minimum: — → 0type: "number" → "integer"2 unchanged entries
(schema root)path
Output schema
Output schema unchanged.
2 unchanged entries
(schema root)content
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
search_filesModifiedWhat changed
- search_files: description changed.
- search_files: declared metadata changed (declared idempotent: false → true).
Why it could matter
- Models choose and call tools partly from their descriptions.
- Annotations such as idempotent or open-world hints can inform how clients treat a tool.
What to verify
- Spot-check that agents still select this tool as intended.
- Confirm any client logic that relies on these annotations.
- Declared effect
- read → read
- Description
- PreviousRecursively search for files and directories matching a pattern. The patterns should be glob-style patterns that match paths relative to the working directory. Use pattern like '*.ext' to match files in current directory, and '**/*.ext' to match files in all subdirectories. Returns full paths to all matching items. Great for finding files when you don't know their exact location. Only searches within allowed directories.
- CurrentFind files and directories by NAME, not by content: this tool never reads or searches inside files. It walks the tree under 'path' and matches a glob pattern against each entry's path relative to 'path' (case-sensitive). Use '*.ext' to match entries directly under 'path', and '**/*.ext' or '**/name' to match at any depth. Returns full paths to all matching items. Great for finding files when you don't know their exact location. Only searches within allowed directories.
Input schema
Input schema unchanged.
5 unchanged entries
(schema root)excludePatternsexcludePatterns › [items]pathpattern
Output schema
Output schema unchanged.
2 unchanged entries
(schema root)content
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
No tools match these filters.
3 tools with no recorded change
create_directorymove_filewrite_file
Evidence and provenance
- Static findings
- FAIL from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
- Human review
- Pending human review. No reviewer decision is recorded for this comparison.
- Published evidence
- Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
- Comparison
filesystem/2.1.0~2.2.0The published comparison identifier.- Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 5, 2026, 4:02 AM UTC.- Distribution
npm- Previous release
@modelcontextprotocol/server-filesystem@2.1.014 tools · published by the registry Oct 28, 2026, 9:08 PM UTCArtifact integritysha512-BMihuyTNi975iQTQDsZ6x+JVg99CAiX83jBV0wGMyc/0DcBO55ulCQqEzwx7lbG5U9/97XiPP9n0sK/iUtSsEg==Interface fingerprintsha256:bd1fd899684feb8595e94bf1ae3a3d71b5ea558d70923bd18338479c7a1959f8Exact interface snapshot (JSON)- Current release
@modelcontextprotocol/server-filesystem@2.2.016 tools · published by the registry Nov 4, 2026, 9:36 PM UTCArtifact integritysha512-mNLj/qhV+P4kj1qP8VzgQ2fjSmWcKDQ3Q+KpZEA+WahCDWHw5zJBRQUNSPZ6Ai2/ZGGUjzNzsFpz958a1+4T9A==Interface fingerprintsha256:28daa4cf473cea0b961f4339affca39603a55e75474254fae65e6ac2431c2020Exact interface snapshot (JSON)- Comparison record
- Exact comparison record (JSON)
The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.
MODELARA ANALYSIS OUTPUT
Interface findings
Policy failures
2 findingsappend_fileFAILAddedcopy_fileFAILAdded
Requires review
3 findingsdirectory_treeREVIEWChangedShow details
input property added: depth
read_fileREVIEWChangedShow details
input property head changed: +maximum=9007199254740991, +minimum=0, type "number" → "integer"input property tail changed: +maximum=9007199254740991, +minimum=0, type "number" → "integer"
read_text_fileREVIEWChangedShow details
input property head changed: +maximum=9007199254740991, +minimum=0, type "number" → "integer"input property tail changed: +maximum=9007199254740991, +minimum=0, type "number" → "integer"
Informational
13 findingsdirectory_treeINFOChangededit_fileINFOChangedsearch_filesINFOChangeddirectory_treeINFOChangedShow details
declared idempotent: false → true
get_file_infoINFOChangedShow details
declared idempotent: false → true
list_allowed_directoriesINFOChangedShow details
declared idempotent: false → true
list_directoryINFOChangedShow details
declared idempotent: false → true
list_directory_with_sizesINFOChangedShow details
declared idempotent: false → true
read_fileINFOChangedShow details
declared idempotent: false → true
read_media_fileINFOChangedShow details
declared idempotent: false → true
read_multiple_filesINFOChangedShow details
declared idempotent: false → true
read_text_fileINFOChangedShow details
declared idempotent: false → true
search_filesINFOChangedShow details
declared idempotent: false → true
What do these results mean?
- PASS
- No policy-significant interface change detected.
- REVIEW
- Interface changes require inspection.
- FAIL
- A policy-significant change was detected.
- INVALID
- The comparison could not be evaluated reliably.