Herohunt MCP Server

Herohunt MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. People search API - find 1 billion candidates across LinkedIn and GitHub with real-time data.

What you get

MCP server for the HeroHunt People Search API. Search for talent across LinkedIn, GitHub, and StackOverflow from any MCP-compatible AI agent.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What the assistant can call

Once Herohunt is connected, these are the calls the assistant has available:

• people_search — Write
• people_search_paginate — Read
• account_usage_get — Read
• account_searches_list — Read
• account_upgrade_link — Read
• account_billing_portal_link — Read
• api_keys_list — Read
• api_keys_create — Write
• api_keys_rotate — Write
• api_keys_revoke — Write

Configuration and credentials

You will need 3 environment variables: HEROHUNT_API_KEY, YOUR_API_KEY, HEROHUNT_MCP_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Herohunt.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the herohunt mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Herohunt's toolset — people_search, people_search_paginate, account_usage_get and 7 more — is a fair guide to whether it matches your workflow. It is maintained by herohunt-ai; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.