Reading a working copy and changing it both go through this one server, so an agent can look at the status, read the log behind a file and land the commit in the same conversation. Branching, merge and switch, and blame are listed as still in development, and the tool descriptions the model reads are written in Spanish.
A Node server that wraps the svn command-line client and exposes the everyday Subversion operations as tools: checkout and update, info, status, log and diff, add, commit, delete and revert, plus cleanup for a working copy left locked.
- The working copy laid out: svn_info for repository details on a path, svn_status for what changed, with remote state included when you ask for it
- History and differences: svn_log for the commit history of a path or revision range, svn_diff between two revisions of a file
- svn_checkout with a revision and a depth of empty, files, immediates or infinity, and svn_update with the conflict-acceptance policy you choose
- The write side too — svn_add stages files and can create parent directories, svn_commit sends a message, svn_delete and svn_revert undo
- svn_cleanup clears a working copy stuck after an interrupted operation
- svn_health_check and svn_diagnose confirm svn is reachable and the working copy is valid before anything else runs
- svn_clear_credentials drops the cached SVN credentials when authentication starts failing
Published as @grec0/mcp-svn and launched over stdio with npx. Node.js 18.0.0 or newer and a Subversion client on PATH — the server shells out to it. SVN_WORKING_DIRECTORY points at a checkout, SVN_URL at a repository, and either or both can be set; SVN_USERNAME and SVN_PASSWORD carry authentication, SVN_PATH names the executable, and SVN_TIMEOUT caps a long operation at 30000 milliseconds by default.
One command plus a key — npm install -g @grec0/mcp-svn, then supply credentials