svn_add
Añadir archivos al control de versiones
LABSCO SUMMARY
Everyday Subversion work handed to an agent, with a health check that fails at launch instead of mid-task.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command plus credentials — npm install -g @grec0/mcp-svn, then supply credentials
USE CASES
01
Getting oriented in a checkout you just inherited
svn_info gives the repository URL and current revision, then svn_status lists what is modified, added or unversioned — pass showAll to bring the remote state in too.
02
Reading the history behind a file
svn_log returns the commits for a path with a revision range and a limit, and svn_diff shows exactly what changed between two of them.
03
Landing a change without leaving the conversation
svn_add stages the new files, creating parent directories when the folder is new as well, and svn_commit sends them with a message.
04
Starting from a repository URL
svn_checkout pulls a working copy at the revision and depth you name, and svn_update brings it forward with a conflict-acceptance policy of your choice.
05
Getting a stuck working copy moving again
svn_cleanup releases locks left by an interrupted operation, svn_clear_credentials clears the credential cache after an authentication error, and svn_health_check confirms the client is there at all.
14 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
svn_checkout
Hacer checkout de un repositorio SVN
svn_cleanup
Limpiar working copy de operaciones interrumpidas
svn_clear_credentials
Limpiar cache de credenciales SVN para resolver errores de autenticación
svn_commit
Confirmar cambios al repositorio
svn_delete
Eliminar archivos del control de versiones
svn_diagnose
Diagnosticar problemas específicos con comandos SVN
svn_diff
Ver diferencias entre versiones de archivos
svn_health_check
Verificar el estado de salud del sistema SVN y working copy
svn_info
Obtener información detallada del working copy o archivo específico
svn_log
Ver historial de commits del repositorio
svn_revert
Revertir cambios locales en archivos
svn_status
Ver el estado de archivos en el working copy
svn_update
Actualizar working copy desde el repositorio
BEFORE YOU INSTALL
What to know first
Tools you get
14 tools when we connected. svn_diagnose and svn_clear_credentials are missing from the documented list; svn_cat and svn_list, named in the configuration section, do not exist. Branch management, merge, switch, blame and batch operations are still in development.
Requires
- npx on PATH
- Node.js >= 18.0.0
- SVN_USERNAME in your environment
- SVN_PASSWORD in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 14 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"svn": {
"command": "npx",
"args": [
"@grec0/mcp-svn"
],
"env": {
"SVN_PATH": "svn",
"SVN_WORKING_DIRECTORY": "<YOUR_SVN_WORKING_DIRECTORY>",
"SVN_URL": "<YOUR_SVN_URL>/repo",
"SVN_USERNAME": "<YOUR_SVN_USERNAME>",
"SVN_PASSWORD": "<YOUR_SVN_PASSWORD>"
}
}
}
}npm
TERMINAL
npm install -g @grec0/mcp-svn
