Skip to main content
New in Meetily Pro 1.11.0

Meetily MCP Server, CLI and API

Meetily Pro 1.11.0 includes an official MCP server, a command-line tool and a local API, so Claude Desktop, Claude Code, Codex, Cursor or Windsurf, or your own scripts, can search your meetings, read transcripts and summaries and, if you allow it, start or stop a recording. Meetily records and transcribes on your own Windows or Mac computer with no meeting bot, the API listens only on your computer by default, and nothing is connected until you turn it on.

Start free trialRead the setup docs
  • Official MCP Server
  • meetily-pro CLI
  • Local API + Signed Webhooks
  • Off by Default
  • One-click Connect for Claude, Codex, Cursor and Windsurf
  • Export any meeting as Markdown, text or JSON
  • You choose what each assistant or key may do
  • Included in the 14-day Pro trial

Meetily MCP, answered

Last updated: Reviewed by the Meetily team

What is the Meetily MCP server?

MCP (Model Context Protocol) is the open protocol, introduced by Anthropic in 2024, that AI assistants use to connect to other apps. Meetily Pro 1.11.0 ships an official MCP server inside the app, so an assistant on the same computer can work with your meetings: search across transcripts, list meetings, read a transcript or summary, export a meeting, regenerate a summary, and start or stop a recording. What it may do is up to you: a new connection starts read-only, and recording and editing summaries are separate permissions you switch on for each assistant. Deleting meetings is never available through the MCP server.

Which AI assistants work with Meetily?

Claude Desktop, Claude Code, Codex, Cursor or Windsurf connect in one click from Meetily’s Integrations tab when they are installed on the same computer. Claude Code and Codex also need their own command-line tool installed for Meetily to detect them. Meetily lists VS Code but cannot connect it from the app yet; VS Code and other MCP clients can be added by hand with the setup guide in the meetily-workflows repository.

Step-by-step guides: connect Claude Desktop or Claude Code, and use your meetings in Cursor, Windsurf or Codex.

What can I connect Meetily to besides an AI assistant?

Your own scripts. The meetily-pro command-line tool and the local HTTP API let a script search meetings, export any meeting as Markdown, text or JSON, and start or stop a recording. Webhooks signed with HMAC-SHA256 tell your script the moment a summary is ready or, with the Record permission, a recording ends.

Code language: bash
meetily-pro meetings export <meeting-id> --format md

That is how notes reach Notion, Jira, a CRM or an Obsidian vault: your script does the sending. Meetily has no built-in connectors for those apps. See Meetily workflows for recipes.

Where does my meeting data go when an assistant reads it?

Meetily serves your meetings to the assistant on your own computer; the API listens only there by default. What happens next is up to the assistant: most send what they read to their own AI provider, the same as anything else you ask them. Connect the assistants you already trust with your meeting notes, and check how each AI provider handles your data if you are not sure. Transcription itself always runs locally.

Is this the official Meetily MCP server?

Yes. The MCP server on this page is built into Meetily Pro and maintained by Zackriya Solutions, the team behind Meetily. Community members have also built unofficial MCP connectors for Meetily; those are separate projects that work differently and are not covered here.

How Do I Turn On the Meetily MCP Server?

Three steps in Meetily Pro 1.11.0 or later

1. Turn On Integrations

Open Settings > PRO and turn on Integrations. A new Integrations tab appears with the Automation API switch, the one on/off for every assistant and key.

2. Connect and Choose Permissions

Click Connect next to your assistant and choose what it may do. New connections start read-only. Then turn on its Allow switch.

3. Ask About Your Meetings

Restart the assistant so it loads the Meetily tools, then ask things like "What did we decide last week?" or "List my action items from yesterday."

Meetily Settings, Integrations tab: the Automation API switch turned on, above Connect buttons for Claude Desktop, Claude Code, Codex, Cursor and Windsurf
The Integrations tab: one switch for everything, then Connect.
Meetily's permissions panel for Claude Desktop: Read always on, with separate switches for Record, Write and Delete
New connections start read-only; Record and Write are switched on here as an example.

Full setup guide: Meetily developer docs

What Can You Do With It?

Your assistant and your scripts, working with meetings recorded on your own computer

Ask Across Meetings

Ask your assistant what was decided about the pricing page last week, and it searches every transcript to answer.

Catch Up on a Missed Call

Have your assistant read the summary and pull out what changed for you and what you owe by Friday.

Turn Action Items Into Issues

An assistant with its own Jira, Linear or GitHub access can file the action items from a sprint planning call.

React When a Summary Is Ready

A signed webhook tells your script the moment a summary is ready, so it can export the notes and send them on.

