A lead generation MCP server your agent can call

Most “AI lead generation” still ends with a human copying rows out of a dashboard. An MCP server removes that step: the agent asks for contacts the same way it asks for the weather, and gets back records it can act on.

Install in one line

npx -y @tapacapi/mcp

Or without a local install, against the hosted endpoint:

https://tapacapi.com/mcp

Client config (Claude Desktop, Cursor, Codex, Windsurf) is a JSON block with the server name tapac — the full snippet is on the MCP page.

The two tools

ToolWhat it does
tapac_find_contactsTakes industry, job_titles, company_size, location, source, limit and returns contacts with SMTP-verified emails.
tapac_statusAccount and quota status, so the agent can tell the user what is left before it burns searches.

Without an API key the server returns onboarding instead of an error, which means you can install it and inspect the tool list before you sign up for anything.

Why verification belongs inside the tool call

If the agent can only retrieve stale rows, it automates the bounce. TAPAC returns 2–5% bounce because the SMTP check happens at request time.

Cost, in agent terms

100 free searches, then $0.10–0.50 per verified contact, pay-per-use. There is no seat licence, so a team of three running one agent pays for the contacts it actually used — not for three logins.

What agents should not do

This is a business-contact tool. It should not be used for consumer or personal contact data, and it should never invent a contact that the tool did not return — the server's own instructions say the same thing.

Where to go next

← Back to TAPAC