Resources · Claude connector

Claude Minutes Conversation Memory connectorWhat Claude can do with the meetings recorded on your machine.

The Claude Minutes Conversation Memory connector exposes 34 tools. 20 read your meetings, memos and insights, 12 write: recording, dictation, live transcripts, notes, summaries. 2 have no active description. Everything stays on your computer unless you send it out.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes when Claude can recall your meetings

Minutes records meetings, voice memos and dictation, transcribes them on your own machine and keeps the result as plain markdown files. With this extension, Claude can start a recording, search what was said last week and pull out decisions and commitments. The publisher's sheet says your audio is never uploaded, and meeting text only leaves the device when you explicitly send it.

Capture the meeting without a cloud service. When a meeting starts, start_recording begins capturing from your default microphone; at the end, stop_recording stops and processes it locally.

Find what was decided. Later, search_meetings looks through transcripts and voice memos, get_meeting opens the right one, and get_meeting_insights lists the decisions, commitments and questions extracted from it.

Keep promises in view. Before you meet someone, track_commitments lists open and stale commitments, filtered by person.

What Claude will not do. Restricted meetings stay out of its results by default; reaching them needs a trusted launch policy, a request on each call and a durable audit record. Two tools on the sheet are described by Minutes as unavailable compatibility names. Existing meeting files cannot be edited through the note tool. And nothing runs by itself: Claude acts while you talk to it. Scheduled jobs belong to automation tools, listed from the Integrations hub.

Vocabulary

Five words in one minute

The vocabulary you will meet when adding Minutes to Claude.

Connector
The link you set up once between Claude and a tool you already use, so Claude can work with it while it answers you.
Tool
One named thing a connector lets Claude do. Claude picks the ones it needs as it replies; the directory sheet lists all 34 by name.
Authorization
The step where you grant the access Claude will use. For a local extension like this one, it happens on your own computer.
Approval
The confirmation Claude waits for before it goes ahead with something that changes your data, shown in the conversation at the right time.
MCP
The shared standard connectors are built on: it is what lets an assistant like Claude talk to software outside it.
Connect

Add Minutes to Claude in three steps

  1. 01

    Find Minutes in your settings

    In Claude Desktop, open Customize, then Connectors, and look for Minutes Conversation Memory. On a Team or Enterprise workspace, an Owner or Primary Owner enables a connector before members can install it.

  2. 02

    Start the installation

    Click Connect on its row and follow what appears on screen. If the extension ever stops responding, use Disconnect, then add it again from the same row.

  3. 03

    Read before you allow

    If a permission screen appears, read it before you confirm: it describes what the access covers, not what Claude will do in every chat. You can remove the extension later from the same place.

Tools

The 34 tools, grouped by what they do

Minutes Conversation Memory gives Claude 34 tools: 20 that read your account, 12 that change something in it, and 2 no official source describes.

Three groups: what Claude reads, what it starts or adds, and two names with no active capability. Tool names stay in English, as Claude shows them.

  • 20 read
  • 12 write
  • 2 not documented

What Claude reads (20)

20 tools

Twenty tools that search, open and summarize what Minutes already holds.

get_status

Tells Claude whether a recording is currently in progress, a quick check before starting another one or asking about the last meeting. It only reports the recording state and starts or stops nothing.

When it helps
you are not sure whether a recording is still running.

Sourcegithub.com · October 1, 2026 ↗

list_processing_jobs

Lists the background processing jobs for recent recordings, so Claude can say which transcripts are done and which are still being worked on.

When it helps
a recent transcript is not available yet and you want to know whether it is still being processed.

Sourcegithub.com · October 1, 2026 ↗

list_meetings

Returns your recent normal meetings and voice memos. Restricted items are left out unless an explicit, logged override is both enabled and requested. Restricted items need all of the override conditions before they appear.

When it helps
you want the list of recent meetings and memos before choosing one.

Sourcegithub.com · October 1, 2026 ↗

search_meetings

Looks through the transcripts of normal meetings and your voice memos for a topic or phrase, with restricted items excluded under the same override rule.

When it helps
a figure or a phrase came up in a meeting and you no longer know which one.
Watch out
a restricted meeting will simply not show up in the results.

Sourcegithub.com · October 1, 2026 ↗

get_meeting

Retrieves the transcript of one normal meeting. For a restricted meeting, Minutes returns a content-free stub instead, unless the logged override is enabled and requested.

When it helps
the search found the right meeting and you want its full transcript.

Sourcegithub.com · October 1, 2026 ↗

activity_summary

Summarizes the desktop context bound to one exact normal meeting, so Claude can relay what the desktop context recorded around that conversation. Its scope is one exact meeting source, not your whole desktop history.

When it helps
you want a summary of the desktop context recorded around one meeting.

Sourcegithub.com · October 1, 2026 ↗

search_context

Searches the desktop-context events tied to one exact normal meeting, rather than across everything you did that day. The search stays bound to that single meeting source.

When it helps
you are looking for one desktop-context event from a given meeting, not from your whole day.

Sourcegithub.com · October 1, 2026 ↗

get_moment

Shows the local desktop-context rewind bound to one exact normal meeting, a way back to what was happening at a given point of that conversation.

When it helps
you want to go back to the desktop context of a given meeting.

Sourcegithub.com · October 1, 2026 ↗

get_screen_context

Brings back bounded, verified screenshots tied to one exact normal meeting, so Claude can refer to what was visible rather than guess from the transcript.

When it helps
the transcript refers to something on screen and you want the verified screenshots of that meeting.

Sourcegithub.com · October 1, 2026 ↗

consistency_report

Flags conflicting decisions and stale commitments across your meetings, the kind of drift that is hard to notice from one conversation to the next. It flags the problems and leaves every decision and commitment as recorded.

When it helps
you suspect two meetings ended on decisions that contradict each other.

Sourcegithub.com · October 1, 2026 ↗

get_person_profile

Builds a profile of someone from policy-authorized meetings, within the corpus bounds Minutes supports, so Claude can brief you on past exchanges with them.

When it helps
you are about to meet someone and want a profile built from your authorized meetings with them.

Sourcegithub.com · October 1, 2026 ↗

research_topic

Researches one topic across policy-authorized meetings, within supported bounds, and gathers what was said about it over time. Restricted meetings stay outside those authorized sources by default.

When it helps
a topic keeps coming back and you want what was said about it across meetings.

Sourcegithub.com · October 1, 2026 ↗

track_commitments

Lists open and stale commitments from your meetings, optionally filtered by person, so promises made out loud do not quietly disappear. Without the person filter, every open or stale commitment comes back.

When it helps
you want to see the commitments still open with one person.

Sourcegithub.com · October 1, 2026 ↗

relationship_map

Ranks relationships from a bounded, process-private, policy-safe graph projection, giving Claude a sense of who you talk to most. It ranks relationships and leaves your meetings as they are.

When it helps
you want to see which relationships stand out across your meetings.

Sourcegithub.com · October 1, 2026 ↗

list_voices

Lists the voice profiles enrolled for speaker identification, so Claude knows which speakers Minutes can recognize in transcripts. Confirming a speaker is not something Claude can do: Minutes keeps that in its app or command line.

When it helps
a transcript does not name a speaker and you want to check which voices are enrolled.

Sourcegithub.com · October 1, 2026 ↗

get_meeting_insights

Queries decisions, commitments and questions extracted from meetings. Minutes re-verifies each source meeting against the live sensitivity policy before release and reports withheld records as a partial view.

When it helps
you need the decisions taken across several meetings, each with its source meeting.

Sourcegithub.com · October 1, 2026 ↗

read_live_transcript

Reads utterances from the active live transcript, with an optional cursor or time window, so Claude can catch up on the latest part of the conversation.

When it helps
you want to catch up on the latest part of a meeting still in progress.

Sourcegithub.com · October 1, 2026 ↗

copilot_status

Reads the current copilot session and the health of its provider, so Claude can say whether the copilot is running properly. The information comes from the copilot's command-line status surface.

When it helps
nudges have stopped arriving and you want to know whether the session is healthy.

Sourcegithub.com · October 1, 2026 ↗

read_copilot_nudges

Reads the nudges the copilot produced, step by step through a cursor or a time window, so they can be reviewed afterwards. It reads nudges already observed and does not start the copilot.

When it helps
after a meeting, you want to go back over the nudges the copilot produced.

Sourcegithub.com · October 1, 2026 ↗

knowledge_status

Shows the current state of the knowledge base: its configuration, adapter, people count and log entries. That knowledge base is the one ingest_meeting feeds with person profiles, a log and an index.

When it helps
you want to check the configuration and contents of the knowledge base.

Sourcegithub.com · October 1, 2026 ↗

What Claude starts or adds (12)

12 tools

