🔒 Atomic Writer MCP Server: A secure file operation service that prevents data loss through atomic transactions. Built for AI integrations
Atomic Writer MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. 🔒 Atomic Writer MCP Server: A secure file operation service that prevents data loss through atomic transactions. Built for AI integrations, collaborative editing, and critical data management.
A secure and atomic file operation service implemented as an MCP (Model Context Protocol) server. This server provides safe, transactional file operations through the MCP protocol.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Once Atomic Writer is connected, these are the calls the assistant has available:
verify-integrity — Check file integrity and initialize tracking for external filesget-status — Get system statusrecover-file — Recover from journalget-file-history — View operation historyget-lock-status — Check file locksforce-release-lock — Release stuck locksrollback-operation — Rollback changesYou will need one environment variable: INVALID_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Atomic Writer's toolset — verify-integrity, get-status, recover-file and 4 more — is a fair guide to whether it matches your workflow. It is maintained by vanzan01; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Atomic Writer's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| verify-integrity | Check file integrity and initialize tracking for external files |
| get-status | Get system status |
| recover-file | Recover from journal |
| get-file-history | View operation history |
| get-lock-status | Check file locks |
| force-release-lock | Release stuck locks |
| rollback-operation | Rollback changes |
{
"mcpServers": {
"atomic-writer": {
"command": "node",
"args": [
"/absolute/path/to/atomic-writer/build/index.js",
"/absolute/path/to/base/directory"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| INVALID_PATH | Filesystem location the server is allowed to use. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.