👉 **Start here:** <https://hunter.io/api-documentation#mcp>
If you already use Hunter MCP, the hunter mcp mcp server is the piece that lets your assistant work with it directly. 👉 Start here: https://hunter.io/api-documentation#mcp.
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.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Prerequisites — The Prerequisites tool exposed by this serverConfiguration is passed through the environment: HUNTER_API_KEY, YOUR_HUNTER_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of knowledge and memory 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. Hunter MCP's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by hunter-io; 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.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
{
"mcpServers": {
"hunter-mcp": {
"command": "uv",
"args": [
"run",
"--with",
"mcp[cli]",
"mcp",
"run",
"PATH_TO_hunter-mcp/main.py"
],
"env": {
"HUNTER_API_KEY": "YOUR_HUNTER_API_KEY"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| HUNTER_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_HUNTER_API_KEY | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.