Meetly
September 21, 20266 min read

Build a Weekly Meeting Digest with MCP in 10 Minutes

Connect Meetly's MCP server to Claude, ChatGPT, or Cursor and ask your agent for the whole week instead of one meeting. The exact setup, the Friday prompt, a sample digest, and what's happening under the hood.

Connect Meetly's MCP server to Claude, ChatGPT, or Cursor, then ask for the week instead of one meeting. Your agent calls Meetly's list_meetings, search, fetch, and get_transcript tools across every recording and writes a digest of decisions, action items, and open questions in about 10 minutes.

Meetly's MCP connector turns a week of recorded meetings into one digest your agent writes for you. Open Claude, ask for the week instead of one call, and get decisions, action items, and open questions back in about ten minutes, pulled straight from the transcripts through Meetly's own retrieval tools, not from your memory of what people said.

Why the digest never gets written

Interaction workers spend nearly 20 percent of the workweek hunting for information other people already produced, according to McKinsey Global Institute research on workplace collaboration. A week of meetings is exactly that kind of buried information: five separate transcripts, no single place that says what actually got decided, and nobody volunteers to write the recap.

What you need before you start

You need three things already in place: Meetly recording your meetings on iPhone, iPad, or Mac; the MCP connector turned on, which is part of a paid plan; and an MCP-compatible agent (Claude, ChatGPT, or Cursor) with that connector added. If a meeting from the week was never recorded, it won't be in the digest; Meetly can't summarize a conversation it never heard.

  • Meetly recording each meeting you want covered that week
  • A Meetly paid plan (the MCP connector is a paid feature), with your library in your own iCloud
  • Claude, ChatGPT, or Cursor with the Meetly connector added

Step 1: Connect Meetly to your agent

Add Meetly the same way you'd add any other MCP server: open your agent's connector settings, paste in Meetly's connection details from the app, and approve the connection once. From then on your agent can call four tools against your library (list_meetings, search, fetch, and get_transcript) instead of you copying transcripts in by hand.

Step 2: Ask for the week, not one meeting

Most people only ask their agent about the call that just ended, so the agent calls fetch once and stops. For the weekly digest, wait until Friday and ask once: "Pull my meetings from this week and write a digest: decisions, action items, and anything still open." The agent now calls list_meetings for the date range, then get_transcript on each result before it writes anything.

See it work

Here's what came back for one Monday-to-Friday stretch on a Meetly-owned test account: a fictional week, built only to show the shape of the output, not a real client's meetings or a real customer's account. The prompt was the one from Step 2, asked once on a Friday afternoon, against five recorded meetings from that account's library.

What's actually happening under the hood

Your agent isn't storing your meetings anywhere new. Every call runs over the Model Context Protocol, the open standard Anthropic introduced on November 25, 2024 with pre-built connectors for tools like Google Drive, Slack, and GitHub. Meetly's MCP server adds your meeting library to that same list: once you explicitly connect it, it reads your transcripts and summaries from your iCloud through Meetly's service, so Claude asks for exactly the meetings it needs.

Where the ten minutes goes

Most of the ten minutes is you, not the agent: reading the digest, correcting anything it got wrong, and forwarding the parts your team needs; the four retrieval calls themselves take seconds. The one hard limit is recording: a hallway conversation or a call made on someone else's laptop was never captured, so it still needs to be typed up the old way, digest or not.

What next

Turn the connector on before your next Friday, not after. The first digest that actually saves you time is the one covering a week you already lived through. Ask for last week's meetings once, see what your agent misses, and adjust the prompt before you make it a weekly habit.

Meetly is a free download, and core recording and transcription work without an account; the MCP connector is part of a paid plan.

Get started free

FAQ

Do I need a paid Meetly plan for the weekly digest?

Yes. Meetly is a free download, and core recording and on-device transcription in 99 languages work on iPhone, iPad, and Mac without an account, but the MCP connector that lets Claude, ChatGPT, or Cursor call Meetly's retrieval tools is part of a paid plan. Prices change, so check the App Store listing for the current ones. Without the connector, your agent has nothing to connect to: the meetings are still recorded and transcribed on your device, and they stay private on your own devices until you explicitly connect an agent. The digest itself doesn't cost anything extra once the connector is on; it's a prompt, not a separate feature you buy again.

Which agents work with Meetly's MCP connector?

Any MCP-compatible agent can connect, including Claude Desktop, Claude Code, ChatGPT with its MCP plugin enabled, and Cursor. The connection uses the Model Context Protocol, the open standard Anthropic introduced in November 2024 so an agent can call the same four tools (list_meetings, search, fetch, and get_transcript) regardless of which company built the agent. You add Meetly through your agent's own connector settings, the same way you'd add any other MCP server, rather than through a Meetly-specific integration. If your agent supports MCP at all, it can ask for a weekly digest exactly the way Claude does in this guide.

Does the digest include meetings I didn't record?

No. Meetly can only summarize audio it actually captured, so a meeting nobody pressed record for, a hallway conversation, or a call made from a different device without Meetly running simply won't appear, and the agent won't guess at what was said. This is deliberate: Meetly's claims policy rules out invented meetings or fabricated quotes, and the MCP connector inherits that constraint: get_transcript only returns real, timestamped, speaker-tagged transcripts. If a meeting is missing from your digest, the fix is recording next time, not asking the agent to fill the gap from context.

Can my agent see meetings from before I turned on the connector?

Yes, as long as Meetly already recorded and transcribed them and they are in your iCloud library. list_meetings reads your existing library; it doesn't only forward new meetings going forward. That means your first weekly digest can cover a week you've already lived through, which is the fastest way to see whether the output is actually useful before you build a Friday habit around it. Older meetings recorded before you owned an iPhone with Meetly installed, or recorded in an app other than Meetly, aren't in that library and won't show up no matter how the prompt is worded.

What if the digest gets a decision wrong?

Check it against the transcript before you forward it. The agent is reading real transcripts, but summarizing five meetings into a few bullet points is still an interpretation, not a transcript. Ask your agent to call get_transcript again and quote the source line for anything you're unsure about; because Meetly keeps timestamped, speaker-tagged transcripts, it can pull the exact sentence a decision came from rather than paraphrasing twice. Treat the weekly digest as a draft you read in two minutes, not a record you forward unread.