repohunt
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub personal access token (read-only) for higher rate limits. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_reposA | Search GitHub for repositories matching a development intent and return structured EVIDENCE (not a verdict) for you to rank. IMPORTANT — before calling this tool you MUST expand the user's single intent into 4-8 VARIED keyword queries: synonyms, likely library/package names, and problem restatements. Do not pass one raw phrase; keyword recall depends on the variety you supply. The server fires every query against GitHub's live search (README body included), dedupes, pre-ranks, and returns the strongest candidates each with a trimmed README excerpt + metadata. You then rank them and decide fork / study / avoid. Example — intent "rate limiting middleware for express": queries: [ "express rate limit middleware", "express-rate-limit", "api throttling node", "request throttling express", "leaky bucket rate limiter node", "ddos protection express middleware" ] |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielrltan/repohunt'
If you have feedback or need assistance with the MCP directory API, please join our Discord server