Change the file. Check the result.
A new CSV is ready. The site still uses the old one. MCP Abilities – Filesystem lets an authenticated AI client inspect the file, save the intended content and read it back—through eleven WordPress file and directory actions.
Replace the list or add to it?
Imagine a training provider updating a CSV of course dates. A complete replacement belongs in a write operation. A few extra rows belong in an append operation. Appending the complete list would duplicate the existing entries.
Inspect the current headings, row format and file size first. The add-on checks the resulting content, but it cannot decide whether the dates or columns suit your importer. Keep the default backup and compare the saved file with the approved data.
Replacement changes the whole file. Appending keeps its existing content and adds more.
Moving a file does not move its references
Copy keeps the original file. Move changes its location. Neither action rewrites a page link, importer setting or plugin configuration that points to the old path.
If a course importer reads a fixed filename, confirm that setting before moving its CSV. For WordPress images, use the Media Library tools when attachment records and responsive image sizes need to stay consistent.
The file can reach its new location while a page or importer still points to the old one.
Choose the action the job needs
The add-on works with physical files inside the WordPress root. WordPress page content and Media Library records have their own editing tools.
Inspect first
List a directory, inspect file information or read permitted content. Reads default to 256 KB and can return at most 1 MB. Directory listings report when their item limit truncates the result.
Write or organise
Create a directory, write a file, append or prepend content, or copy and move a permitted file. Copying or moving over an existing destination requires an explicit overwrite choice.
Remove with care
File deletion keeps a backup by default, unless the caller disables it. Directory deletion has no backup; recursive deletion must be requested explicitly. Check what uses the path before removing it.
Review the change
The operations log records successful writes, appends, copies, moves and deletions. Read it to find the affected path and available backup details, then inspect the file and the process that uses it.
Know what the checks cover
Every action requires an authenticated WordPress account with manage_options. Paths stay within the resolved WordPress root. Reads, copies and moves reject selected configuration and key-file paths. Writes reject PHP-like files, protected core destinations and detected unsafe content. Complete written content is limited to 10 MB.
Required backup failure stops the file change. Some actions let the caller disable backups, and backup folders older than seven days can be cleaned up. Backup and log files may contain sensitive data; their web access depends on hosting rules. Keep a separate site backup. A passed file check does not prove that the content is correct for your site.
Connect the WordPress file tools
Use WordPress 6.9 or later, which includes the Abilities API, and PHP 8.0 or later. Configure the WordPress MCP Adapter and MCP Expose Abilities to make the actions available to your authenticated client.
The server must allow the requested filesystem operation. WordPress can disable file changes through DISALLOW_FILE_MODS. Start with a read-only inspection and check the discovered input fields before making a change.
Start with the file you need to understand
Install the add-on, inspect the intended path and use what you find to define one clear change. Then read back the saved result.