Skip to main content
The NeetoAuth CLI (neetoauth) lets you manage NeetoAuth from your terminal. It covers the v2 REST API: list who is in your workspace, invite new members with the right product roles, remove people who have left, see which neeto products are enabled and what roles each one exposes, and enable or disable products. It is designed for people comfortable with a terminal or HTTP. You do not need to be a developer: run neetoauth setup to connect an AI assistant such as Claude or Cursor, then describe the task in plain language.

​
Why use the CLI?

Script onboarding

Invite new joiners and assign their product roles from shell scripts, so access is granted the same way every time.

Audit access from the terminal

Pull the active member list, pipe it to jq, and reconcile it against your HR system without opening the admin UI.

Manage many workspaces

Sign in to several workspaces at once and target any of them with a single flag.

Built for AI agents

Use token-efficient --toon output and one-command setup for Claude, Cursor, Copilot, and more.

​
CLI vs MCP: which should I use?

NeetoAuth’s MCP server reaches the same resources the CLI does - workspace members and products. Two gaps are small: the ListUsers MCP tool filters by an email substring, which the CLI has no flag for, and only the CLI can enable or disable a product with neetoauth products enable and neetoauth products disable. Otherwise neither one can do more than the other, so choose on how the work reaches NeetoAuth.

​
Reach for the CLI when

  • No AI assistant should be in the loop. A cron entry or a CI step runs neetoauth with nothing but the binary and the workspace you already signed in to - no assistant open, no model account, no tokens spent per run. Over MCP, something with model access has to be running before any call happens at all.
  • The output feeds another program. --quiet prints the bare member records for the next command; --json returns records plus pagination for jq, a spreadsheet, or your own script. An assistant replies in prose you would have to copy out by hand.
  • You are working through thousands of records. Over MCP every page is a separate tool call, and a list that long crowds out the assistant’s context. The CLI pages on your terms instead: --page-size 100 with --json returns total_pages and total_records alongside the records, so a loop knows how many pages are left and walks all of them unattended. Each page lands in a file or goes straight into jq, so nothing has to be held in memory and the size of the list stops mattering.
  • You need the same run every time. A neetoauth command is plain text you can save. Drop it into a runbook or a pull request and anyone can read exactly what it will do before it runs, then run it later and get the identical call. An assistant works from a prompt rather than a fixed command, so the same request can come out as a different set of calls on a different day.

​
Reach for MCP instead when

  • The details live in your chat, not in your head. An email, a thread, or a pasted note turns into the invitation with no retyping. The CLI cannot see any of it.
  • You have not decided the steps yet. “These contractors finished last week - make sure they are out” means looking at what is there and choosing. A command can only carry out a decision you have already made.
  • One request should cover several steps. Check which products the workspace has, invite the person with the right roles, and read back the grants, with no glue between commands.
  • The person doing it does not use a terminal. NeetoAuth hosts the server, so there is nothing to install or keep updated.
You can have both. Run neetoauth setup claude and your AI assistant drives the CLI itself, so a plain-language request still ends in an exact command you can read, repeat, and paste into a script.

​
What you need

  1. Access to one or more NeetoAuth workspaces.
  2. Permission to manage the resources you want to work with (members and products).
  3. The neetoauth binary. See Installation.
Unlike the API, which authenticates with an X-Api-Key header, the CLI signs you in through your browser and stores credentials locally. See Authentication.