gittr-mcp
Related Servers
Alternatives to gittr-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA secure and scalable Git MCP server giving AI agents powerful version control for local and (soon) serverless environments.Apache 2.0
- AlicenseBqualityDmaintenanceAn MCP server to provide AI agents money functionalities via Nostr and Cashu.666 npm17MIT
- AlicenseNot gradedqualityCmaintenancePublishes an MCP server that exposes a self-hosted, GitHub-compatible git forge so agents can drive repositories, the REST v3 and GraphQL v4 APIs, and git smart HTTP operations through tool calls. It runs inside a single dependency-free Node.js process, letting clients clone, inspect, and manipulate hosted repos conversationally.MIT
- AlicenseAqualityFmaintenanceLocal Git MCP server exposing 29 tools that let AI clients manage repositories, commits, branches, remotes, and advanced git operations via natural language.29MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that equips AI agents with dev workflow tools including GitHub project management, conventional commits, visual regression testing, Jira/Confluence integration, and a persistent memory knowledge graph.14 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools for interacting with Git repositories, enabling AI assistants to manage repositories, branches, commits, and files through a standardized interface.1Apache 2.0
TDQS
Scored across 75 tools
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.
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.
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.
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.