Skip to main content
Glama
Anselmoo

mcp-repo-release-tools

by Anselmoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-repo-release-tools

No user-submitted related servers found.

    Related Servers

    • mcp-creator

      gmoneyn
      A
      license
      A
      quality
      B
      maintenance
      A tool that enables AI assistants to conversationally scaffold, build, and publish Python MCP servers to PyPI. It automates the entire development lifecycle, including package naming, tool scaffolding, GitHub repository setup, and package publishing.
      10
      MIT

    • devflow-mcp

      boranesn
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server that provides AI assistants with comprehensive GitHub developer tooling including PR analysis, code review, changelog generation, dependency auditing, commit summarization, and refactoring suggestions.
      8 npm
      ISC

    • mcp-easy-installer

      onigetoc
      F
      license
      A
      quality
      C
      maintenance
      A robust MCP server with tools to search, install, configure, repair, and uninstall MCP servers, automating setup and maintenance across multiple AI and developer tools.
      4
      17
      -

    • gitea-mcp

      werebear73
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to read, create, and manage issues, repositories, and releases on Gitea, Forgejo, or Codeberg instances via personal access tokens.
      21
      132 PyPI
      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

    A3.9/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most rrt_* tools target distinct resources (branch, config, health, drift, tree, artifacts, version, changelog), and descriptions clarify read-only vs. check vs. action. The main ambiguities are rrt_init vs. rrt_init_run and the dashboard/overview tools that parallel their data counterparts, though the descriptions explicitly steer agents away from the UI variants.

    Naming Consistency3/5

    There is a consistent rrt_ prefix and snake_case style, but the verb/noun pattern is mixed: some tools are noun-only (rrt_health, rrt_tree, rrt_changelog), some are verb_noun (rrt_validate_branch, rrt_release_check), and rrt_doctor is a noun used as a verb. The two prefab tools (generate_prefab_ui, search_prefab_components) break the rrt_ prefix entirely, making the set feel like two naming systems.

    Tool Count2/5

    At 27 tools, the server exceeds the 25-tool threshold and feels heavy for its purpose. The core release-check/bump/version functionality is reasonably scoped, but the five dashboards, two init tools, and two prefab UI tools inflate the surface and could be split out or removed.

    Completeness4/5

    The release lifecycle is well covered: branch validation, version reading, bumping, commit validation, changelog reading, release checks, sync checks, folder/docs checks, and publish-snapshot all exist. Minor gaps remain, such as no MCP tool for the live tree check, no direct changelog write, and no docs-map check, but these are explicitly noted as CLI-only rather than silent dead ends.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources