gh-autostar
Related Servers
Alternatives to gh-autostar
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server + CLI that makes AI coding agents search GitHub for existing open-source solutions before implementing a feature, scoring each repo 0-100 with an adopt / adapt / inspect / avoid verdict.35 npm6MIT
- AlicenseBqualityCmaintenanceA powerful MCP server that helps you discover relevant repositories from your own starred list on GitHub using BM25 keyword ranking and Gemini Semantic Search.219MIT
- AlicenseAqualityDmaintenanceAn MCP server that caches your GitHub starred repositories in a local SQLite database and lets you search, list, and retrieve details about them through any MCP client (Claude Desktop, Cursor, VS Code, etc.), with automatic freshness checks via GitHub's ETag mechanism.51MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables AI clients to autonomously discover, analyze, fix, test, submit, and track open-source contributions on GitHub through specialized tools.12ISC
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to directly manage GitHub repositories, including PRs, issues, and code search, using natural language.MIT
- AlicenseAqualityDmaintenanceMCP server that provides AI coding agents automatic access to AGENTS.md documentation from GitHub repositories, enabling understanding of codebase conventions and patterns.2Apache 2.0
TDQS
Scored across 6 tools
Each tool maps to a distinct action: starring (ensure_starred), verifying (check_star), removing (unstar), configuring (configure_autostar), and two read-only views. The only mild overlap is between star_status (global config/state) and list_recent_stars (history log), but the descriptions make the boundary clear enough.
Most names follow verb_noun (check_star, list_recent_stars, configure_autostar), but ensure_starred uses a past-participle form, unstar is a bare verb, and star_status leads with a noun. The conventions are mixed yet still readable and predictable enough to infer intent.
Six tools cover the full lifecycle of a narrow, well-defined domain without redundancy. Each tool earns its place: act, verify, undo, inspect state, audit, and configure.
Star/unstar/check plus status, audit history, and configuration covers the core lifecycle with no dead ends. Minor gaps exist—no batch operations and no dedicated query for current whitelist/blacklist contents beyond what star_status exposes.