Install the NeetoRecord CLI
macOS with Homebrew:
brew install neetozone/tap/neetorecord
macOS or Linux:
curl -fsSL https://neetorecord.com/cli/install.sh | sh
Windows (PowerShell):
irm https://neetorecord.com/cli/install.ps1 | iex
Then sign in. This opens your browser, and there's no API key to manage:
neetorecord login --subdomain your-workspace
To teach your AI coding assistant how to use the CLI, run one of these from your project folder:
neetorecord setup claude # Claude Code
neetorecord setup cursor # Cursor
neetorecord setup codex # Codex
neetorecord setup copilot # GitHub Copilot
neetorecord setup gemini # Antigravity CLI and Gemini CLI
neetorecord setup windsurf # Devin (formerly Windsurf)
Every command supports --json for structured output and --toon for a more compact format that uses fewer tokens when processed by AI assistants. See the NeetoRecord CLI reference for the complete list of commands.
Automate with the CLI
Why use a CLI when MCP already exists? Because some tasks don't need AI at all. You can run them on a schedule using the NeetoRecord CLI and familiar tools such as jq, curl, and your cloud CLI. No AI account, no model usage costs, and consistent results every time.
Export your recording library to a file
This script retrieves all recordings, one page at a time, and saves each recording as a separate line in a JSONL file. The next three examples reuse this file.
page=1
while :; do
out=$(neetorecord recordings list \
--page "$page" --page-size 100 --json) || exit 1
echo "$out" | jq -c '.data[]'
total=$(echo "$out" | jq '.pagination.total_pages')
[ "$total" -le "$page" ] && break
page=$((page + 1))
done > recordings.jsonl
Export your recording library to CSV
jq -r '[.title, .duration, .view_count, .folder_name, .created_at,
.public_url] | @csv' recordings.jsonl > recordings.csv
Post the most-watched recordings every week
jq -s '{text: ([sort_by(-.view_count)[:10][]
| "\(.view_count) views \(.title)"] | join("\n"))}' \
recordings.jsonl \
| curl -s -X POST -H "Content-Type: application/json" \
-d @- "$SLACK_WEBHOOK_URL"
Back up transcripts nightly
mkdir -p transcripts
jq -r '.id' recordings.jsonl | while read -r id; do
neetorecord recordings transcript "$id" --json \
> "transcripts/$id.json"
done
aws s3 sync transcripts \
"s3://your-backup-bucket/neetorecord/transcripts/"
Request a recording from your support tool
When a support ticket requires a screen recording, use your helpdesk script to create a recording request. The request is associated with the NeetoRecord account used by the CLI, and the command returns a link you can share with the customer.
neetorecord recording-requests create \
--title "Screen recording for ticket #1042" \
--request-instructions \
"Record from opening the app until the error appears."
Retitle and file a recording
folder=$(neetorecord folders create --name "Customer calls" --quiet)
neetorecord recordings update 3f6a1c58-0b6e-4c71-9d0a-2f4e8b7c1d93 \
--title "Acme onboarding call" --tag customer --tag onboarding \
--folder-id "$folder"
Add and deactivate teammates
neetorecord team-members create --email jane@example.com --role Standard
neetorecord team-members delete "$(neetorecord team-members list \
--email sam@example.com --quiet | jq -r '.[0].id')"
Let a coding agent build it for you
You don't have to write these scripts yourself. Claude Code, Codex, or another coding agent can write the automation and use the open-source NeetoRecord CLI to work with your library. Run neetorecord setup claude (or setup codex, setup cursor) once, then ask:
Every Friday at 4 PM, use the NeetoRecord CLI to post this week's new recordings, with their view counts and links, to our Slack channel. Write the script, test it, and set up the cron job.
Using the NeetoRecord CLI, write a script that downloads the transcript of every recording in the Customer calls folder into a Markdown file per call.
You get the convenience of a chat, and the result is a script you can read, run, and commit.
When to use the CLI and when to use MCP
Both work with the same recordings, folders, and tags. Pick based on how the work reaches NeetoRecord.
Use MCP when:
- You want to understand a recording. Summaries, action items, and "what's on screen at 0:48" need someone to read the transcript or look at the frame.
- You're searching by meaning. Finding the call where something was said works best when the assistant can read and compare.
- You're asking a question. "Which recordings don't have transcripts?" needs someone to look and explain.
- You don't use a terminal. NeetoRecord hosts the server. There's nothing to install.
Use the CLI when:
- No AI should be in the loop. A cron job or CI step runs the CLI with nothing but the binary. No model account, no cost per run.
- The output feeds another program. The CLI prints raw JSON for
jq, a spreadsheet, a Slack webhook, or your own script. - You're working through thousands of recordings. The CLI pages through everything unattended.
- You're onboarding or offboarding in bulk. A script can add or remove a whole list of teammates in one run.
You can also have both. With neetorecord setup claude, your AI assistant drives the CLI for you, so a plain-language request still ends in a command you can read and reuse.
Open source
The NeetoRecord CLI is open source and available on GitHub. You can inspect its code, see exactly what it sends to NeetoRecord, and customize it for your workflows. Written in Go, it runs on macOS, Linux, and Windows.
The NeetoRecord CLI is built on neeto-cli-commons, the shared foundation for all Neeto CLI tools. This means the commands and conventions you learn in one Neeto CLI will feel familiar across the others.
Found a bug or have an idea for a new command? Open an issue or submit a pull request on GitHub.
Frequently asked questions
Can I automate NeetoRecord without using AI?
Yes. The NeetoRecord CLI works directly from your terminal, shell scripts, cron jobs, and CI workflows. You don't need Claude, ChatGPT, or any other AI service to automate tasks.
Is the NeetoRecord CLI open source?
Yes. The NeetoRecord CLI is open source and available on GitHub. You can inspect the code, modify it, and contribute improvements.