Skip to main content
The NeetoEngage CLI (neetoengage) lets you work with NeetoEngage from your terminal. It covers the external API: search the public roadmap, file a customer’s request, add voters, move requests between tracks, post comments, and manage the product name and website URL. It is designed for people comfortable with a terminal or HTTP. You do not need to be a developer: run neetoengage setup to connect an AI assistant such as Claude or Cursor, then describe the task in plain language.

​
Why use the CLI?

File requests from support

Search for a duplicate, then add the customer as a voter or create a new request with a private note, straight from a support workflow.

Follow up when it ships

Move a request to the done track, attach a changelog, and email every voter in one command.

Script and audit

Pipe voters, votes and changelogs to jq, loop over pages, and switch workspaces 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?

NeetoEngage’s MCP server covers the same work through an AI assistant, with nothing to install. Choose on how the work reaches NeetoEngage.

​
Reach for the CLI when

  • No AI assistant should be in the loop. A cron entry or a CI step runs neetoengage with nothing but the binary and the workspace you already signed in to.
  • The output feeds another program. --quiet prints a bare identifier for the next command; --json returns records plus pagination for jq or your own script.
  • You need the same run every time. A neetoengage command is plain text you can save in a runbook or a pull request, then run later to get the identical call.

​
Reach for MCP instead when

  • The details live in your chat. An email or a pasted note turns into a feature request with no retyping.
  • The person doing it does not use a terminal. NeetoEngage hosts the server, so there is nothing to install or keep updated.
You can have both. Run neetoengage 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 NeetoEngage workspaces.
  2. Permission to manage feature requests in those workspaces.
  3. The neetoengage 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.