DevMatch

KI-gestützte Rekrutierung für missionsorientierte Ingenieure — verifiziert über GitHub, X, YouTube, Medium und mehr

Dokumentation

On this page

DevMatch MCP — Run Evidence-Backed Shortlists from Cursor and Claude

What is the DevMatch MCP server, how do you install it in Cursor or Claude, which tools and credits does it use, and when should a technical founder run a JD shortlist via MCP instead of — or alongside — /chat? This page documents the hosted endpoint: install, the three priced tools, and when to use it. Not a Placement sales letter. Not a protocol tutorial.

01 · Overview

What DevMatch MCP is

A hosted remote MCP server at https://mcp.dev-match.xyz/mcp. It exposes the same public-work index story as the homepage: Unique mission fit from NASA reports, published papers, SBIR awards and code. Every signal traces to a real source, never a resume. Your assistant can search, match, and show evidence without leaving the editor.

  • 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.

What this page is not

Not a guide to building MCP servers. Not a comparison of every MCP client. Not a promise of ungated results without an account. Third-party directories sometimes list extra identifier forms, numeric limits, or client snippets — those are not first-party claims here.

02 · Connect a client

Install: Cursor and Claude

One HTTP endpoint, no local install. 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.

Free plan on pricing: MCP after /chat. This page does not document OAuth, device code, or discovery flows beyond the Authorization header and Account → API keys.

04 · Credits

Tools and credits (match pricing)

Credit numbers below match /pricing at publish. Shortlist run is shared across find_candidates, chat, and Slack /devmatch.

ActionCreditsAvailable on

Shortlist run (find_candidates / chat / Slack /devmatch)25All plans

Reveal identity on a shortlist you already paid for0Included

get_profile (MCP), per profile1All plans

find_similar_projects (MCP)3All plans

Free includes 250 company credits / month; Pro includes 350. Credits are a company-shared pool, reset monthly, no rollover, Platform only. About ten unique-fit shortlist runs on Free at 25 credits each. See pricing for plan ceilings.

05 · Tools reference

Tools the server exposes

Only these three names are first-party documented. Param names below come from this page’s existing docs. Numeric defaults, maxima, and extra identifier forms that appear on third-party scans are not taught as first-party truth.

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

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.

06 · MCP vs chat

How a JD shortlist run works via MCP vs /chat

  1. Same job. Paste or pass a job description → run against the index → shortlist with evidence and source links (homepage how it works 01–03).
  2. MCP path. An assistant in Cursor or Claude calls find_candidates with the JD or brief as input. 25 credits. Reveal is free on that shortlist. Follow up with get_profile (1) only when you need a handle outside the shortlist or deeper detail. find_similar_projects (3) is for landscape or anchor repos — not a hiring shortlist by itself.
  3. /chat path. Paste the JD in the web product. Same 25-credit shortlist meter.
  4. When MCP fits. You already live in the editor or agent loop and want tools beside code review or JD drafting.
  5. When /chat fits. No MCP client, a one-off web run, or you are starting Free and following “MCP after /chat.”

Platform channels: chat, MCP, Slack /devmatch. This page does not claim better match quality on MCP versus chat beyond the documented MCP rerank: true behavior, and it does not invent latency or default result counts.

07 · 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.

08 · Platform vs Placement

When to use Platform MCP vs Placement

Platform: monthly credits for unique-fit shortlists (chat, MCP, Slack /devmatch). Reveal is free on a shortlist you already paid for. Connect email to outreach yourself.

Placement: for urgent roles, DevMatch sources, shortlists, and runs outreach. A card is required at submit ($0 today). Fee only when a hire from the shortlist is confirmed — $10,000 under a $200k base midpoint, $15,000 at $200k and above. Never stack Platform and Placement on the same hire.

See credits and plans. This page does not claim which path converts better.

09 · Questions

Questions people ask

What is DevMatch MCP?

DevMatch MCP is a hosted remote server at https://mcp.dev-match.xyz/mcp. It exposes the same public-work index as the product: engineers and researchers found through published work, technical reports, awarded contracts, and code — not resume keywords. Your assistant can search, match, and show evidence without leaving Cursor, Claude, or another MCP client.

How do I install DevMatch MCP in Cursor or Claude?

There is no local install. Add the hosted URL https://mcp.dev-match.xyz/mcp to the client’s MCP config (mcpServers.devmatch.url), restart the client, and the three tools appear alongside your other MCP tools. Every request carries a key in the Authorization header. Keys are issued after you sign in on Platform (/chat).

What tools does DevMatch MCP expose and how many credits does each cost?

Three tools, priced on /pricing: find_candidates is a 25-credit shortlist run (shared with chat and Slack /devmatch); reveal on that shortlist is 0 credits; get_profile costs 1 credit per profile; find_similar_projects costs 3 credits. No other tool names are first-party documented.

How does an MCP shortlist run differ from using /chat?

Same job: pass a job description, run it against the index, receive a shortlist with evidence and source links. MCP is the editor/agent path (find_candidates). /chat is the web paste path. Both meter a shortlist run at 25 credits. Free plan copy says MCP after /chat. DevMatch MCP already sends rerank: true on find_candidates; raw API defaults rerank to false.

When should a team use Platform MCP credits vs DevMatch Placement?

Use Platform MCP when you want monthly credits for unique-fit shortlists from the editor, then reveal names and outreach yourself. Use Placement for urgent roles when you want DevMatch to source, shortlist, and outreach — card at submit, $0 today, fee only on a confirmed hire. Never stack Platform and Placement on the same hire.

What to do next

Add https://mcp.dev-match.xyz/mcp to Cursor or Claude, sign in on Platform for a key, and run find_candidates on a job description — unique-fit shortlist with evidence attached. Free platform credits; no card required to start.

Need outreach done for you? Submit a Placement role — card at submit, $0 today, fee only when a hire from the shortlist is confirmed. Never stack Platform and Placement on the same hire.

Related: unique-fit vs keyword recruiting · flight software from public evidence · robotics firmware from public evidence · research engineers from public work · check inbound claims · defense engineers from SBIR awards · Platform vs Placement.

DevMatch MCP — shortlists from Cursor and Claude | DevMatch