Skip to main content
Glama
seayniclabs

Mooring

Official
by seayniclabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Mooring

No user-submitted related servers found.

    Related Servers

    • Gitrama MCP Server by GitramaLLC

      Gitrama MCP Serverofficial

      GitramaLLC
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides 15 MCP tools for AI-powered Git intelligence, enabling commit messages, branch creation, PR descriptions, code review, diff analysis, and push operations directly from your AI assistant.
      MIT

    • Git MCP Server

      DanyelKirsch
      A
      license
      B
      quality
      D
      maintenance
      Provides comprehensive Git functionality to MCP clients, enabling users to manage repositories through operations like commits, diffs, and branch management via natural language. It automatically detects the current working directory and supports multi-project workflows across different local environments.
      16
      142 npm
      2
      MIT

    • GitLab Review MCP

      lininn
      A
      license
      B
      quality
      C
      maintenance
      Enables code review operations on GitHub and GitLab, including fetching pull/merge requests, viewing diffs, adding comments, analyzing code quality, and creating merge requests directly from your MCP client.
      15
      8 npm
      4
      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

    B3.4/5.0

    Scored across 12 tools

    Disambiguation4/5

    Clear separation between GitHub API (gh_*) and local git (repo_*) operations. While gh_issues combines list/create/update into one tool whereas PR operations are split into separate tools, the descriptions clearly distinguish their purposes with no overlapping functionality between different tools.

    Naming Consistency3/5

    Uses consistent prefixes (gh_ and repo_) but mixes naming patterns: gh_issues and gh_actions use nouns while PR tools use verb_noun (gh_pr_create, gh_pr_list). Local git tools follow git command names (mostly nouns) but lack verb consistency with the GitHub action-oriented names.

    Tool Count5/5

    Twelve tools is well-scoped for a server bridging GitHub API and local git operations. The count covers essential inspection and management tasks without bloat, with each tool earning its place in the set.

    Completeness3/5

    Strong read-only coverage (status, log, diff, blame, list operations) but notable gaps in write operations: no PR update/merge/close, no local git commit/push/pull/checkout, and limited Actions support (list only). The surface supports inspection workflows well but leaves agents unable to complete full git/PR lifecycle operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources