Model Context Protocol
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
02 · Connect a client
One HTTP endpoint, one header. Paste the config below into your client, restart it, and the DevMatch tools appear alongside the rest.
https://mcp.dev-match.xyz/mcp{
"mcpServers": {
"devmatch": {
"url": "https://mcp.dev-match.xyz/mcp"
}
}
}03 · Authentication
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
Free includes 250 credits / month; Pro includes 350. Credits are a company-shared pool. See pricing for plan ceilings.
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
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.