Search, rank, and analyze GitHub developers for tech recruiting via GitHunt's API.
Search, rank, and analyze GitHub developers for tech recruiting via GitHunt's API. Exposed over MCP by the githunt mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Ask "find backend engineers in Berlin who know Go and Kubernetes" and get back a ranked, scored shortlist with activity signals and contact info.
Everything the assistant can do here goes through one of these:
search_developers — Search GitHunt's pre-indexed pool by location, role, skills, languages, and more. Returns candidates ranked by fit with scores, activity, and contactget_developer — Get one developer's ranked profile by login/username: overall, profile, tech-stack, and activity scores, experience, commit activity, top repos, andanalyze_profile — Deep AI analysis of a profile from live GitHub data: proficiency level, best-fit roles, and extracted emails. Use it to vet a shortlisted candidateCursor — Any MCP client that speaks stdio works the same way: run npx githunt-mcp with GITHUNT_API_KEY in the environmentYou will need 2 environment variables: GITHUNT_API_KEY, GITHUNT_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Githunt's toolset — search_developers, get_developer, analyze_profile and 1 more — is a fair guide to whether it matches your workflow. It is maintained by githunt-agent; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| search_developers | Search GitHunt's pre-indexed pool by location, role, skills, languages, and more. Returns candidates ranked by fit with scores, activity, and contact info. Pages via offset (0-200). Returns a markdown table plus structur |
| get_developer | Get one developer's ranked profile by login/username: overall, profile, tech-stack, and activity scores, experience, commit activity, top repos, and contact info. |
| analyze_profile | 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. |
| Cursor | Any MCP client that speaks stdio works the same way: run npx githunt-mcp with GITHUNT_API_KEY in the environment. |
{
"mcpServers": {
"githunt": {
"command": "npx",
"args": ["-y", "githunt-mcp"],
"env": {
"GITHUNT_API_KEY": "your-value",
"GITHUNT_API_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| GITHUNT_API_KEY | Credential the server authenticates with. | Yes |
| GITHUNT_API_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.