GitHunt MCP
Search a pre-indexed pool of GitHub developers with filters like location, role, skills, and languages; retrieve ranked profiles with scores and contact info; perform deep AI analysis on specific GitHub profiles for proficiency and role fit.
githunt-mcp
An MCP server that gives your AI assistant a recruiter's view of GitHub. It wraps GitHunt's API so Claude, Cursor, and other MCP clients can search a pre-indexed pool of GitHub developers, look up a ranked profile, and run deep AI analysis on a candidate - all from a chat prompt.
Ask "find backend engineers in Berlin who know Go and Kubernetes" and get back a ranked, scored shortlist with activity signals and contact info.
Prefer zero setup? GitHunt also runs a hosted MCP server at
https://mcp.githunt.ai/mcp. Add it as a custom connector in Claude (Settings -> Connectors) or as a remote MCP server in your client and sign in with your GitHunt account - no API key or local process needed. This package is the self-hosted (stdio) alternative.
Quickstart
Grab an API key from your GitHunt account.
Run the server:
GITHUNT_API_KEY=your-key-here npx githunt-mcpWire it into your client (see below), then just ask.
Environment variables
Variable | Required | Description |
| yes | Your GitHunt API key |
| no | API base URL (default |
Claude Code
claude mcp add githunt -e GITHUNT_API_KEY=your-key-here -- npx githunt-mcpClaude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"githunt": {
"command": "npx",
"args": ["githunt-mcp"],
"env": {
"GITHUNT_API_KEY": "your-key-here"
}
}
}
}Cursor
Add to .cursor/mcp.json:
{
"mcpServers": {
"githunt": {
"command": "npx",
"args": ["githunt-mcp"],
"env": {
"GITHUNT_API_KEY": "your-key-here"
}
}
}
}Any MCP client that speaks stdio works the same way: run npx githunt-mcp with
GITHUNT_API_KEY in the environment.
Related MCP server: Repo Radar MCP
Try it
Once connected, prompt your assistant naturally:
"Find senior frontend developers in Warsaw who know React and TypeScript."
"Show me hireable DevOps engineers in Poland with 5+ years on GitHub."
"Give me the next 25 candidates for that search." (paging via
offset)"Pull up octocat's GitHunt profile."
"Do a deep analysis of torvalds - proficiency, best-fit roles, any public emails."
"Search for ML engineers in San Francisco, then analyze your top 3."
Tools
Tool | What it does | Speed |
| Search GitHunt's pre-indexed pool by | Fast (pool-served, no live crawl) |
| Get one developer's ranked profile by | Fast (cache-first) |
| Deep AI analysis of a profile from live GitHub data: proficiency level, best-fit roles, and extracted emails. Use it to vet a shortlisted candidate. | Slower (live crawl) |
Supported role values: fullstack, frontend, backend, mobile,
devops, ai-engineer, ai-orchestrator, ml-engineer, data-scientist,
data-engineer, security, cloud, blockchain, embedded, gamedev,
ios-developer, android-developer, sre, platform-engineer,
qa-engineer, solutions-architect, cto, vp-engineering,
head-engineering, engineering-manager, tech-lead, product-manager,
director-engineering.
Skills are matched with synonyms (k8s -> kubernetes), and locations are
normalized (SF, NYC, UK, Warszawa).
Full API reference: https://docs.githunt.ai
Scoring
Each candidate carries an overall score built from three dimensions, all
surfaced in get_developer:
Profile score - bio, seniority signals, and account maturity.
Tech-stack score - how well their languages and repos match the requested skills and role.
Activity score - recency and volume of public contributions (commits, frequency, commit-message quality).
search_developers ranks the pool by fit for your query; analyze_profile
recomputes proficiency and role fit against fresh GitHub data.
Quotas
Requests count against your GitHunt plan's quota. Every response includes your
current usage (used / limit for the month), and a quota_exceeded error tells
you when you've hit the cap. See your account for
plan limits.
Limitations & responsible use
GitHunt reads public GitHub activity, which is strong evidence of technical work but far from the whole picture:
It's blind to private-repo, internal, and enterprise contributions - many excellent engineers have quiet public profiles.
The candidate pool is pre-indexed, so brand-new or rarely-active accounts may be missing;
analyze_profilefetches live data for a specific person.Public-activity signals can skew by geography, employer, and career stage.
Use this as a lead generator, not an automated filter. Treat scores as a starting point for a human conversation, not a hiring decision. GitHub is not the whole engineer.
Contributing
Issues and pull requests are welcome. Please open an issue describing the change before sending a large PR. For API behavior and endpoint details, see https://docs.githunt.ai.
License
MIT - see LICENSE.
Available Tools
3 toolsanalyze_profileAnalyze GitHub profileARead-onlyInspect
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.
Inputs: login, username.
get_developerGet developer profileARead-onlyInspect
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.
Inputs: login, username.
search_developersSearch developersARead-onlyInspect
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.
Inputs: location (required), role, offset, skills, +5 more. Returns: offset, results, totalCount, matchedCount, +1 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
The open-source talent graph for humans and AI agents. Find developers.
Hire engineers by what they shipped: find, judge and shortlist developers from public GitHub work.
Hiring developers? Find and source software engineers by what they build on GitHub.
Find software engineers by what they built on GitHub: search, similar, enrich, deep research.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables querying and analysis of public GitHub repositories for statistics, contributor data, and commit history. It provides both a RESTful API and an MCP interface for seamless integration with AI agents.MIT
- AlicenseNot gradedqualityDmaintenanceDiscover, rank, and compare GitHub repositories from any MCP-compatible AI client. Enables searching, filtering, ranking, and evaluating open-source repositories by topic, language, stars, license, activity, and relevance.MIT
- AlicenseAqualityCmaintenanceMCP server that searches, scores, and ranks GitHub developers for technical recruiting.810Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered GitHub interactions including repository analysis, code search, PR reviews, and more through the MCP protocol.4MIT