A Cursor MCP server that finds people, not just files

Cursor already reads your repository. The gap in an agentic workflow is usually the world outside it: who to write to, and whether their mailbox still works. TAPAC is an MCP server that closes that gap — one line of configuration, then Cursor can call tapac_find_contacts and tapac_status like any other tool.

Add it to Cursor

npx -y @tapacapi/mcp

In .cursor/mcp.json (project) or ~/.cursor/mcp.json (all projects):

{
  "mcpServers": {
    "tapac": {
      "command": "npx",
      "args": ["-y", "@tapacapi/mcp"],
      "env": { "TAPAC_API_KEY": "your-key" }
    }
  }
}

Restart Cursor; the tools appear in the MCP panel. No key yet? The server still starts and answers tapac_status with onboarding instructions instead of failing — grab a free key (100 searches, no card) at /get-key.

What the two tools do

ToolInputOutput
tapac_find_contactsindustry, job titles, company size, geography, source (web / Telegram / Discord), limitPeople with name, title, company, source — and each email already SMTP-verified
tapac_statusnothingAPI version, key state, remaining quota

The verification is not a follow-up step. Each address is checked over SMTP while the response is assembled, which is why returned contacts bounce at 2–5% instead of the 10–35% typical of stored lists.

Hosted endpoint instead of npx

If you cannot run local processes in your environment, the same server is reachable over streamable HTTP at https://tapacapi.com/mcp with an Authorization: Bearer <key> header. Clients that speak MCP over HTTP — including Claude and Codex setups — can point at that URL directly.

Why a coding editor wants a contact tool at all

What it does not do

No browser extension, no CRM, no bulk enrichment of millions of stored rows. It answers one question well: who should I contact, and is that mailbox real right now.

Where to go next

← Back to TAPAC