Skip to main content
Glama
csawantgit

commvault-release-comparison-mcp

by csawantgit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to commvault-release-comparison-mcp

No user-submitted related servers found.

    Related Servers

    • release-intel

      barissozudogru
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that generates release intelligence from GitHub repository data, correlating commits, pull requests, issues, and contributors between two git refs to produce structured context for release notes, changelogs, and summaries.
      3
      54 npm
      3
      MIT

    • dealhub-admin

      vishvick
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for DealHub administrators to manage versions (list, get, activate, duplicate) through natural language commands via Claude and other AI agents.
      107 npm
      MIT

    • changeOracle

      ToolOracle
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables DORA Article 8 change management through MCP tools for registering and tracking changes, assessing risk, validating approvals, rollback plans, and test evidence, checking patch compliance and segregation of duties, and viewing change statistics and server health.
      -
    • heddle by foundryside-dev

      heddleofficial

      foundryside-dev
      A
      license
      C
      quality
      A
      maintenance
      Temporal change-impact authority MCP server that tracks per-entity change history across runs and answers downstream propagation queries, enabling impact analysis and reverification worklists.
      12
      MIT
    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

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: comparing two releases, retrieving all changes for a release, retrieving changes by category, and generating a summary. There is no overlap in their functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case: compare_releases, get_release_changes, get_category_changes, generate_summary. This makes the set predictable and easy to navigate.

    Tool Count5/5

    With only 4 tools, the server is well-scoped for its purpose of release comparison and summarization. Each tool serves a distinct need without redundancy or bloat.

    Completeness4/5

    The tool set covers the core comparison workflow: comparing releases, fetching changes, filtering by category, and generating summaries. A tool to list available releases would make the set more self-contained, but the current coverage is sufficient for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources