ArgorantDocs
Claude Code

Claude Code

Connect Claude Code to Argorant with one command, for you or for a whole project, and let it prospect, verify and run campaigns from the terminal.

You need Claude Code and an Argorant account. No account yet? The sign-in that opens on the first tool call offers Create account, with a 7-day trial, 100 credits and 300 campaign emails.

Add the server

For yourself, in every project:

Shell
claude mcp add --transport http --scope user argorant https://mcp.argorant.com/mcp

For one project, so teammates get it too, put this in .mcp.json at the project root:

JSON
{ "mcpServers": { "argorant": { "type": "http", "url": "https://mcp.argorant.com/mcp" } } }

Sign in

Run /mcp inside Claude Code, pick argorant and choose Authenticate. The browser opens the Argorant sign-in; approve the scopes. Claude Code stores the OAuth token, never an API key. Without this step the first tool call triggers the same prompt.

Check the connection

Text
> Check my Argorant account.

You should see the connected email, your plan, your credits and what is left of today's limits. claude mcp list shows the server as connected.

Try it

  • "Find the person responsible for partnerships at Acme and their verified business email address."
  • "Find 500 relevant business owners for my bookkeeping business, draft an introduction and two follow-ups, and prepare the campaign using my connected inboxes. Show me the audience and messages before sending."
  • "Check the email addresses in leads.csv and separate valid from invalid before I use it."

Or use the CLI

Claude Code is good at terminals. npx argorant … --json returns machine-readable output and exit codes it can branch on, and it needs no MCP setup at all; see CLI. Both routes use the same account, lists and credits.

What to expect

  • Counts, previews and reading your account run without asking. Anything that spends credits (reveal, export, enrich) or sends email (launch, reply) is marked destructive; Claude Code asks before it calls.
  • If a tool answers scope_missing, run /mcp and authenticate again; the scope list is on Security and scopes.

On this page