github-stars-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | A GitHub personal access token. Fine-grained tokens need no special scopes for public stars; classic tokens need read:user. | |
| GITHUB_STARS_DB | No | Override path for the SQLite cache database. | |
| GITHUB_STARS_HOME | No | Override directory for the optional .env file. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_starsA | Search your GitHub starred repos by keyword (matches name, description, and topics). Optionally filter by language. |
| list_starsB | List your GitHub starred repos, with optional language filter and sorting. |
| get_starA | Get full details for one starred repo by its full name (owner/repo). |
| refresh_starsA | Force a full re-fetch of your starred repos from the GitHub API and update the local database. Read tools already check for updates automatically on use. |
| stars_statusA | Show when the local stars database was last checked and last synced. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
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.
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.