MCP servers that can write a file
5 verified servers expose a tool that can write a file's contents
Reading a file is half of it; writing one is the other half. When an agent produces a config, a script, or a document and needs it to persist, a write-file tool creates or updates the file at a path, on a code host or a storage service.
These verified servers let an agent write a file's contents.
GitHub
GitHub
GitHub's official remote MCP server for repos, issues, pull requests, Actions, and code search.
create_or_update_file
create_or_update_file creates a new file or updates an existing one in a GitHub repository as a commit, the way a coding agent lands a change without cloning.
Gitea
Gitea
Gitea's official MCP server for repos, branches, issues, pull request reviews, releases, Actions, and wikis on any Gitea instance.
create_file
create_file commits a new file to a self-hosted Gitea repository, the same write on a forge you run in-house.
Nextcloud
Chris Coutinho
Production-ready community MCP server for Nextcloud: files, notes, calendar, contacts, tables, deck, talk, and more across 110+ tools.
nc_webdav_write_file
nc_webdav_write_file writes a file over WebDAV, for content that belongs in Nextcloud storage rather than a repo.
Google Drive (Workspace MCP)
taylorwilsdon
The Google Workspace MCP, scoped to Drive, lets an agent search, read, create, and share your Google Drive files over OAuth.
create_drive_file
create_drive_file creates a file in Google Drive, optionally pulling its content from a source, for documents that live in Drive.
Dropbox
Dropbox
Dropbox's hosted MCP server lets agents search, read, organize, and share files in your Dropbox over OAuth.
CreateFile
CreateFile writes a new text file from inline content in Dropbox, the fit when an agent's output belongs in a shared Dropbox folder.
What to know
Where the file goes decides the tool and the semantics. A code-host write creates or updates a file in a repository as a commit, which is how a coding agent lands a change without a full local clone. A storage write puts bytes at a path in a drive or a WebDAV share. The code hosts care about the commit, a message and a branch; the storage services care about the path and the content. Match the server to whether the file is code under version control or a document in a folder.
Writing is the consequential half, so it wants the same care as any change: write to a branch, not straight to main, where the host supports it. And what the agent wrote, and where, is worth recording, so a later session can find or revise the file instead of creating a second copy of it.
Questions
- Does writing to a repo make a commit?
- Yes. GitHub's create_or_update_file and Gitea's create_file land the change as a commit with a message on a branch you choose, so it goes through version control like any edit. The storage writes (Drive, Dropbox, WebDAV) just place the file at a path, with no commit history.
- Should an agent write straight to main?
- Prefer a branch where the host supports it. Writing to a feature branch and opening a PR keeps a human or a check in front of the change, which matters more once an agent can commit files on its own. Reserve direct writes for low-stakes paths.