Claude Code can use Argorant in two ways. The connector gives Claude Code the same Argorant tools Claude has in chat, approved once in your browser with no key. The Argorant command line (npx argorant) runs with a private key and writes real files, which suits exports into a repo. You can use either or both. They share one account, one credit balance and the same lists.
Who can do it
- Anyone with an Argorant account and a confirmed email address. A trial account works, and counting and previewing are free.
- You need Claude Code installed and signed in. For the command line you also need Node.js with npm on the same machine.
- If your company manages Claude Code settings centrally, an admin may limit which servers you can add. Ask them if the command is refused.
The connector, step by step
- Open a terminal in the project where you use Claude Code and run the command below. If an
argorantserver is already listed inclaude mcp list, keep it instead of adding a second one. - Start Claude Code, type
/mcp, pick argorant and choose to authenticate. - Your browser opens Argorant's screen. Sign in if asked, check the Signed in as line, and click Allow access.
- Back in Claude Code,
/mcpshows argorant as connected. Ask your first question in a task.
claude mcp add --transport http argorant https://mcp.argorant.com/mcp
By default Claude Code saves the server for the current project only. To have it in every project, add --scope user to the command. To share it with your team through the repo, use --scope project. That shares the server entry, never your sign-in. Each teammate approves with their own Argorant account.

Why the screen says "an app on this computer"
Claude Code runs on your own machine, so the sign-in returns to an address on your computer, not to a website Argorant can check. That is why Argorant's screen is headed Connect Argorant to an app on this computer, shows a yellow note that Argorant cannot check this app, and has an Allow access button. It is expected. Continue only if you just ran /mcp yourself.

The list under This connection can is the same as for Claude in the browser. It covers counts and masked previews, lists, campaigns, reveals at 1 credit per new contact, exports that spend credits and checks of your own email lists. Approving spends nothing.
The command line with a private key
On the AI connections page the Claude Code tab opens on the setup prompt by default. It asks you to create a private key, then gives you a prompt to paste into Claude Code. Claude Code then logs in to the Argorant command line with that key.

- Click Create private key. The key is shown once and starts with
ag_live_. - Click Copy setup prompt and paste it into Claude Code in a project you trust.
- Claude Code runs the login and an account check, then asks who you want to reach.
If you prefer to do it yourself, keep the key in your environment, not in a file in the repo:
export ARGORANT_API_KEY=ag_live_...
npx argorant login "$ARGORANT_API_KEY"
npx argorant whoami
npx argorant count --keywords logistics --country "United States" --seniority vp --json
whoami and count are free. Exports write a CSV straight into your project:
npx argorant export --keywords logistics --country "United States" -n 500 -o leads.csv
An export costs 1 credit per working email in the file. When the command runs inside an agent, with --json or --yes, or without a terminal, it does not stop to ask. It spends right away. So tell Claude Code in your project instructions that reveals and exports need your explicit go.
Prompts to try
Check my Argorant account.
Through the connector this calls the account check. Through the command line it runs argorant whoami. Free either way.
Count heads of procurement at manufacturers in Germany, then show five masked examples.
A count and a preview. Both free. The preview shows initials, job, company and place, no emails.
Save that search as a list called "DE procurement" and tell me when it is ready.
Claude Code saves a private list and checks its status until it has filled. Free, nothing sent.
Export the list to data/de-procurement.csv, at most 200 rows. Tell me the cost first.
Claude Code should state that each person with a working email costs 1 credit and wait for your yes. With the command line the file lands at that path. Through the connector you get a download link.
Write a script that counts our ICP every Monday and saves the number to metrics.json. Use only free calls.
Claude Code writes a script around npx argorant count --json. Counts are free and the JSON output has stable field names, so the script does not break on wording changes.
Find the work email of Anna Weber at northwind-supply.example.
The email finder costs 1 credit when an address is found and a quarter credit when nothing is found. Claude Code should ask first.
What it costs
Search, counts and masked previews do not deduct credits. Account permissions and rate limits still apply. Reveals, exports and email lookups use your normal credits. Connecting Claude Code or creating a key does not add credits. During the trial and without a plan, searches and counts through a key or the command line are limited to 10 a minute, 500 counts and 500 search rows a day per account. Through the connector the limits are 20 a minute and 1,000 a day.
Common mistakes
- The server was added in another folder. Without
--scope userit only exists in the project where you ran the command. Runclaude mcp listin the project you are in. - Two Argorant entries. Remove the extra one with
claude mcp removeand its name. - The browser does not open. Copy the link Claude Code prints into your browser on the same computer. The sign-in must come back to this machine.
- The key ended up in a commit. Revoke it at once under Settings, then API keys, and create a new one. Keep keys in the environment or a secret store.
- Exit code 2 from the command line. The key was rejected. Exit code 5 means the action needs credits or a plan.
Disconnect
For the connector, open Settings, then AI connections in Argorant and click Disconnect next to the app under Connected apps. Then run claude mcp remove argorant to remove the entry from Claude Code. For the command line, run npx argorant logout and revoke the key under Settings, then API keys. Revoking works at once. The next request with that key fails with 401.
What happens next
Lists, exports and spent credits show in the app exactly as if you had done it yourself. For scripts, read CLI exit codes and exports from the CLI.