Skip to main content
Glama

Related Servers

Alternatives to UVCS MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to safely read, search, understand, and edit local project code and files, with Git inspection, code indexing, and controlled command execution within permissioned workspaces.
      1 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables remote AI agents to read, patch, and (opt-in) execute commands in a local workspace, with all actions approved locally and fully audited.
      6,910 npm
      2
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to access version control data and perform safe, structured read/write operations across files, changelists, shelves, workspaces, jobs, reviews, streams, and server metadata, with optional P4 DAM asset management. It supports configurable toolsets, read-only mode by default, and interactive confirmation for destructive actions.
      -
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI clients to inspect and carefully edit a bounded local workspace via stdio, with a read-only default, conflict-safe updates, and no network listener or telemetry.
      10
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to execute safe read-only shell commands immediately and to request one-time human approval before potentially destructive shell or file operations run. It integrates with clients such as Cursor, Claude Code, Copilot CLI, and Codex.
      MIT

    TDQS

    B3.2/5.0

    Scored across 45 tools

    Disambiguation3/5

    Mutating operations are split into prepare/confirm pairs with descriptions that clarify the workflow, but the large surface creates some overlap among status/diagnostic tools such as doctor, policy_status, setup_status, workspace_status, and branch_info. Read-only previews and diffs are mostly distinct, but several tools require careful reading to choose correctly.

    Naming Consistency4/5

    All tools use the uvcs_ prefix and snake_case, with a predictable _prepare/_confirm suffix for mutating operation pairs. A few read-only tools use noun-style names rather than strict verb_noun, but the pattern is still mostly consistent and readable.

    Tool Count2/5

    45 tools is well above the 25+ threshold for a heavy surface, even accounting for the many prepare/confirm pairs. The set is comprehensive, but the sheer number of tools increases selection cost and makes the server feel over-scoped.

    Completeness3/5

    Core version-control workflows are covered: status, pending changes, branch/label creation and listing, checkout, checkin, merge, update, diff, history, annotate, and workspace switching. However, notable lifecycle gaps remain, including branch/label deletion or modification, shelve/unshelve, rollback/revert changeset, and in-client conflict resolution is explicitly out of scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues