Skip to main content
Glama
gcorroto

SVN MCP Server

by gcorroto

Related Servers

Alternatives to SVN MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol server implementation that enables AI assistants to interact with file systems, databases, GitHub repositories, web resources, and system tools while maintaining security and control.
      46 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol server that enhances AI agents by providing deep semantic understanding of codebases, enabling more intelligent interactions through advanced code search and contextual awareness.
      90
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that provides Git version control operations as structured tools for AI coding agents. It enables LLMs to programmatically manage repositories through actions like committing changes, rolling back code, and comparing diffs.
      10
      Apache 2.0
    • A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server for Git repository interaction and automation. This server provides tools to read, search, and manipulate Git repositories via Large Language Models.
      12
      39,753 PyPI
      90,629
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A robust, lightweight Model Context Protocol (MCP) server designed to empower your AI Agents with context-awareness, safe execution sandboxes, and dedicated thought logs.
      -

    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