What it can do

Find Candidates: Search the DevMatch index for engineers matching a job description. Pass JD text — formal description, informal request, role brief, paste of a README, or anything in between. The lon

Get Profile: Fetch one contributor's profile card when the user mentions a specific GitHub handle that was NOT already returned by find_candidates. Use cases: (a) user types 'tell me about @karpathy';

Find Similar Projects: Find open-source projects similar to a given GitHub repo, ranked by semantic similarity to its description/topics/README. Each result includes the project's top contributors so

DevMatch is an MCP server for hiring engineers based on what they've actually built. Connect from Cursor, Claude Desktop, or any MCP-compatible AI assistant and search 35M+ developers ranked by verified open-source contributions — not LinkedIn keywords or self-reported skills.

Three tools:

find_candidates — paste a job description, get a ranked shortlist with bio, top repos, contribution evidence, and contact info. Pro tier adds verified email enrichment on the top 5 results. get_profile — deep-dive any GitHub handle. Bio, recent activity, top projects, and outreach channels in one call. find_similar_projects — landscape mapping from a seed repo with top contributors surfaced, so you can pivot from a project to its maintainers in one step.

Built for mission-driven teams that want engineers who care about the work, not just check the keyword box. OAuth sign-in (no API keys to juggle). Free tier with 50 monthly credits, $129/mo Pro for higher quotas plus verified email enrichment.

DevMatch

What it can do

What data it sees

Do you need an account

find_candidates	Search the DevMatch index for engineers matching a job description. Pass JD text — formal description, informal request, role brief, paste of a README, or anything in between. The longer + more specific, the better the match. Returns ranked candidates with FULL profile data inline per result: handle, name, bio, location, followers, top_repos, top_topics, matched_projects (with contribution counts), contact info (email + social URLs when available), and candidate_score. You do NOT need to call get_profile for candidates returned here — their profiles are already embedded in the response. Only call get_profile when the user asks about a handle that was NOT in the find_candidates results. Public github.com repo URLs are also accepted as input (server fetches README + topics + language and uses it as the JD), but ONLY for PUBLIC repos. For private repos, paste the README content directly as the JD string.
get_profile	Fetch one contributor's profile card when the user mentions a specific GitHub handle that was NOT already returned by find_candidates. Use cases: (a) user types 'tell me about @karpathy'; (b) user references a handle they found elsewhere; (c) user wants to verify someone before outreach. Do NOT call this immediately after find_candidates for handles in those results — find_candidates already returns full profile data inline per candidate (bio, location, contact, top_repos, top_topics). IMPORTANT — interpreting recent_activities: this field reflects indexed GitHub activity in the current ingestion window (2025–2026), up to ~20 events per recent project. It is NOT a complete career history. Older or empty activity does not mean the person is inactive; they may be outside the index window or not yet enriched. Do not infer tenure or 'last active' from activity older than 2025.
find_similar_projects	Find open-source projects similar to a given GitHub repo, ranked by semantic similarity to its description/topics/README. Each result includes the project's top contributors so the caller can pivot from a project to its maintainers in one step. Use for landscape mapping ("what else is like X?"), competitive intel, or to expand a candidate search past a single anchor project.