DevMatch MCP
Call DevMatch from inside Cursor, Claude Desktop, or any MCP-compatible AI assistant. Search 35M+ verified engineers, pull profiles, and find similar projects without leaving your editor.
Quick start
Two minutes from zero to first tool call. Drop the snippet into your client's MCP config, restart, sign in once via browser, and the three DevMatch tools appear in your assistant's tool list.
Cursor — Settings → MCP → Add new server
{
"mcpServers": {
"devmatch": {
"url": "https://mcp.dev-match.xyz/mcp"
}
}
}Claude Desktop — edit claude_desktop_config.json
{
"mcpServers": {
"devmatch": {
"url": "https://mcp.dev-match.xyz/mcp"
}
}
}First connection opens a browser tab for OAuth consent. Sign in (Google / GitHub / email) → click Allow → return to your editor. Subsequent connects silently re-authorize.
Tools
Three tools today. Each successful call bills the listed credits — failed, cached, and empty results don't bill.
Search 35M+ engineers by job description. Returns ranked candidates with verified contributions inline.
{ "input": "Senior Rust + WebAssembly engineer, civic-tech experience" }Multi-phase agent search across the candidate index. Each result includes login, name, bio, location, top repos, top topics, matched projects (with contribution counts), contact info, and a candidate_score. Pro callers also get email enrichment on the top 5 (where derivable).
Fetch one builder's profile card by GitHub handle.
{ "handle": "karpathy" }Returns full profile: bio, location, company, social URLs, top repos/topics, and recent_activities from the current ingestion window (2025–2026). Use when the user mentions a specific handle NOT already in a find_candidates result.
Find open-source projects similar to a seed repo, ranked by semantic similarity.
{ "repo": "karpathy/llm.c", "limit": 10 }Each result includes the project's top contributors so you can pivot from a project to its maintainers in one step. Use for landscape mapping, competitive intel, or expanding a candidate search beyond a single anchor project.
Authentication
OAuth, configured automatically when you connect. No keys to generate, store, or rotate. We use Supabase OAuth Server with PKCE — tokens are scoped to your DevMatch account and refresh transparently.
First connect opens a browser tab for consent. Sign in (Google / GitHub / email) → click Allow → return to your editor. Subsequent connects silently re-authorize.
Troubleshooting
Bug or feature request? Reach out.