GitHunt MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUNT_API_KEY | Yes | GitHunt API key. Get one at https://githunt.ai/account. | |
| GITHUNT_API_URL | No | Override the GitHunt API base URL (defaults to https://api.githunt.ai). | https://api.githunt.ai |
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_developersA | Search GitHunt's pre-indexed pool of GitHub developers by location, role, and skills. Returns candidates ranked by fit with scores, activity, and contact info. Fast (pool-served, no live crawl); page with offset. |
| get_developerA | Get a single GitHub developer's ranked profile by username: overall/profile/tech/activity scores, experience, commit activity, top repos, and contact info. Cache-first and fast; use analyze_profile for deep AI analysis. |
| analyze_profileA | Deep analysis of a GitHub profile from live GitHub data: proficiency level, best-fit roles, extracted emails. Slower and heavier than get_developer; use it to vet a shortlisted candidate. |
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 3 tools
Each tool serves a distinct purpose: searching, retrieving pre-indexed profiles, and deep live analysis. There is no overlap in functionality.
All tool names follow a consistent verb_noun pattern (search_developers, get_developer, analyze_profile), making them predictable and easy to understand.
With only 3 tools, the server is highly focused on the core workflow of finding and evaluating developers. The count is appropriate for the domain.
The set covers the main tasks: search, basic retrieval, and deep analysis. The only minor gap is a tool for managing shortlists or comparisons, but the workflow is well-supported.