How to give Claude your meeting notes

Method 1: paste a transcript into Claude

The simplest way is by hand. Get a transcript first, from your meeting app's export or a recorder. Then open Claude, upload the file or paste the text, and ask for what you want: a summary, the action items, a follow-up email. Claude reads plain text, Markdown, .vtt caption files, PDFs, and Word documents.

This works well for a single important meeting. The catch is that it's a fresh upload every time, and Claude has no memory of the last one, so you can't ask a question that spans several meetings.

Method 2: keep your meetings in a folder Claude reads

Claude can read a folder instead of a one-off upload. On the Mac, Claude Desktop reads your meetings in place over MCP, and Claude Code reads files in your filesystem directly. Claude in a browser can't reach your disk, but it can read a folder you sync to Dropbox or Google Drive and connect there.

Now Claude can answer across every meeting in the folder, not just the one you pasted. The missing piece is getting each meeting into the folder as a clean file in the first place, which is still a manual save unless something does it for you.

Method 3: let Peachy write the file and connect it

Peachy is a Mac app that records your meetings, with no bot on the call, and writes each one as a speaker-labeled Markdown file in a folder you choose. Then it connects that folder to Claude over MCP, so Claude reads your meetings in place with no upload and no copy-paste.

Now you can ask across your whole history. With write-back switched on, Claude can also write notes and action items back into the meeting file, in a block you own and can regenerate. Transcription defaults to the cloud for accuracy; an opt-in on-device mode keeps the audio on your Mac and is still labeled experimental while we finish proving it. The files are yours either way, plain Markdown in a folder no Peachy cloud holds.

What to ask Claude once it has your meetings

The point of getting meetings into Claude is the questions you can then ask. A few that work well:

• Summarize this meeting: decisions, action items with owners, and open questions.
• What did I commit to across my meetings this week?
• Prep me for my next call with this client, using what we covered last time.
• Draft the follow-up email from this meeting, in my voice.

Give Claude a template so every write-up matches

If you like your notes in a particular shape, hand Claude the template once and it'll follow it, meeting after meeting. That's the part people miss most when they leave a dedicated notes app: a fixed vendor summary can't bend to your format, but your own agent can. Because your history sits in one folder, each new meeting also makes the next answer better.

Three ways to get meetings into Claude

Frequently asked questions

What is the best way to get meeting notes into Claude?

For one meeting, paste or upload the transcript. For every meeting without the copy-paste, keep your meetings in a folder Claude reads. Peachy writes each meeting to that folder and connects it over MCP, so Claude reads them in place.

Can I give Claude a template for my meeting notes?

Yes. Hand Claude your format once and it follows it every meeting. Unlike a fixed tool summary, your own agent writes to the shape you want, and you can change it any time.

Can Claude read a Zoom or .vtt transcript?

Yes. Claude reads plain text, Markdown, .vtt caption files, PDFs, and Word documents. Peachy writes each meeting as Markdown, the format Claude parses most cleanly.

Does Claude remember my past meetings?

Claude itself doesn't store them, but if your meetings live in a folder it reads, it can answer across all of them. The folder is the memory; Claude reads it fresh each time you ask.

Do I have to paste every meeting by hand?

Only if you want to. Keep your meetings in a folder Claude reads, or let Peachy record and connect them for you, and the per-meeting copy-paste goes away.