Skip to main content
Glama
JoeGlenn1213

lgh

by JoeGlenn1213
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

Related Servers

Alternatives to lgh

No user-submitted related servers found.

    Related Servers

    • Git MCP Server

      a-g-e-n-t-s
      A
      license
      Not graded
      quality
      D
      maintenance
      A secure and scalable Git MCP server giving AI agents powerful version control for local and (soon) serverless environments.
      148 npm
      Apache 2.0

    • git-mcp-server

      jesspig
      A
      license
      A
      quality
      B
      maintenance
      Local Git MCP server exposing 29 tools that let AI clients manage repositories, commits, branches, remotes, and advanced git operations via natural language.
      29
      MIT

    • my-local-mcp

      az-ka
      F
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that turns AI clients into power users of local git repositories, enabling clone, browse, search, and inspect code without burning API tokens.
      -

    • GitPilot MCP

      DarkRyan721
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      A lightweight MCP server that enables AI assistants to manage local Git repositories by executing commands like status, add, and commit. It streamlines development workflows by providing repository context and diffs directly to the assistant.
      Apache 2.0

    • github-mcp

      iiinigence
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with GitHub via a fine-grained personal access token — pushing commits, managing branches, opening and merging PRs, creating issues, and reading repositories. It runs locally with no telemetry and supports a read-only mode.
      15
      1
      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

    A4.3/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target distinct actions and descriptions explicitly cross-reference siblings (e.g. lgh_save vs lgh_up, lgh_diff vs lgh_up_dryrun, lgh_status vs lgh_log), so selection is clear. Minor overlap remains: lgh_up auto-registers, duplicating lgh_add, and lgh_up vs lgh_save differ only in whether a push happens.

    Naming Consistency4/5

    Every tool shares the lgh_ prefix and uses snake_case, giving a predictable scheme. A few break the verb-first pattern (lgh_serve_start/lgh_serve_stop place the object first, lgh_up_dryrun appends a modifier), a small deviation but still readable.

    Tool Count5/5

    13 tools is well-scoped for a git backup/server-management server. Each tool maps to a distinct lifecycle step (server control, registration, checkpoint/backup, inspection, recovery) and none feels redundant.

    Completeness4/5

    The surface covers the full loop: server start/stop/status, add/remove/list/clone, save/up/up_dryrun, diff, rollback, and log inspection. Minor gaps exist around pulling/fetching into an existing tree and branch/tag management, but core backup and restore workflows are covered.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources