Skip to main content
Glama
shrishailrana-maker

svn-agent MCP

by shrishailrana-maker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to svn-agent MCP

No user-submitted related servers found.

    Related Servers

    • SVN MCP Server

      gcorroto
      A
      license
      A
      quality
      C
      maintenance
      A complete Model Context Protocol server for Subversion (SVN) integration, designed to allow AI agents to efficiently manage SVN repositories.
      14
      22 npm
      21
      MIT

    • McpApp

      krok1029
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a local-first MCP server for AI-native software delivery, enabling structured specifications, human approval gates, controlled repository operations, verification evidence, review, and traceability.
      Apache 2.0

    • git-mcp-server

      saitolume
      A
      license
      A
      quality
      B
      maintenance
      A local MCP server that provides a safe, explicit set of Git operations for version control tasks like status, diff, branching, staging, committing, fetching, merging, and pushing.
      13
      18 npm
      MIT

    • Cross Repo Ops MCP

      DHCross
      F
      license
      B
      quality
      C
      maintenance
      Enables secure, policy-controlled operations on local git repositories through MCP, including bounded reads, context-checked patches, allowlisted tasks, and guarded git operations.
      10
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., svn_add vs svn_commit). However, svn_move and svn_rename are aliases for the same operation, causing redundancy. Additionally, eol_check and eol_fix_verified overlap in scope, but descriptions clarify their difference.

    Naming Consistency3/5

    The majority of tools follow a consistent svn_{verb} pattern. However, two EOL-related tools use an eol_ prefix instead of svn_eol_, and svn_self_check does not follow the verb pattern. This inconsistency may confuse an agent.

    Tool Count5/5

    23 tools is an appropriate number for a Subversion client agent. It covers a wide range of operations without being overwhelming or too sparse. Each tool seems necessary for distinct SVN tasks.

    Completeness3/5

    The tool set covers many core SVN operations, but notable gaps exist: svn_delete, svn_merge, svn_switch, and svn_blame are missing. For a comprehensive SVN workflow, these operations are important. The precommit check and EOL handling are nice additions, but the gaps reduce completeness.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources