Skip to main content
Glama
ENFernandes

github-stars-mcp

by ENFernandes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to github-stars-mcp

No user-submitted related servers found.

    Related Servers

    • github-mcp-server

      ArnabbLank
      A
      license
      B
      quality
      C
      maintenance
      A minimal MCP server for GitHub that enables browsing repos, reading code, searching, and getting insights through natural language via Claude, Cursor, or any MCP client.
      7
      MIT

    • github-mcp

      AbdeeBuilds
      A
      license
      A
      quality
      C
      maintenance
      GitHub MCP server for Claude Code, Cursor, Cline, Windsurf, and any MCP-compatible client. Exposes GitHub tools (issues, pull requests, code search, file content) to your LLM via the Model Context Protocol.
      7
      MIT

    • gitcontribute

      morluto
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that helps coding agents research and prepare GitHub contributions by gathering repository guidance, related work, code context, and validation evidence into a local SQLite corpus, without ever writing to GitHub.
      384 npm
      3
      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

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search, list, get single, refresh, and status. While search and list both return starred repos, search focuses on keyword matching while list is for general listing with sorting, so no ambiguity.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (search_stars, list_stars, refresh_stars), but get_star uses singular while others use plural, and stars_status is a noun phrase rather than verb_noun. These are minor deviations from an otherwise consistent convention.

    Tool Count5/5

    Five tools is well-scoped for the server's purpose of managing GitHub starred repos. Each tool serves a distinct function without redundancy, and the count is neither too thin nor excessive for this niche domain.

    Completeness5/5

    The tool set covers the full lifecycle for reading and syncing starred repos: search, list, get details, refresh, and status. There are no obvious gaps in the stated purpose, and the automatic update check covers the freshness concern.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources