Give Claude a memory of every meeting you've had (without giving anyone else one)

Monday, 8:40. You open Claude and type: “What did we decide about the retention policy last week, and who owns it?” Claude answers with the decision, the owner, the minute someone said “let’s not ship that yet”, and a reference back into the transcript. No bot sat in that call. Nobody at a notetaker company can read it. The audio is still on your phone, where it was recorded.

That is the combination this guide builds: capture on the device, memory in the agent. Most tools give you one or the other. A cloud notetaker gives your agent a memory by sending every conversation to a server you cannot see. A private recorder keeps the audio at home and leaves your agent amnesiac. MCP lets you have both, and the setup takes about ten minutes.

What MCP is, in one paragraph

MCP, the Model Context Protocol, is an open-source standard for connecting AI applications to external systems. The MCP docs call it a USB-C port for AI applications: one plug, many devices. An MCP server exposes tools such as search or fetch; a host such as Claude, Claude Code or Cursor calls them when you ask a question. Under the hood it is JSON-RPC 2.0 messages, nothing exotic.

The plumbing is the boring part. The interesting question is what the server is allowed to hand over, and where that data was before the agent asked. Claude’s own help centre is candid that custom connectors allow you to connect Claude to services that haven’t been verified by Anthropic, so the trust question moves to the server. Which is why it matters what the Meetly server actually holds.

Why “on-device plus MCP” is the sentence nobody else says

You can get MCP from a cloud notetaker, and that is fine as far as it goes. The catch is upstream: the bot joined the call, the audio went to their servers, and their transcript is the thing your agent reads. Meetly turns that around. Recording, transcription and speaker tagging happen on your iPhone, iPad or Mac; audio never leaves your device for capture, transcription, or speaker labels. The connector only ever sees text.

Here is the exact data path, taken from Meetly’s privacy page rather than from a badge. When you turn on agent access, Meetly uploads AES-256-GCM encrypted transcript text, summaries, participants, highlights, action items and meeting metadata to mcp.getmeetly.ai. Recording audio is not included. The encryption key is generated on your device and kept in the iOS Keychain; an authorised request decrypts the minimum needed data in request memory, and the service does not persist or log meeting plaintext. Switch agent access off in Settings and the agent goes back to knowing nothing.

Step	Cloud bots	Meetly + MCP
Capture	A bot joins the call	Your phone or Mac records; no bot joins
Transcription	On the vendor’s servers	On the device (Apple Speech or on-device Whisper, 99 languages)
Speaker tags	Added on the server	Added on the device
Audio	Uploaded for processing	Never leaves the device
What the agent reads	The vendor’s transcript	Encrypted transcript text, decrypted per authorised request
Revoking access	Depends on the vendor	Meetly → Settings → AI Agent Access

Connect Meetly to Claude in five steps

You need the Meetly app with the Pro subscription (agent access is part of it), a Claude account, and about ten minutes. The connector is the same for Claude on the web and Claude Desktop. If you are on Claude’s free plan, note that free users are limited to one custom connector, so this will be the one. The steps below follow Meetly’s setup page.

1. Record something first. Open Meetly, press record, put the phone down. When the meeting ends, the transcript with speaker tags is already on the device.
2. Copy your connection key. In Meetly, open Settings → AI Agent Access.
3. Add the connector. In Claude, open Settings → Connectors, choose Add custom connector, name it “Meetly” and paste https://mcp.getmeetly.ai/mcp.
4. Set Authentication to OAuth and Always required. Claude may suggest that authentication is not needed; change that before you add the connector.
5. Click Connect. Paste the connection key on the Meetly authorisation page, then in a chat open Search and tools and check that Meetly is enabled.

Ask for the Monday digest

Once the connector shows up, the first prompt is the fun one. Ask Claude for a digest of last week’s meetings: decisions, owners, open questions, and where each came from. Claude calls Meetly’s search and fetch tools, reads the speaker-tagged transcripts it needs, and answers with references you can follow back into the source. Below is what that looks like. It is a realistic but fictional sample, not a customer’s meeting.

Prompt: “Digest last week’s meetings. Decisions, owners, open questions. Cite the meeting and the minute.”

Decision	Owner · due	Where it was said
Ship the simplified onboarding in 1.9, not 2.0	Maya · Fri 11 Sep	Product review, Tue 09:12
Retention policy stays at 90 days until legal answers	Jonas · Wed 9 Sep	Product review, Tue 09:41
Drop the calendar-scrape idea; no bot, ever	You · done	Founder sync, Wed 16:05
Feature table goes on the pricing page before the launch post	Priya · Mon 7 Sep	Marketing stand-up, Thu 10:20
Open: who signs off the App Store copy?	unassigned	Product review, Tue 09:55
Open: does the Mac build need its own release notes?	parked	Founder sync, Wed 16:30

Every row points at a minute in a transcript you can open. That is the difference between a recap and a memory: a recap tells you what happened, a memory lets you check.

What to ask next

The digest is only the first trick. After a week you will stop opening the transcript at all and just ask. Because Claude reads the source rather than a recap, it can quote the sentence, name the speaker and give you the minute mark. A few prompts that earn their keep, taken from the workflows Meetly’s site shows for Cursor, ChatGPT and Claude:

• “Create an engineering spec from this brainstorm.” Constraints, trade-offs and decisions intact, ready to hand to your coding agent.
• “Draft the product spec from Tuesday’s review.” Goals, scope, decisions and open questions, with the source still attached.
• “Make a study map and detailed lecture notes from today.” Built from what the speaker covered, not from a generic topic summary.
• “What did the customer object to, in her own words?” A quote, a speaker tag and a timestamp.

The numbers behind the habit

Why bother wiring this up at all? Because meetings are where the information is and where it gets lost. Microsoft’s 2023 Work Trend Index found that the average employee spends 57% of their time communicating in meetings, email and chat, and that 68% of people say they don’t have enough uninterrupted focus time. A 2025 follow-up report adds that 57% of meetings are ad hoc calls without a calendar invite.

An ad hoc call is exactly the one no bot was invited to. A recorder in your pocket does not need an invite: tell the room you are recording, press the button, and the conversation is captured and speaker-tagged on the device. Later it is one search away for the agent you already use. Meetly’s privacy page is blunt that getting consent to record is on you, and we would rather you heard that from us than from a lawyer.

Before you rely on it: the honest caveats

Three things to know before this becomes a habit. First, agent access needs the Pro subscription; the free app records and transcribes on the device, but the connector stays off. Second, once you enable agent access, encrypted transcript text does live on Meetly’s MCP service until you delete it, so “on-device” describes the audio and the transcription, not the connector. Third, whatever the agent receives is then handled under that agent provider’s terms.

Claude’s help centre adds one more. When you add a custom connector, Claude connects to your remote MCP server from Anthropic’s cloud infrastructure, rather than from your local device. That is true of every connector, and it is exactly why the audio staying on your device matters: the worst case is text you chose to share, never the recording.