DevMatch

MCP ServerFreemium

The devmatch mcp server connects an AI assistant to DevMatch's engineer discovery service. It can find candidates for a role, retrieve contributor profiles, and find projects similar to a repository.

Last updated: November 3, 2026

Official. Built and maintained by the company or project behind the service, so usually kept in step with it. Not audited by us.
Community. Built and maintained by an independent developer or group, not by the company behind the service. The company has not reviewed it, and updates depend on its author.

About DevMatch

DevMatch is an engineer discovery service, and the devmatch mcp server connects an AI assistant to its search tools. That lets a recruiter or technical team search for engineers who match a role or job description, retrieve an individual contributor profile by GitHub handle, and find open-source projects similar to a seed repository. DevMatch says its candidate search ranks matches using evidence from public contributions and runs against its full index. The returned evidence gives readers a basis for reviewing why a candidate matched.

What can DevMatch do?

The server exposes three documented tools for candidate sourcing and project discovery. Use candidate search to submit a role or job description and receive a ranked shortlist with evidence behind each score. Profile lookup retrieves an individual contributor profile using a GitHub handle. Similar-project search takes a seed repository and finds related open-source projects.

Find engineers matching a role or job description, with evidence behind each score.
Retrieve an individual contributor profile by GitHub handle.
Find open-source projects similar to a seed repository.

The documented tools focus on search and lookup. DevMatch says candidate searches run against its full index. Its documentation does not list a tool for contacting candidates or editing their data, so the MCP server's described role is discovery rather than outreach or record management.

How DevMatch connects and authenticates

DevMatch runs as a hosted MCP service over Streamable HTTP, so the server is not installed locally. Requests authenticate with an API key in the Authorization header. DevMatch issues keys after signup, scopes each key to one workspace, and allows keys to be rotated. The documentation names Cursor and Claude Desktop as clients and also describes compatibility with MCP-compatible assistants. It does not provide a complete supported-client list.

Who is DevMatch best for?

DevMatch may suit technical recruiters and teams looking for engineers through public contributions, or teams exploring contributors around a repository. Using the MCP server requires a DevMatch account and API key. The pricing page lists Free access with 250 company credits each month and says MCP access follows use of /chat. Pro includes 350 company credits each month. Enterprise offers contract credit allocation, integrations, and an SLA. Credits are shared across the company, reset monthly, and do not roll over.

What DevMatch can access and change

The documented MCP tools search for candidates, retrieve contributor profiles, and find similar open-source projects. The available facts describe no candidate-contacting or>GitHub MCP and GitHub Official MCP Server are related options. For searching a codebase or its indexed content, Meilisearch Official MCP Server is another option. These servers have different documented purposes from DevMatch's candidate, contributor profile, and project discovery tools, so compare their listings against the task you need to handle.

Visit Website

Key Features

Search for engineers matching a role or job description, with evidence behind each score.

Retrieve an individual contributor profile by GitHub handle.

Find open-source projects similar to a seed repository.

Run searches against DevMatch's full index, according to its documentation.

Connect through a hosted MCP endpoint using Streamable HTTP.

Use Cursor, Claude Desktop, or another MCP-compatible assistant.

Share monthly company credits across MCP calls. Credits reset monthly with no rollover.

Before you installSecurity checklist for MCP servers

An MCP server runs code and gives your AI assistant access to files, accounts or data. A few minutes of checking is worth it.

Check the source. Make sure the repository belongs to the vendor or author you expect, that the vendor's own documentation links to it, and that it is actively maintained. Beware of lookalike names.
Read what it can do. Look at the tools the server exposes and the permissions or scopes it asks for. Start with read-only access where the server allows it.
Use the least access that works. Give it a dedicated API key or a narrowly scoped token, ideally on a test project or sandbox, not your production credentials.
Pin versions and review updates. Install a specific version, read changes before upgrading, and do not run copied commands you do not understand.
Treat what it returns as untrusted. Documents, web pages and tool results can contain text that tries to steer your AI assistant. Keep confirmation switched on for actions that write, delete, send or spend.
Know where your data goes. Find out whether the server runs on your machine or is hosted, and what it sends to the vendor or to third parties.
Keep a way back. Know how to revoke the key and remove the server from your client's configuration.

This page is general information, not security or legal advice, and listing a server is not an endorsement or a security review. We do not create, host or control MCP servers, and listing details such as commands, permissions or pricing can be out of date, so check the official source. You install and use MCP servers at your own risk. See the section on third-party products in our Terms of Service.

Pricing Plans

Free

$0/month

250 company credits each month, shared across the company.
Includes directory access and MCP access after using /chat.
A shortlist run costs 25 credits; profile lookup costs 1 credit per profile.
Credits reset monthly and do not roll over.
For teams starting engineer discovery with a DevMatch account.

Pro

$129/mo

350 company credits each month, shared across the company.
Includes full profiles, contact information, and export.
A shortlist run costs 25 credits; profile lookup costs 1 credit per profile.
Credits reset monthly and do not roll over.
For teams needing more monthly credits and the listed profile and export features.

Enterprise

Custom

Contract-based credit allocation.
Integrations are included in the enterprise offer.
Service-level agreement included.
Contact sales for pricing.
For organizations that need contract-set credits, integrations, and an SLA.

Pricing information last updated: November 3, 2026

Visit Website

FAQs

What can the DevMatch MCP server do?

It can search for engineers matching a role or job description, retrieve a contributor profile by GitHub handle, and find open-source projects similar to a seed repository.

How does DevMatch MCP connect to an assistant?

It is a hosted MCP endpoint using Streamable HTTP. The documentation names Cursor and Claude Desktop, and says it works with MCP-compatible assistants.

Do I need a DevMatch account and API key?

Yes. MCP access requires a DevMatch account and an API key. Each key is scoped to one workspace.

How are MCP calls charged?

Calls use company-shared monthly credits. A shortlist run costs 25 credits, a profile lookup costs 1 credit per profile, and a similar-project search costs 3 credits. Credits reset monthly with no rollover.

What does the free plan include?

It includes 250 company credits per month. The pricing page says free signup requires no card, and MCP access is available after /chat.