{
  "markdown": "# githunt-mcp\n\n[![npm version](https://img.shields.io/npm/v/githunt-mcp.svg)](https://www.npmjs.com/package/githunt-mcp)\n[![node](https://img.shields.io/node/v/githunt-mcp.svg)](https://www.npmjs.com/package/githunt-mcp)\n[![license](https://img.shields.io/npm/l/githunt-mcp.svg)](./LICENSE)\n[![MCP](https://img.shields.io/badge/MCP-server-blue.svg)](https://modelcontextprotocol.io)\n\nAn [MCP](https://modelcontextprotocol.io) server that gives your AI assistant a\nrecruiter's view of GitHub. It wraps [GitHunt's](https://githunt.ai) API so\nClaude, Cursor, and other MCP clients can **search a pre-indexed pool of GitHub\ndevelopers, look up a ranked profile, and run deep AI analysis on a\ncandidate** - all from a chat prompt.\n\nAsk *\"find backend engineers in Berlin who know Go and Kubernetes\"* and get back\na ranked, scored shortlist with activity signals and contact info.\n\n> **Prefer zero setup?** GitHunt also runs a hosted MCP server at\n> `https://mcp.githunt.ai/mcp`. Add it as a custom connector in Claude\n> (Settings -> Connectors) or as a remote MCP server in your client and sign in\n> with your GitHunt account - no API key or local process needed. This package\n> is the self-hosted (stdio) alternative.\n\n## Quickstart\n\n1. Grab an API key from your [GitHunt account](https://githunt.ai/account).\n2. Run the server:\n\n   ```bash\n   GITHUNT_API_KEY=your-key-here npx githunt-mcp\n   ```\n\n3. Wire it into your client (see below), then just ask.\n\n### Environment variables\n\n| Variable | Required | Description |\n|---|---|---|\n| `GITHUNT_API_KEY` | yes | Your GitHunt API key |\n| `GITHUNT_API_URL` | no | API base URL (default `https://api.githunt.ai`) |\n\n### Claude Code\n\n```bash\nclaude mcp add githunt -e GITHUNT_API_KEY=your-key-here -- npx githunt-mcp\n```\n\n### Claude Desktop\n\nAdd to `claude_desktop_config.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"githunt\": {\n      \"command\": \"npx\",\n      \"args\": [\"githunt-mcp\"],\n      \"env\": {\n        \"GITHUNT_API_KEY\": \"your-key-here\"\n      }\n    }\n  }\n}\n```\n\n### Cursor\n\nAdd to `.cursor/mcp.json`:\n\n```json\n{\n  \"mcpServers\": {\n    \"githunt\": {\n      \"command\": \"npx\",\n      \"args\": [\"githunt-mcp\"],\n      \"env\": {\n        \"GITHUNT_API_KEY\": \"your-key-here\"\n      }\n    }\n  }\n}\n```\n\nAny MCP client that speaks stdio works the same way: run `npx githunt-mcp` with\n`GITHUNT_API_KEY` in the environment.\n\n## Try it\n\nOnce connected, prompt your assistant naturally:\n\n- *\"Find senior frontend developers in Warsaw who know React and TypeScript.\"*\n- *\"Show me hireable DevOps engineers in Poland with 5+ years on GitHub.\"*\n- *\"Give me the next 25 candidates for that search.\"* (paging via `offset`)\n- *\"Pull up octocat's GitHunt profile.\"*\n- *\"Do a deep analysis of torvalds - proficiency, best-fit roles, any public emails.\"*\n- *\"Search for ML engineers in San Francisco, then analyze your top 3.\"*\n\n## Tools\n\n| Tool | What it does | Speed |\n|---|---|---|\n| `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 structured JSON. If a location matches nothing, it suggests similar supported locations instead of an empty page. | Fast (pool-served, no live crawl) |\n| `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. | Fast (cache-first) |\n| `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. | Slower (live crawl) |\n\n**Supported `role` values:** `fullstack`, `frontend`, `backend`, `mobile`,\n`devops`, `ai-engineer`, `ai-orchestrator`, `ml-engineer`, `data-scientist`,\n`data-engineer`, `security`, `cloud`, `blockchain`, `embedded`, `gamedev`,\n`ios-developer`, `android-developer`, `sre`, `platform-engineer`,\n`qa-engineer`, `solutions-architect`, `cto`, `vp-engineering`,\n`head-engineering`, `engineering-manager`, `tech-lead`, `product-manager`,\n`director-engineering`.\n\nSkills are matched with synonyms (`k8s` -> `kubernetes`), and locations are\nnormalized (`SF`, `NYC`, `UK`, `Warszawa`).\n\nFull API reference: <https://docs.githunt.ai>\n\n## Scoring\n\nEach candidate carries an **overall score** built from three dimensions, all\nsurfaced in `get_developer`:\n\n- **Profile score** - bio, seniority signals, and account maturity.\n- **Tech-stack score** - how well their languages and repos match the requested\n  skills and role.\n- **Activity score** - recency and volume of public contributions (commits,\n  frequency, commit-message quality).\n\n`search_developers` ranks the pool by fit for your query; `analyze_profile`\nrecomputes proficiency and role fit against fresh GitHub data.\n\n## Quotas\n\nRequests count against your GitHunt plan's quota. Every response includes your\ncurrent usage (`used / limit` for the month), and a `quota_exceeded` error tells\nyou when you've hit the cap. See [your account](https://githunt.ai/account) for\nplan limits.\n\n## Limitations & responsible use\n\nGitHunt reads **public GitHub activity**, which is strong evidence of technical\nwork but far from the whole picture:\n\n- It's blind to private-repo, internal, and enterprise contributions - many\n  excellent engineers have quiet public profiles.\n- The candidate pool is pre-indexed, so brand-new or rarely-active accounts may\n  be missing; `analyze_profile` fetches live data for a specific person.\n- Public-activity signals can skew by geography, employer, and career stage.\n\nUse this as a **lead generator, not an automated filter**. Treat scores as a\nstarting point for a human conversation, not a hiring decision. GitHub is not\nthe whole engineer.\n\n## Contributing\n\nIssues and pull requests are welcome. Please open an issue describing the change\nbefore sending a large PR. For API behavior and endpoint details, see\n<https://docs.githunt.ai>.\n\n## License\n\nMIT - see [LICENSE](./LICENSE).\n",
  "bytes": 6055,
  "sha": "8e31a8f282c9772fdff0b8cf64e4088eb315d6c921b8dfb8126249ef60d7eb00",
  "repo_slug": "githunt-agent/githunt-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_githunt_agent_githunt_mcp_9f8fd148/readme"
}