Tool

ContactCTL for Claude Code

Claude Code already has the only integration surface ContactCTL needs: the Bash tool. Install once, add three lines to CLAUDE.md, and Claude finds, verifies, and enriches contacts inside the session — no MCP server, no schema overhead.

Start finding contacts Install guide

01 — The problem

Your agent writes the outreach but cannot source the data

Claude Code will happily draft a sequence, build the send script, and structure the CRM import. Then it hits the email column and stalls — or worse, guesses. Pattern-guessed addresses are how clean campaigns turn into bounce storms.

ContactCTL closes that gap as a native CLI. Claude runs it through Bash like any other tool: instant startup, deterministic exit codes, --json output it can parse without ceremony. There is no standing context cost — the tool consumes zero tokens until the moment Claude actually runs `ctc instructions` (about 60 lines, once per session).

Because every command is non-interactive and cost-capped, Claude can work unattended: estimate, run, verify, report.

02 — The workflow

How it runs

What a session actually looks like

You ask in plain language. Claude plans, runs ctc through its Bash tool, and reports with real numbers.

claude — ~/outbound

> Get me a verified email for the VP Growth at acme.com

Bash: searching for the right person first

$ ctc search people --domain acme.com --titles "VP Growth"

1 profile: Jane Smith — VP Growth

Bash: resolving and verifying the address

$ ctc find "Jane Smith" acme.com --json

jane.smith@acme.com (valid, confidence 0.98)

$ ctc verify jane.smith@acme.com --json

status: deliverable

total charged: 1.27 credits

Set it up once in CLAUDE.md

Add a short section so every future session knows the tool exists and how to behave with money.

CLAUDE.md

## Contact data

Use the contactctl CLI (alias `ctc`) for all B2B contact work:
finding work emails, verifying deliverability, reverse lookup
(whois), people/company search, and lookalikes.

- Run `ctc instructions` once per session before first use.
- Always pass --json. Preview spend with --estimate.
- Ask before any batch run estimated above 50 credits.

03 — Commands and credits

What this workflow uses

Every command reports its credit cost in the output. Preview any spend with --estimate at zero cost.

Command	Purpose	Credits
ctc instructions	Agent reads the full tool guide	free
ctc find <name> <domain> --json	Work email, parseable output	1 credit per result found
ctc verify <email> --json	Deliverability before send	0.02 credits per verification
ctc <cmd> --estimate	Spend preview, zero cost	free

Full datasheet: credit costs in the docs · plan pricing on /pricing

Three lines in CLAUDE.md. A full contact-data stack in every session.

Start finding contacts Install guide