Skip to main content
Meetily Pro 1.11.0 MCP server

Connect Claude to Your Meeting Notes

Meetily Pro's built-in MCP server lets Claude Desktop and Claude Code 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, and you connect Claude in one click from Meetily's Settings, choosing exactly what it may do.

  • Claude Desktop
  • Claude Code
  • One-Click Connect
  • You Set the Permissions
  • Ask Claude about any meeting
  • Reading is always on, everything else is opt-in
  • Transcription stays on your computer
  • Included in the 14-day Pro trial

Claude and Meetily, answered

Last updated: Reviewed by the Meetily team

Can Claude read my meeting notes?

Yes, once you connect it. Meetily Pro 1.11.0 includes an MCP server, the standard way Claude connects to other apps. With it, Claude can search every transcript, list your meetings, read a transcript or summary, and export a meeting. With the Record permission it can also start or stop a recording, and with Write it can edit or regenerate a summary. Meetily still does the recording and transcription on your own computer; Claude reads the results when you ask.

How do I connect Claude Desktop to Meetily?

  1. Update to Meetily Pro 1.11.0 or later. The 14-day trial works.
  2. Open Settings > PRO and turn on Integrations. The Integrations tab appears.
  3. Click Connect next to Claude Desktop and choose what Claude may do. New connections start read-only.
  4. Turn on Claude Desktop’s Allow switch.
  5. Restart Claude Desktop so it loads the Meetily tools, then ask it about a meeting.
Meetily's Claude Desktop panel: Read always on, with separate switches for Record, Write and Delete, and a Connect button
New connections start read-only; Record and Write are switched on here as an example.

How do I connect Claude Code to Meetily?

The same way: when Claude Code is installed on the same computer (Meetily looks for the claude command-line tool), it appears in the Integrations tab with its own Connect button and its own permissions. Turn on its Allow switch, then start a new Claude Code session so it loads the Meetily tools. Claude Code is useful when a meeting decides something about your code, for example “read Monday’s architecture review and list the API changes we agreed.” For manual setup, follow the up-to-date guide in the meetily-workflows repository.

What can I ask Claude about my meetings?

Anything the meetings can answer. A few examples:

  • “What did we decide about the pricing page in Tuesday's product sync?”
  • “List every action item assigned to me in this week's meetings.”
  • “Summarize the customer calls that mentioned SSO.”
  • “Draft a follow-up email from yesterday's call with the Acme team.”
  • “Start recording this meeting as "Design review".”

The last one needs the Record permission.

What does Claude see, and where does it go?

Claude sees the meetings it reads when you ask, through the permissions you chose. Meetily serves them on your own computer, but Claude then sends what it reads to Anthropic, the same as anything else you ask it. If that matters for a meeting, keep that meeting out of the conversation, or read how Anthropic handles your data first. Transcription itself always runs locally.

What if Claude does not see Meetily?

Check that the Automation API switch is on in the Integrations tab and that Claude’s Allow switch is on, then restart Claude. If it still does not work, run the built-in check in a terminal. It confirms Meetily is reachable and your Pro license is active:

Code language: bash
meetily-pro mcp doctor

Three Steps to Connect Claude

In Meetily Pro 1.11.0 or later

1. Turn On Integrations

Settings > PRO > Integrations. The Integrations tab appears with the Automation API switch on.

2. Connect and Allow

Click Connect next to Claude Desktop or Claude Code, choose what it may do, then turn on its Allow switch.

3. Restart and Ask

Restart Claude so it loads the Meetily tools, then ask about any meeting.

Claude and Meetily: Common Questions

Yes. The MCP server that Claude connects to is part of Meetily Pro 1.11.0 and later ($10/user/month billed annually), and it is included in the 14-day Pro trial. The free Community Edition does not include it.
No. The Meetily MCP server runs on your own computer, so it works with Claude Desktop and Claude Code installed on the same machine. Claude in a browser cannot reach it.
No. Meetily's MCP server has no tool for deleting meetings, whatever permissions you set. A new connection starts read-only; recording and editing summaries are separate switches in the Claude panel in Meetily.
Claude sends what it reads from Meetily to Anthropic, the same as anything else you ask it, and Anthropic handles it under its own terms. Meetily transcribes and stores your meetings on your computer; Claude only sees the meetings it reads when you ask.
Check that the Automation API switch is on in the Integrations tab and that Claude's Allow switch is on, then restart Claude Desktop or your Claude Code session. Running meetily-pro mcp doctor in a terminal checks that Meetily is reachable and that your Pro license is active.
Claude loads the Meetily tools when it starts. After you change what Claude may do, restart Claude Desktop or your Claude Code session so it picks up the new permissions.

Ask Claude About Your Next Meeting

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

✅ Claude Desktop · ✅ Claude Code · ✅ Local Transcription · ✅ 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