Twelve tools that record, dictate, transcribe live, annotate or rebuild summaries. No source describes a confirmation specific to them, so the general rule below applies.

start_recording

Approval: see the rule

Begins capturing audio from your computer's default input device, so a meeting or a thought gets recorded without opening the Minutes app yourself.

What Claude asks for
no source describes a confirmation for this tool; Claude's general approval rule covers it.
When it helps
a meeting is about to start and you want it captured on your machine.

Sourcegithub.com · October 1, 2026 ↗

stop_recording

Approval: see the rule

Ends the recording in progress and hands it over for processing on your machine, the step that turns raw audio into a transcript.

What Claude asks for
nothing specific is documented here, so the default rule from the approvals section applies.
When it helps
the meeting is over and you want the recording processed into a transcript.

Sourcegithub.com · October 1, 2026 ↗

process_audio

Approval: see the rule

On macOS and Linux, processes bounded WAV audio from your inbox or Downloads folder. Compressed or private containers, and Windows, fail closed without reading the audio.

What Claude asks for
the sources stay silent on a prompt here; the general rule is what applies.
When it helps
a WAV file sits in your inbox or Downloads folder and you want it processed.

Sourcegithub.com · October 1, 2026 ↗

add_note

Approval: see the rule

Adds a note with a timestamp to the recording that is currently running. Minutes states that existing meeting files cannot be edited through this tool.

What Claude asks for
no dedicated confirmation is documented; see the approvals section.
When it helps
during a recording, you want to mark a moment with a note.

Sourcegithub.com · October 1, 2026 ↗

start_dictation

Approval: see the rule

Turns on dictation mode, sending your speech to the clipboard and to daily notes.

What Claude asks for
Minutes documents no prompt for this tool, so Claude's default approval behavior governs it.
When it helps
you would rather speak a text than type it.

Sourcegithub.com · October 1, 2026 ↗

stop_dictation

Approval: see the rule

Switches dictation mode off, so what you say stops going to the clipboard and daily notes.

What Claude asks for
undocumented for this tool specifically; the rule in the approvals section is the reference.
When it helps
you are done dictating and want your speech to stop going to the clipboard.

Sourcegithub.com · October 1, 2026 ↗

start_live_transcript

Approval: see the rule

Opens a live transcript session for real-time transcription of the meeting under way.

What Claude asks for
no confirmation tied to this tool appears in any source; the approvals section explains what governs it.
When it helps
a meeting is under way and you want it transcribed in real time.

Sourcegithub.com · October 1, 2026 ↗

start_copilot

Approval: see the rule

Launches the independent real-time copilot for a goal you set and observes its stream of nudges.

What Claude asks for
the documentation names no prompt; Claude's default rule applies.
When it helps
you have a goal for a meeting and want the copilot's nudges during it.

Sourcegithub.com · October 1, 2026 ↗

stop_copilot

Approval: see the rule

Ends the active real-time copilot without touching the recording or the live transcription, which keep running.

What Claude asks for
nothing beyond the general approval behavior is documented for it.
When it helps
you no longer need nudges but the recording must keep running.

Sourcegithub.com · October 1, 2026 ↗

ingest_meeting

Approval: see the rule

Extracts facts from a meeting and adds them to the knowledge base: person profiles, log and index.

What Claude asks for
Minutes describes no specific prompt here; rely on the general rule.
When it helps
a meeting just ended and you want its facts added to the knowledge base.

Sourcegithub.com · October 1, 2026 ↗

resummarize_meeting

Approval: see the rule

Re-runs the AI pass on a meeting or memo you edited, previewing the result by default and keeping your own edits.

What Claude asks for
there is no documented confirmation beyond the default rule, though the preview comes first.
When it helps
you corrected a transcript and want the summary to reflect your edits.

Sourcegithub.com · October 1, 2026 ↗

add_agent_annotation

Approval: see the rule

Appends attributed commentary from the agent as a separate event, never altering the meeting markdown or its frontmatter. It is gated by an allowlist file on your machine.

What Claude asks for
no source mentions a prompt; the approvals section applies.
When it helps
you want Claude's commentary kept next to a meeting without touching the original record.

Sourcegithub.com · October 1, 2026 ↗

Not documented as active (2)

2 tools

These two names are on the sheet, but no source describes an active capability for them: Minutes calls them compatibility names only.

confirm_speaker

No source describes an active capability behind this name. The publisher's own wording calls it a compatibility name only and points to the Minutes app or a human command line instead.

Watch out
the general approval rule still covers it.

