Give your AI agent a B2B contact search tool in one line of config
Published 18 September 2026 · TAPAC
Most agents are good at writing outreach and bad at knowing who to send it to. That gap is not a prompting problem — it is a missing tool. The Model Context Protocol (MCP) is the standard way to hand an agent a real capability instead of asking it to guess. TAPAC ships an MCP server, so the "find and verify contacts" step becomes a tool call.
The install
npx -y @tapacapi/mcp
That is the whole local install: no clone, no build, no Python. For clients that read JSON config (Claude Desktop, Cursor, Codex, Windsurf), the entry is:
{
"mcpServers": {
"tapac": {
"command": "npx",
"args": ["-y", "@tapacapi/mcp"],
"env": { "TAPAC_API_KEY": "your_key" }
}
}
}
If you prefer Python, uvx tapac-mcp works the same way. There is also a hosted endpoint, and a hosted SKILL.md for agents that load skills rather than servers. Full notes: tapacapi.com/mcp.html.
What the agent can call
tapac_find_contacts— takes criteria (industry, job titles, company size, location, source) and returns contacts with verification status.tapac_status— key validity and remaining searches.
Verification happens at request time, over SMTP, per address. That is the difference from a stored list: what the agent hands you is what resolved a moment ago.
What happens with no key
Nothing breaks. The server returns onboarding text pointing at /get-key instead of throwing an error into the conversation — so you can wire an agent up before you have a key, and the agent tells the user what to do. 100 searches are free and no card is required.
Why this matters with real numbers
- 23% of contacts change jobs annually (ZoomInfo, 2025) — a list is decaying the day it is bought.
- 40% of emails are dead within two years (NeverBounce).
- Fresh scraped data outperforms stale databases by 42% (Harvard Business Review, 2024).
- Personalized outreach gets 3.2× higher open rates (HubSpot, 2025) — personalization needs the right person, not just any address.
- TAPAC's own bounce rate is 2–5% against the 10–35% range typical of static databases, at $0.10–0.50 per contact.
A sane sequence
- Install the server (one line above).
- Ask the agent for contacts with tight criteria — narrow beats broad.
- Use the returned verification status; do not send to anything unverified.
- Compare with your own numbers using the free lead cost & bounce-risk calculator.
Keep reading
- TAPAC vs Apollo, ZoomInfo, Hunter and Lusha
- Verify email before sending
- What a 10–35% bounce rate actually costs you
- Comparison from the other side: Apollo alternative · ZoomInfo alternative
Get a key: tapacapi.com/get-key.
← Back to TAPAC