Skip to main content
New in Meetily Pro 1.11.0

Meetily CLI: Meeting Notes From the Command Line

meetily-pro is the command-line tool that ships inside Meetily Pro 1.11.0. Your scripts can search meetings, export any meeting as Markdown, text or JSON, read transcripts and summaries, start or stop a recording, and subscribe to webhooks, all against Meetily's local API on your own computer. It stays off until you allow it, and it only gets the permissions you give it.

  • meetily-pro
  • Markdown, Text, JSON
  • Local API
  • Scoped Keys
  • Ships with Meetily Pro on Windows and macOS
  • Read-only until you give it a key
  • Output your scripts can parse
  • No SDK needed

The Meetily CLI, answered

Last updated: Reviewed by the Meetily team

What is the Meetily CLI?

meetily-pro is Meetily’s own command-line tool, bundled with Meetily Pro 1.11.0 and later. It is the scripting side of the same integrations that power the Meetily MCP server: a local API on your computer, per-key permissions, and signed webhooks. Use it from a shell script, cron, a task runner or any language that can run a command, while Meetily is running. It does not transcribe anything itself; Meetily does that on your computer, and the CLI reads and controls the results.

How do I turn on the Meetily CLI?

  1. Open Settings > PRO and turn on Integrations.
  2. In the Integrations tab, under Apps & scripts, turn on Allow the CLI on this computer. That gives the CLI read-only access to your meetings and recording notifications.
  3. If a script needs to start or stop recordings, click Create key, give it only the permissions it needs, copy the key (Meetily shows it once) and turn on its Allow switch.
Meetily's Apps and scripts section with the Allow the CLI on this computer switch, which gives the built-in command-line tool read-only access
Allowing the CLI gives it read-only access. Recording control needs a key.

The CLI docs show where the binary lives on Windows and macOS. meetily-pro install-cli copies it to ~/.local/bin and tells you if that folder still needs adding to your PATH.

Which commands does meetily-pro have?

The ones most scripts need, with the permission each one uses:

  • Search every transcript

    meetily-pro search "pricing page"

    Permission: Read

  • List recent meetings

    meetily-pro meetings list --limit 10

    Permission: Read

  • Export a meeting (md, txt or json)

    meetily-pro meetings export <meeting-id> --format md

    Permission: Read

  • Read a transcript

    meetily-pro transcript get <meeting-id>

    Permission: Read

  • Read a summary

    meetily-pro summary get <meeting-id>

    Permission: Read

  • Check whether Meetily is recording

    meetily-pro recording status

    Permission: Read

  • Wait (up to an hour) until a recording stops

    meetily-pro recording wait --until stopped --wait-timeout 3600

    Permission: Read

  • Start a recording

    meetily-pro recording start --meeting-name "Weekly sync"

    Permission: Record

  • Stop the recording

    meetily-pro recording stop

    Permission: Record

  • Get a webhook when a summary is ready

    meetily-pro webhooks add --url <url> --events summary.completed

    Permission: Read

  • Check your setup

    meetily-pro doctor

    Permission: None

Every command accepts --json for raw JSON output. The full list, including jobs, speaker labels and summary regeneration, is in the CLI reference.

How do I export a meeting to Markdown?

meetings export prints the meeting’s title, summary and timestamped transcript. Pick Markdown, plain text or JSON (the default), and redirect it wherever you keep notes, for example an Obsidian vault:

Code language: bash
meetily-pro meetings list --limit 5
meetily-pro meetings export <meeting-id> --format md > ~/Obsidian/Meetings/weekly-sync.md

How can a script react when a meeting ends?

Two ways. For a quick script, block until the recording stops and carry on from there. For something that runs all the time, subscribe a local endpoint to a signed webhook:

Code language: bash
# Block (up to an hour) until the current recording stops
meetily-pro recording wait --until stopped --wait-timeout 3600

# Or get a signed webhook every time a summary is ready
meetily-pro webhooks add --url http://127.0.0.1:9002/meetily --events summary.completed

Before you add a webhook, turn on Outgoing (webhooks) and add your script’s address as a local target under Integrations > Advanced. A new webhook then stays pending until you approve its destination, and Meetily shows its signing secret once, when you add it. Each delivery carries only the event name, a meeting ID and a timestamp, signed with HMAC-SHA256 in the X-Meetily-Signature header. Details are in the webhooks docs.

How does the CLI authenticate?

Allowing the CLI in the app is enough for read-only commands on the same computer. For anything more, create a key in Apps & scripts with only the permissions the script needs, copy it (Meetily shows it once), turn on its Allow switch, save it to a file, and pass it with --token-file or the MEETILY_PRO_TOKEN environment variable. The CLI no longer accepts a key directly on the command line, so it never shows up in your shell history or process list.

Code language: bash
meetily-pro --token-file ~/.config/meetily/record.key recording start --meeting-name "Design review"

Want ready-made scripts? The meetily-workflows repository has setup guides with screenshots and example workflows, and Meetily workflows walks through recipes for Obsidian, Notion, Jira, Slack and your CRM.

Meetily CLI: Common Questions

The meetily-pro command-line tool is part of Meetily Pro ($10/user/month billed annually) and is included in the 14-day Pro trial. The free Community Edition does not include it.
Yes. The meetily-pro binary ships inside Meetily Pro on both Windows and macOS (Apple Silicon). The CLI docs show where it lives and how to put it on your PATH.
No. The CLI talks to Meetily on your own computer; the API listens only there by default. Meeting notes leave the computer only if your script sends them. Webhooks carry only the event name, a meeting ID and a timestamp.
There is no official SDK. Use the meetily-pro command-line tool from any script, or call the local HTTP API directly from any language. The meetily-workflows repository includes small example helpers.
Only with a key that has the Delete permission. Even then, meetily-pro meetings delete asks for --yes when it runs from a script, and it keeps the recording files unless you also pass --delete-files.
Yes. The CLI talks to the running app's local API, so Meetily has to be open with Integrations turned on before a script or scheduled job runs.
Add --json to any command for raw JSON instead of human-readable output. meetings export writes Markdown or plain text with --format md or --format txt, and JSON by default.

Script Your Meetings

The meetily-pro CLI is part of Meetily Pro: $10/user/month billed annually, with a 14-day trial. Meetings are recorded and transcribed on your computer.

✅ meetily-pro · ✅ Local API · ✅ Signed Webhooks · ✅ Windows & macOS

Why Choose Meetily Pro?

Privacy-First Architecture

Transcription runs 100% locally; recordings and audio never leave your device. For summaries, you choose your provider: local AI or your own API key. Compliant by design with GDPR and HIPAA workflows.

Advanced AI Features

Real-time transcription, speaker identification, action item extraction, meeting summaries, and custom AI workflows.

Priority Support

Dedicated support team, direct access to engineers, custom integration assistance, and priority bug fixes.

Flexible Deployment

On-Device deployment. Local file access for custom integrations and workflows.

Buy Now

Have questions? or join our GitHub community