get_agent_annotations

The sheet lists this name, but no source documents a working capability behind it. Minutes explains it is unavailable because an annotation's pointer and body are both supplied by its author. Minutes adds that revalidating the pointer cannot bound what the body discloses.

Watch out
the general approval rule covers it.
Approvals

What Claude asks before acting

By default, Claude stops and asks before every action it takes for you. Minutes adds its own gate: restricted meetings stay out of agent results unless a logged override is in place.

On Team and Enterprise, workspace owners decide whether members may let some actions through without a prompt. They can also limit what any connector may do for the whole organization, keeping reads and closing writes for example, and nobody overrides that from a personal account. Claude works with the access you gave it and nothing more. The official per-tool label, read-only versus write and delete, only appears inside a connected account's settings.

Plans

Which plans include it

None of the 819 sheets in the official directory shows plan availability. Connector by connector, that answer is not published anywhere.

The general rule is published: desktop extensions install on Claude Desktop, while remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector before members can use it. The sheet lists Claude Desktop and Claude Code for this extension. For the current state on your account, check its sheet in the official directory.

Limits

Where this extension stops

A connector is not an automation. Claude calls these tools while it answers you; nothing starts on its own when a meeting begins.

Only its publisher documents this extension: Claude's help center has no page for it, so the limits below come from the directory sheet and the extension manifest. The tool list is an observed floor, not a guarantee. The verification badge is not a security audit, and Anthropic writes on every sheet that it does not choose a publisher's tools. Here that matters, since the extension listens to your microphone. For scheduled workflows, see the Integrations hub.

Need help

Need help connecting Minutes Conversation Memory to Claude?

A person reads every message.

FAQ

Questions about the Claude Minutes Conversation Memory connector

01What can the Claude Minutes Conversation Memory connector do?
It lets Claude work with the meetings, voice memos and dictation that Minutes records and transcribes on your own computer. Claude can start and stop recordings, search and open transcripts, pull decisions, commitments and questions, profile a person or a topic across meetings, follow a live transcript, run a real-time copilot and feed a local knowledge base. Of the 34 tools on the sheet, two are described by the publisher as unavailable compatibility names.
02Can Claude record, change or delete my meetings?
Claude can start and stop recordings, dictation, live transcripts and the copilot, add a timestamped note to the running recording, rebuild a summary with a preview first, feed the knowledge base and append an agent annotation. Minutes is explicit about the edges: existing meeting files cannot be edited through the note tool, annotations never touch the meeting markdown, and no tool on the sheet is described as deleting a meeting. Speaker corrections stay in the Minutes app.
03Does Claude ask before starting a recording?
By default, Claude asks for confirmation before any action it takes for you. No source describes a confirmation specific to start_recording or the other write tools, so that default rule is what covers them. Minutes adds its own safeguards elsewhere: summaries are previewed by default, annotations sit behind an allowlist, and restricted meetings need a logged override. On Team and Enterprise, owners decide which actions members may let through without a prompt.
04Which Claude plans can use Minutes?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets displays it. The general rule says desktop extensions install on Claude Desktop, remote connectors are open to all users across Claude's apps, and on Team and Enterprise an Owner or Primary Owner enables a connector before members use it. This sheet lists Claude Desktop and Claude Code. The directory sheet shows the current state for your account.
05Does Claude see every meeting I recorded?
Not by default. Restricted meetings are excluded from agent results, and opening one returns a content-free stub. Reaching them takes a trusted launch policy, a per-call request and a durable audit record. Insights are released only after their source meeting is re-checked against the live sensitivity policy, and withheld records are reported as a partial view, so Claude can tell you when part of the answer is missing. Without those three conditions, restricted meetings stay excluded.
06Does my meeting audio leave my computer?
According to the publisher's sheet, no. Minutes never uploads your audio, and transcription runs on your own machine. Meeting text leaves the device only when you explicitly send policy-authorized context to a connected cloud agent or summarizer, which includes Claude when you ask it about a meeting. Restricted meetings, for their part, are excluded from agent results by default. Recording, transcription and the markdown files in your meetings folder all stay on your own machine.
07Claude or an automation tool for meeting notes?
They do different jobs, so choose by use. Claude with this extension works in the moment: record this call, find what we decided on pricing, list the commitments made to one person. An automation tool runs on a schedule or on events, for example sending a summary to a channel after every meeting, which this extension never does by itself. For recall and preparation in conversation, Claude fits; for recurring distribution, automation.