Claude File Manager MCP

Overview Schema Source Related Servers Discussions Admin

Create or overwrite a file

write_file

Writes text content to a file, creates missing parent folders, and can overwrite existing files while keeping a backup for undo.

Instructions

Writes text to a file. Creates missing parent folders. By default overwrites an existing file and keeps a backup (restorable via undo_last_change).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>",
      "content": "<content>"
    },
    "name": "write_file"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	File path
`content`	Yes	Text content of the file
`overwrite`	No	false — do not overwrite if the file already exists
`create_parents`	No	Create missing parent folders

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Nov 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses that overwrites happen by default, that a backup is retained and restorable via undo_last_change, and that missing parent folders are created. It omits failure behavior (e.g., error when overwrite=false) and encoding or permission requirements, which keeps it short of a 5.

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?

Three short sentences, zero filler, with the core action and the backup/undo safety fact front-loaded before the defaults.

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?

For a four-parameter write tool with no output schema and no annotations, the description covers the mutation semantics and recoverability well. The main gap is that it does not indicate what the call returns (e.g., the written path or backup reference), which an agent would need to chain into a follow-up call.

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 100%, so both optional flags (overwrite, create_parents) are already documented and the baseline is 3. The description reinforces the default overwrite and parent-folder creation and adds the non-schema fact that a backup is kept, but supplies no extra syntax or format detail beyond the schema.

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

Purpose4/5

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

States a specific verb and resource ('Writes text to a file') and adds concrete scope details (creates parent folders, overwrites by default). It does not name siblings such as append_file or edit_file, but the word 'overwrites' implicitly distinguishes it from an append operation.

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

Usage Guidelines3/5

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

Usage is implied through the default-overwrite behavior and the pointer to undo_last_change for recovery, so an agent can infer that this is a destructive write. However, it never says when to prefer append_file, edit_file, or multi_edit over this tool, and never states what happens when overwrite=false and the file exists.

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