Command-line tool¶
The Drovio app comes with a command-line tool, drovio, for scripts and AI apps
to drive it: read and send chat messages, ask participants for a decision, take
the frame of a shared screen, change what you share, create meetings, invite
contacts, let guests in, and follow all of it as it happens.
The same features are offered to AI apps as an MCP server.
Availability
The command-line tool comes with the Drovio app from version 3.7.1, on macOS, Windows and Linux, for both editions. It drives the app running on the same machine, signed in with your account. Guests in a web browser see decision cards and messages from the tool from Drovio Server 3.7.1.
Where it is¶
The tool is installed with the app, next to it.
The tool is inside the app, at
/Applications/Drovio.app/Contents/MacOS/drovio. To type drovio in a
terminal, open Preferences → Advanced, then click Install next to
CLI command in the Command-line tool section: macOS asks for an
administrator password, and the app links the tool into /usr/local/bin.
Remove takes the link away.
The tool is drovio.exe, in the app's installation directory,
C:\Program Files\Drovio by default. The installer adds that directory to the
PATH of every user: open a new terminal after installing.
When the app runs as a Windows service, the tool works from the session of the user at the console.
The tool is /opt/drovio/drovio, and /usr/bin/drovio points to it, so
drovio works in any terminal.
The command that starts the app itself is now /usr/bin/drovio-launcher.
Links, autostart entries and update scripts that still call
/usr/bin/drovio are handed over to it.
The tool needs the app to be running: otherwise it stops with exit code 4.
Allowing the tool¶
The first time the tool reaches the app, the app asks you whether to allow it. Until you answer, the command waits, a minute at most, and says so:
Your answer is kept. To change it, open Preferences → Advanced: Withdraw takes the access back, Ask Again will make the app ask you at the next command. See AI apps for what this consent covers.
First steps¶
$ drovio status
Signed in as grace@example.com
Not in a session
$ drovio meeting create
https://drovio.example.com/meet/9d612a16-07e7-464d-93a0-e692dd5286b9
$ drovio participants --json
{"participants":[{"id":"0","name":"Grace","host":true,"me":true,...}]}
- Add
--jsonfor scripts and AI apps: every command then prints one JSON object, and streams one per line. drovio helplists the commands.drovio agentsprints the guide given to AI agents: point yours to it.
For AI apps¶
An AI app can run the commands itself, or connect to the MCP server. Either way:
- everything it does is done in your name, and chat messages it sends are marked as coming from the tool;
- it only sees the screens of participants who allow it;
- it asks participants for their go-ahead with decision cards.
See AI apps for the safeguards.