StarSeeker MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub Personal Access Token for higher rate limits (optional, can run without it) | |
| GEMINI_API_KEY | Yes | Gemini API Key required for semantic search capabilities |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| _fetch_stars_for_userC | Fetch or update the database of starred repositories for a specific GitHub username. Args: username: The exact GitHub username (e.g., 'gulbaki'). token: Optional GitHub personal access token to avoid rate limits (defaults to GITHUB_TOKEN env). |
| search_starsA | Search through a user's starred repositories using AI-powered semantic search or keyword matching. Args: username: The exact GitHub username provided by the user. query: The search terms or project idea to find relevant repositories for. |
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 2 tools
The two tools have clearly distinct purposes: one fetches/updates the database of starred repositories, the other searches through them. No ambiguity.
Naming is inconsistent: '_fetch_stars_for_user' uses a leading underscore and underscores between words, while 'search_stars' omits the underscore prefix and uses fewer words. No consistent pattern.
With only 2 tools, the server feels minimal but could be sufficient for a focused use case of fetching and searching stars. However, it is borderline for a broader star management tool.
The set covers fetching and searching starred repositories, but lacks operations like listing all stars or deleting them. Minor gaps exist, but core functionality is present.