Skip to content

Tool

ContactCTL for Cursor

Cursor’s agent runs terminal commands, and ContactCTL is built to be run by agents. Add one project rule and the agent that edits your outreach scripts can also fill them with verified contact data.

01 — The problem

The data step breaks the flow

You are in Cursor building a campaign script. The code is done in minutes — then the work moves to browser tabs: an enrichment dashboard here, a verifier there, a CSV download in between. The editor flow dies at the data step.

With ContactCTL the data step is a terminal command, which means Cursor’s agent can do it as part of the task: enrich the fixture file, verify the seed list, resolve the missing emails in the CSV it just generated. Everything stays in the project, in version control, in one tool.

A project rule tells the agent the tool exists; ctc instructions teaches it the rest on demand — about 60 lines, read once per session.

02 — The workflow

How it runs

A rule the agent picks up

Drop a rule file in the repo so every Cursor session knows about the CLI and the spending etiquette.

.cursor/rules/contactctl.mdc
---
description: B2B contact data via the contactctl CLI
alwaysApply: true
---

Use `ctc` (contactctl) in the terminal for contact tasks:
- `ctc find "<name>" <domain>` — work email
- `ctc verify <email>` — deliverability
- `ctc whois <email>` — person + company behind an email
- `ctc search people|companies …` — scoped search

Run `ctc instructions` before first use. Always pass --json.
Preview batch spend with --estimate; cap with --max-cost.

In the integrated terminal

The agent enriches the file it just created, without leaving the editor.

cursor — terminal
$ ctc find targets.csv targets-enriched.csv --estimate
estimate: up to 48 credits · misses free
$ ctc find targets.csv targets-enriched.csv --max-cost 50
done: 44 found · 4 not found
charged: 44 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.

CommandPurposeCredits
ctc find <in.csv> <out.csv>Enrich the file in the repo1 credit per row found
ctc verify <email> --jsonCheck addresses in test fixtures0.02 credits per verification
ctc search filtersList accepted search filter valuesfree, runs locally

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

Next

One rule file. The data step never leaves the editor again.