Script Exports and Backups

Export any meeting as Markdown, text or JSON with meetily-pro, from a shell script, cron or your own tools while Meetily is running.

Start Recording From a Chat or Script

Give an assistant or a key the Record permission and it can start or stop a recording for you.

How Does Meetily’s MCP Server Compare?

Some meeting assistants now offer an MCP server. The difference is where your meetings live and what is on by default.

Meetily Pro vs typical cloud meeting assistants
CapabilityMeetily ProTypical cloud meeting assistants
MCP server for AI assistantsYes, built inOffered by some
Where your meetings are served fromYour own computerThe vendor's cloud
Where transcription runsOn your computer (Whisper or Parakeet)The vendor's cloud
Official command-line toolYes (meetily-pro)Varies
Signed webhooksYes (HMAC-SHA256)Offered by some
No-code app connectorsNo, use your own scriptOffered by some
Default stateOff until you turn it onVaries

If you want ready-made connectors with no scripting, a cloud assistant is the better fit. Compare Meetily with Granola, Fireflies and Otter.

Open Source & Privacy-First

Local by Default. Off Until You Say So.

Nothing is connected until you turn it on, and you decide what each assistant or key can do.

Runs on Your Computer

  • The API listens only on this computer by default
  • The MCP server runs next to the assistant, on the same machine
  • Transcription always runs locally

You Decide Who Gets What

  • New connections start read-only; record and write are opt-in
  • Each script gets its own key with only the permissions it needs
  • Webhook destinations wait for your approval in the app

Know Where Data Goes Next

  • An assistant sends what it reads to its own AI provider
  • Summaries use a local model or your own API key
  • One switch turns every assistant and key off

Built on Meetily's On-Device Foundation

The same locally run app trusted by a growing open-source community

31K+
GitHub Stars
599K+
Downloads
99+
Languages Supported
Local
API by Default

Keep Going

Connect Claude

Let Claude Desktop or Claude Code search your meetings and read transcripts and summaries.

Read more →

Cursor, Windsurf and Codex

Bring decisions from design reviews and sprint planning into your editor.

Read more →

Meetily CLI

Search, export and record from scripts with the meetily-pro command-line tool.

Read more →

Meetily Workflows

Recipes for Obsidian, Notion, Jira, GitHub, Slack and your CRM.

Read more →

Developer Docs

Setup, MCP, CLI, webhooks and the API reference on docs.meetily.ai.

Open the docs →

Example Workflows on GitHub

Setup guides with screenshots and example scripts in the meetily-workflows repository.

View on GitHub →

New in this release? Read the Meetily Pro 1.11.0 release notes or browse the meetily-workflows repository.

Meetily MCP Server: Common Questions

The MCP server, the meetily-pro CLI, the local API and webhooks are Meetily Pro features: $10/user/month billed annually, and they are included in the 14-day Pro trial. The free, MIT-licensed Community Edition records and transcribes meetings locally but does not include them.
Claude Desktop, Claude Code, Codex, Cursor or Windsurf, when the assistant is installed on the same computer. Claude Code and Codex also need their own command-line tool installed for Meetily to detect them. VS Code and other assistants that support MCP can be added by hand.
No. The Automation API, the MCP server and webhooks are off until you turn on Integrations in Settings > PRO. By default the API listens only on your own computer, and one switch turns every assistant and key off again.
Yes, if you allow it. A new connection starts read-only; recording and editing summaries are separate permissions you switch on per assistant. No assistant can delete meetings through Meetily's MCP server.
Not with a built-in connector. Meetily Pro gives your own script what it needs: a signed webhook when a summary is ready, and a command-line tool and local API that export any meeting as Markdown, text or JSON. The script then sends the notes wherever you want them.
There is no official SDK. Scripts use the meetily-pro command-line tool or call the local HTTP API directly, which works from any language. The meetily-workflows repository includes small example helpers.
No. The Meetily MCP server runs on your own computer, so it works with assistants installed on the same machine, such as Claude Desktop, Claude Code, Codex, Cursor and Windsurf. A browser-based assistant cannot reach it.
Every webhook is signed with HMAC-SHA256 and carries the signature in the X-Meetily-Signature header. Your script checks it with the signing secret that Meetily shows once, when you add the webhook. The developer docs show the exact steps.

Connect Your AI Assistant to Your Meetings

The MCP server, CLI, API and webhooks are in Meetily Pro: $10/user/month billed annually, with a 14-day trial. Transcription stays on your computer.

Start free trialGet Meetily Pro

✅ Official MCP Server · ✅ Local by Default · ✅ Off Until You Turn It On · ✅ 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