Release Highlights
LatestYour meeting notes no longer have to stay inside Meetily. Ask your AI assistant about any meeting, and let your own scripts send notes where your team works - off by default and part of Pro. Plus summaries that stick to the facts, meeting links on Windows, and safer imports of long recordings.
Table of Contents
What's New in Pro 1.11.0
Meetily Pro 1.11.0, released on September 24, 2026, connects your meeting notes to the tools you already use. Your AI assistant (Claude, Cursor, Windsurf or any app that supports MCP) can now search your meetings and read their transcripts and summaries, and your own scripts can export notes and react the moment a summary is ready. Meetily still records and transcribes on your own Windows or Mac computer, with no bot joining the call, and the new integrations are part of Meetily Pro and off by default.
This release also makes summaries stick to the facts, brings meetilypro:// links to Windows, and makes importing long recordings faster and safer. If you are coming from Pro 1.9.2, this update brings everything below in a single upgrade.
Connect Meetily to the Tools You Use
The new integrations are part of Pro and are off by default. Nothing is connected until you turn on Integrations in Settings > PRO. That adds an Integrations tab, where you connect assistants and manage keys. Step-by-step setup with screenshots is below, and the full guide is in the Meetily developer docs(opens in new tab).
Ask your AI assistant about your meetings
Meetily Pro now includes an MCP server. MCP (Model Context Protocol) is the open protocol, introduced by Anthropic in 2024, that AI assistants use to connect to other apps. Connect Claude Desktop, Claude Code, Codex, Cursor or Windsurf from Settings in one click when it is installed on the same computer, or add another assistant that supports MCP by hand, such as VS Code. Then ask things like "What did we decide last week?" or "What are my action items from yesterday's call?"
Your assistant can search all your meetings and read transcripts and summaries, and, if you allow it, start or stop a recording. You choose exactly what each assistant is allowed to do, and you can disconnect it at any time.
Meetily hands your meetings to the assistant on your own computer. What happens next is up to the assistant: most send what they read to their own AI provider, as they do with anything else you ask them. Connect the ones you already trust with your meeting notes, and check how each AI provider handles your data if you are not sure.
Step-by-step guides: the Meetily MCP server, connect Claude Desktop or Claude Code, and use your meetings in Cursor, Windsurf or Codex.
Send your notes where your team works
Meetily can now tell your tools the moment a summary is ready or, with the Record permission, a recording ends, using webhooks signed with HMAC-SHA256 so your script can check they came from Meetily. The meetily-pro command-line tool, which ships inside the app, lets your own scripts export any meeting as Markdown, text or JSON and, with a key that has the Record permission, start or stop recordings, so your notes can reach Notion, your CRM or your Obsidian vault without copy-paste. Meetily does not post to those apps itself; your script does.
For example, this exports a meeting's title, summary and timestamped transcript as Markdown:
meetily-pro meetings export <meeting-id> --format mdYou create a key for each script or tool, give it only the permissions it needs, turn on its Allow switch, and can revoke it at any time. Every command is on the Meetily CLI page, and Meetily workflows has recipes for Obsidian, Notion, Jira, Slack and your CRM.
Summaries That Stick to the Facts
The default summary now only includes what was actually said. It no longer lists someone as an attendee just because their name came up, or fills in a meeting date nobody mentioned. Long meetings now summarize in full with local or cloud AI, and summaries made with Ollama follow the settings you chose.
Meeting Links Now Work on Windows
meetilypro:// links let you open a meeting, start or stop a recording, or activate your license from an email, a calendar invite or another app. They now work on Windows as well as on Mac. On Mac, links work when Meetily is already open. Links are off by default: turn on meetilypro:// links under Settings > Integrations > Advanced, and on Windows restart Meetily once afterwards. License activation links always work.
Stability & Reliability
- Imported recordings longer than about 5 minutes are no longer transcribed from slowed-down audio.
- A large audio import can no longer use up so much memory that it slows down or freezes your computer. Very long files are now refused at the start instead: roughly anything over 3 hours of 48 kHz stereo audio, and less for higher-quality or multichannel files.
- Pausing or cancelling a large import now takes effect in seconds instead of minutes.
- Settings now explain when Speaker Diarization needs "Save Audio Recordings" turned on.
Upgrade
The app will prompt you to update via the in-app update dialog. Click "Update Now!" to install. All existing settings, recordings, and models are preserved.
Download
- macOS (Apple Silicon): Download .dmg(opens in new tab)
- Windows: Download .exe(opens in new tab)
If the links above are slow or blocked on your network, use the alternative hosts:
- macOS (Apple Silicon): Alternative .dmg(opens in new tab)
- Windows: Alternative .exe(opens in new tab)
Or visit the downloads page for guided install with automatic platform detection.
After You Install: Set Up Integrations
Read the Meetily developer docs
Once Meetily Pro 1.11.0 is installed, the Meetily developer docs(opens in new tab) walk you through everything in this release: turning on the Automation API, connecting Claude, Codex, Cursor or Windsurf, allowing the command-line tool, creating keys and subscribing to webhooks.
1. Turn on the Automation API
Open Settings > PRO and turn on Integrations. A new Integrations tab appears with the Automation API switch at the top. That switch is the one on/off for every assistant and key: turning it off closes the connections, while recording and processing on your computer keep going.

2. Connect your AI assistant and choose what it can do
Click Connect next to Claude Desktop, Claude Code, Codex, Cursor or Windsurf and choose what it may do. New connections start read-only; recording and editing summaries are separate switches, and no assistant can delete meetings through Meetily. Then turn on the assistant's Allow switch and restart the assistant so it loads the Meetily tools. VS Code and other MCP clients can be added by hand.

In this example, Record and Write are switched on. A new connection starts with only Read.
3. Allow the command-line tool
Under Apps & scripts, turn on Allow the CLI on this computer. That gives the built-in meetily-pro tool read-only access to your meetings and recording notifications. For a script that 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.

For API keys, webhooks, events and more examples, continue in the Meetily developer docs(opens in new tab). For ideas on what to build, see Meetily workflows.
Frequently Asked Questions
Frequently Asked Questions
Ready to try Meetily?
Join 599,000+ users who use Meetily for private meeting transcription. No bots, privacy first. Community Edition free.
Star on GitHub (31K+) · Open source & self-hostable