CLI overview

The ringee CLI puts contacts, leads, campaigns, analytics, DNC, AI pipelines, AI Voice Agents, dialing sessions and follow-ups behind a consistent command line. It is a thin front end over the Ringee MCP server—the same tools an AI assistant would call, with the same guardrails.

npm i -g ringee
export RINGEE_MCP_URL="https://api.ringee.io/api/mcp/<userId>/sse"

ringee config check
ringee contacts search acme

Configure the connection

Point the CLI at your workspace

Command reference

Every command, argument and flag

Install

npm i -g ringee
ringee --help

npx ringee --help

pnpm ringee contacts search acme
pnpm --filter ringee dev -- config check

Requires Node 20 or newer. The published binary pulls in three dependencies — @modelcontextprotocol/sdk, zod and commander.

What it is good for

Use case	Why the CLI
Quick lookups	`ringee contacts search acme` beats opening the dashboard
Scripting	`--json` on any command gives machine-readable output
AI agents	Any harness that can run shell commands can drive Ringee
Debugging MCP	`ringee config check` lists every tool the server exposes
CI and automation	No browser, no session cookie — just an env var

Command groups

Group	Purpose
`contacts`	Search, view, create, update, delete; find by call outcome
`leads`	Prospect via Apollo or Prospeo; reveal and import
`sessions`	Magic-link dialing queues
`calls`	Browse call history with outcomes, transcriptions and recordings
`outcomes`, `callbacks`, `meetings`	Log results and book the next touch
`campaigns`	Inspect campaign configuration, manage leads and read performance
`analytics`	Dashboard metrics and one-day activity
`dnc`	Manage the workspace Do Not Call suppression list
`pipelines`	Read AI pipeline state and results
`voice-agents`	List agents, start a real billed call and read its result
`config`	Connection diagnostics and the shared agent knowledge

Safety

Sensitive and destructive commands refuse to run without an explicit flag, so neither a typo nor an autonomous agent can spend credits, mint a shareable link or delete data by accident.

ringee leads reveal <jobId> <externalId> --yes
ringee sessions create --contact <id> --yes
ringee sessions revoke <sessionId> --yes
ringee contacts delete <id> --confirm-phone +14155550123 --yes
ringee campaigns delete-lead <campaignId> <leadId> --yes
ringee dnc remove +14155550123 --yes
ringee voice-agents call <agentId> --to +14155550123 --yes

See Safety and confirmations.

Output modes

By default the CLI prints readable, formatted output. Add --json to any command for the raw payload:

ringee contacts search acme --json | jq '.contacts[].phoneNumber'

Next steps

Configuration

Environment variables and diagnostics

Use it from an agent

Drive Ringee from Claude Code or any shell-capable harness

AI Voice Agents

Place and monitor autonomous calls from the CLI

Get Started

Reference

Configure the connection

Command reference

Install

What it is good for

Command groups

Safety

Output modes

Next steps

Configuration

Use it from an agent

AI Voice Agents

Configure the connection

Command reference

​Install

​What it is good for

​Command groups

​Safety

​Output modes

​Next steps

Configuration

Use it from an agent

AI Voice Agents

Install

What it is good for

Command groups

Safety

Output modes

Next steps