Skip to main content
Glama
gcorroto

SVN MCP Server

by gcorroto

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
svn_health_checkB

Verificar el estado de salud del sistema SVN y working copy

svn_diagnoseC

Diagnosticar problemas específicos con comandos SVN

svn_infoC

Obtener información detallada del working copy o archivo específico

svn_statusC

Ver el estado de archivos en el working copy

svn_logC

Ver historial de commits del repositorio

svn_diffC

Ver diferencias entre versiones de archivos

svn_checkoutC

Hacer checkout de un repositorio SVN

svn_updateC

Actualizar working copy desde el repositorio

svn_addC

Añadir archivos al control de versiones

svn_commitC

Confirmar cambios al repositorio

svn_deleteC

Eliminar archivos del control de versiones

svn_revertC

Revertir cambios locales en archivos

svn_cleanupC

Limpiar working copy de operaciones interrumpidas

svn_clear_credentialsB

Limpiar cache de credenciales SVN para resolver errores de autenticación

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 14 tools

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity. Each targets a specific SVN operation (e.g., checkout, commit, diff, log) with clear boundaries between them. The descriptions reinforce distinct functions, making misselection unlikely.

Naming Consistency5/5

All tools follow a consistent 'svn_verb' or 'svn_noun_verb' pattern (e.g., svn_checkout, svn_commit, svn_health_check). The naming is uniform throughout, using snake_case and starting with 'svn_' as a prefix, making it predictable and readable.

Tool Count5/5

With 14 tools, the count is well-scoped for an SVN server, covering core operations like version control, file management, diagnostics, and history. Each tool earns its place without feeling excessive or insufficient for the domain.

Completeness5/5

The tool set provides complete coverage of essential SVN workflows, including CRUD operations (add, delete, commit, revert), repository interactions (checkout, update), diagnostics (health_check, diagnose), and history/logging. No obvious gaps exist for typical agent tasks.

Maintenance

ActivityStale
ResponsivenessNo issues