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.
      177 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.
      3,597 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.6/5.0

    Scored across 75 tools

    Disambiguation2/5

    Several tool boundaries are unclear: createPR and createPRViaGittrCLI both create PRs, getFile overlaps with bridgeGetFileContent, and closeIssue/reopenIssue/markPullRequestMerged are wrappers around publishStatusForRoot. There are also explicit aliases (findReposByGithub/findReposBySource, deleteRepo/softDeleteRepo) that further blur the surface.

    Naming Consistency4/5

    The vast majority use a readable camelCase verb_noun pattern (listIssues, createRepo, publishRepoAnnouncement). Minor deviations like myRepos, bridgeRepoExists, createRelease (which doesn't actually create), and createPRViaGittrCLI prevent a perfect score.

    Tool Count1/5

    75 tools is an extreme surface for a single MCP server, far past the 25+ threshold. Even granting the broad gittr/Nostr domain, the count will make tool selection and model context unwieldy.

    Completeness4/5

    The surface covers repo lifecycle, issues/PRs, comments, bounties, releases, social actions, auth, and security audits, so core workflows have no dead ends. Minor gaps exist, such as no repo metadata update/remove-collaborator tool and release tooling split awkwardly across listReleases/listForgeReleases/createRelease.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources