Build a Weekly Meeting Digest with MCP in 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 close to a fifth 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 the Pro subscription; 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
• Meetly Pro subscription (the MCP connector is a Pro feature)
• 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 directly 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, so Claude asks for exactly the meetings it needs, each time, instead of holding a copy.

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.