Skip to main content
Glama
arbadacarbaYK

gittr-mcp

by arbadacarbaYK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to gittr-mcp

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.
      202 npm
      Apache 2.0

    • git-mcp-server

      jesspig
      A
      license
      A
      quality
      F
      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

    • Git MCP Server

      wty0512
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools for interacting with Git repositories, enabling AI assistants to manage repositories, branches, commits, and files through a standardized interface.
      4,277 npm
      1
      Apache 2.0
    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

    C2.7/5.0

    Scored across 75 tools

    Disambiguation2/5

    Multiple tools overlap heavily: createPR vs createPRViaGittrCLI, listReleases vs listForgeReleases vs fetchForgeReleases, publishSoftwareAnnounce vs announceSoftwareFromForgeRelease, and pushToBridge vs importRemoteToBridge vs mirrorRepo. Several aliases (deleteRepo/findReposByGithub) and multiple bounty flows add to the confusion. An agent must read long warnings to choose correctly.

    Naming Consistency4/5

    All tool names use lowerCamelCase consistently, so there is no casing chaos. However, the verb+noun pattern is not uniform: some tools are noun-first (bountyCreateWithdraw, bountyRelease), and verb choices vary widely (fetch, announce, explore, star, watch, merge, softDelete). Aliases and prefixed names (bridge*) are minor deviations.

    Tool Count2/5

    75 tools is far beyond the typical 3-15 range and includes many alias, low-level, and niche tools. While the platform is broad, the count forces agents to sift through redundant options and raises the risk of misselection. It should be consolidated.

    Completeness4/5

    Core lifecycle coverage is strong: repos (create/get/list/delete/fork), issues (create/list/get/close/reopen/comments), PRs (create/list/get/merge/comments), bounties, releases, paywall, and bridge operations are all present. Minor gaps exist (e.g., no updateIssue, no removeCollaborator, createRelease is a stub), but agents can work around them.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources