DevMatch

On this page

DevMatch MCP

The DevMatch MCP server exposes the public-work index to any client that speaks Model Context Protocol. Your assistant can search, match, and show evidence without leaving the editor.

01 · Overview

What the server does

• Matching runs server side against the whole index, never a sample.
• Results carry the evidence behind each score, so a client can show its work.
• Every call is attributed to your key, so credits and limits stay yours.

02 · Connect a client

Add the server to your client

One HTTP endpoint, one header. Paste the config below into your client, restart it, and the DevMatch tools appear alongside the rest.

Server URLCopy

https://mcp.dev-match.xyz/mcp

{
  "mcpServers": {
    "devmatch": {
      "url": "https://mcp.dev-match.xyz/mcp"
    }
  }
}

03 · Authentication

Keys and access

Every request carries a key in the Authorization header. Keys are issued after you sign in on Platform (/chat), scoped to one workspace, and rotatable under Account → API keys.

Rotating a key revokes the previous one after a 24 hour grace window, so a running client is never cut off mid session.

04 · Tools reference

Tools the server exposes

ToolCreditsPurpose

find_candidates25Find engineers who uniquely fit a job description or brief from public work. Returns a shortlist with evidence per person. This is the billable shortlist run (25 credits). Reveal on that shortlist is free. On Pro, contact fields we already have from public sources (GitHub Archive and mined records) unlock after reveal — not third-party email enrichment.

Params: input, limit, exclude, location (MCP). rerank (bool, default false on POST /api/builders/find; DevMatch MCP sends true). Omitting rerank on a raw API or SDK call can return a materially weaker embedding-only pool.

get_profile1Fetch one builder profile card by GitHub handle.

Params: handle

find_similar_projects3Find open-source projects similar to a seed repo, with top contributors.

Params: repo, limit

Free includes 250 credits / month; Pro includes 350. Credits are a company-shared pool. See pricing for plan ceilings.

find_candidates · rerankAPI default off · MCP on

find_candidates runs an embedding search first, then an optional LLM rerank that reorders the pool against your role text. Raw API and SDK calls to POST /api/builders/find default rerank to false. Omitting the flag returns embedding-only results, which can be materially weaker for the same query. Pass "rerank": true when you want the precision gate.

The DevMatch MCP server at mcp.dev-match.xyz already sends rerank: true on every find_candidates call. Cursor, Claude, and other MCP clients do not need to set the flag. In-page WebMCP on this site uses your signed-in session and the same find path as chat.

05 · WebMCP

In-page tools, not the remote server

The website also registers find_candidates, get_profile, and find_similar_projects on the page via WebMCP. An agent in your logged-in browser tab can call those functions instead of scraping or clicking. This is not /.well-known/mcp.json — that file still points at the remote MCP server for Cursor and Claude.

In-page tools use your existing session and the same contact paywall as the site. Chrome 149+ can try them with chrome://flags/#enable-webmcp-testing.

MCP Integration | DevMatch