Find business leads with emails from Google Maps, Apollo.io and LinkedIn. Prepaid, API key.
Find business leads with email addresses from inside Claude, Cursor or any other MCP client.
Ask your assistant things like:
Evascrape runs the extraction on its own servers and returns structured records. Nothing runs in your browser and no source-platform login is used.
evs_live_.Keep the key in your MCP client's config or secret store. Do not commit it to a repository.
Requires Node.js 18 or newer.
claude mcp add evascrape --env EVASCRAPE_API_KEY=evs_live_xxx -- npx -y @evascrape/mcp
Add this to the client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json, ...):
{
"mcpServers": {
"evascrape": {
"command": "npx",
"args": ["-y", "@evascrape/mcp"],
"env": { "EVASCRAPE_API_KEY": "evs_live_xxx" }
}
}
}
Claude Desktop users can also install the evascrape.mcpb file from the
latest GitHub release: open it with Claude Desktop
and paste the key when asked. The key is stored as a secret field.
| Tool | What it does | Spends credit |
|---|---|---|
google_maps_leads | Businesses from Google Maps: name, address, phone, website, rating, email where published | yes |
apollo_export | Export a people search you already built on Apollo.io | yes |
linkedin_leads | People from LinkedIn audiences by job title, location, company, revenue | yes |
job_status | Check whether an extraction has finished | no |
download | Read the finished records as structured data | no |
check_balance | Remaining prepaid credit | no |
estimate_cost | Price a job before starting it | no |
Extractions are asynchronous: a tool call starts the job and returns an id, job_status reports
progress, and download returns the records once the job has succeeded.
The three tools that start a job spend prepaid credit. Most MCP clients ask you to approve each tool
call; ask the assistant to run estimate_cost first if you want to see the price before a job starts.
Prepaid USD balance. Top-ups start from $10. No subscription, and credit does not expire.
| Source | Per 1,000 records |
|---|---|
| Google Maps | $12 |
| Apollo.io | $9 |
| LinkedIn / Sales Navigator | $9 |
| Real-time email verification (optional) | +$5 |
You pay for delivered records: the job reserves the amount when it starts and anything that could not be delivered is refunded automatically. Verification is charged only for delivered records that have an email address. Current prices: evascrape.com/pricing.
| Variable | Required | Meaning |
|---|---|---|
EVASCRAPE_API_KEY | yes | Key from your Evascrape account |
EVASCRAPE_BASE_URL | no | Override the API host, for testing. Must be https. |
https://app.evascrape.com (or the https host you set), as a Bearer header.
It is never written to stdout, logs or error messages.evascrape-mcp/<version> user agent.This server runs on your machine and sends your tool inputs (search terms, locations, filters, Apollo
URLs, job ids) and your API key to the Evascrape API at app.evascrape.com to run and read jobs. It
does not collect anything else and keeps no local files, logs or telemetry. Evascrape stores the jobs
and their results in your account. How Evascrape collects, uses, shares and retains data, and how to
contact us, is described in the Evascrape Privacy Policy.
Questions: info@evascrape.com.
include_unverified to true.npm install
npm test
Tests run the real MCP stdio protocol against a local mock API; they never call Evascrape.
MIT licensed.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @evascrape/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"com-evascrape-evascrape": {
"command": "npx",
"args": [
"-y",
"@evascrape/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@evascrape/mcpnpmEvascrape works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.