github-talent-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | GitHub personal access token with read:user and public_repo scopes |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_developersA | Search GitHub developers by technical and geographic filters. Returns a list of matching usernames sorted by followers. Use get_developer_profile on interesting candidates for full enrichment and to verify recent activity. For topic-based sourcing (e.g. "LLM", "inference"), use get_repo_contributors on relevant repos instead — GitHub user search doesn't support topic/bio search. Args: languages: Filter by programming languages, e.g. ["python", "rust"] location: Filter by location, e.g. "San Francisco" or "Germany" min_followers: Minimum follower count min_repos: Minimum public repo count limit: Max results to return (default 20, max 100) |
| get_developer_profileA | Get enriched GitHub developer profile with activity scoring. Returns languages, stars, commit activity, OSS contributions, profile README, license breakdown, and a 0-205 activity score with per-dimension breakdown. Args: username: GitHub username to analyze |
| rank_candidatesA | Rank GitHub users against a job description. Enriches each profile, scores activity + relevance, and returns candidates sorted by combined score with strengths, gaps, and reasoning. Args: usernames: GitHub usernames to evaluate job_description: The role description to rank candidates against top_n: Number of top candidates to return (default 10) |
| score_against_jdA | Score GitHub candidates against a job description with per-dimension breakdown. Unlike rank_candidates (keyword matching), this extracts structured requirements from the JD and scores each candidate on: tech stack match, experience level, OSS signal, and leadership signals. Returns dimension scores, gaps, and personalized interview questions. Args: job_description: Full job description text usernames: GitHub usernames to evaluate top_n: Number of top candidates to return (default 10) |
| compare_candidatesA | Compare 2-5 GitHub candidates side-by-side. Shows each candidate's languages, activity, stars, strengths, and gaps. If a job description is provided, also scores each candidate against it and picks winners per dimension. Args: usernames: 2-5 GitHub usernames to compare job_description: Optional job description for JD-aware comparison |
| bulk_scoreA | Score a batch of GitHub usernames and return a ranked table. Enriches each profile and ranks by activity score (or JD fit if a job description is provided). Returns a markdown table or CSV. Args: usernames: List of GitHub usernames (max 100) job_description: Optional JD for relevance scoring export_format: Output format - "markdown" (default) or "csv" top_n: Max candidates in output (default 100) |
| generate_outreachA | Generate personalized recruiter outreach messages for a GitHub candidate. Creates three message variants (short, medium, detailed) that reference the candidate's actual repos, contributions, and tech stack. IMPORTANT: Always ask the user for their company_name and sender_name before calling this tool. If not provided, placeholders will be used. Args: username: GitHub username of the candidate job_description: The role description company_name: Your company name (ask the user) sender_name: Your name as the recruiter/hiring manager (ask the user) tone: Message tone - "casual" (default) or "formal" |
| get_repo_contributorsA | Get top contributors for a GitHub repository as candidate leads. Accepts 'owner/repo' format or full GitHub URL. Args: repo: Repository in 'owner/repo' format or GitHub URL limit: Max contributors to return (default 25) |
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
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/carolinacherry/github-talent-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server