- Home
- Resources
- Integrations
- Minutes Conversation Memory
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
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.
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.
Add Minutes to Claude in three steps
- 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.
- 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.
- 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.
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
Tools index
- get_status
- list_processing_jobs
- list_meetings
- search_meetings
- get_meeting
- activity_summary
- search_context
- get_moment
- get_screen_context
- consistency_report
- get_person_profile
- research_topic
- track_commitments
- relationship_map
- list_voices
- get_meeting_insights
- read_live_transcript
- copilot_status
- read_copilot_nudges
- knowledge_status
What Claude reads (20)
20 toolsTwenty 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
What Claude starts or adds (12)
12 toolsTwelve 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 ruleBegins capturing audio from your computer's default input device, so a meeting or a thought gets recorded without opening the Minutes app yourself.
stop_recording
Approval: see the ruleEnds the recording in progress and hands it over for processing on your machine, the step that turns raw audio into a transcript.
process_audio
Approval: see the ruleOn 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.
add_note
Approval: see the ruleAdds a note with a timestamp to the recording that is currently running. Minutes states that existing meeting files cannot be edited through this tool.
start_dictation
Approval: see the ruleTurns on dictation mode, sending your speech to the clipboard and to daily notes.
stop_dictation
Approval: see the ruleSwitches dictation mode off, so what you say stops going to the clipboard and daily notes.
start_live_transcript
Approval: see the ruleOpens a live transcript session for real-time transcription of the meeting under way.
start_copilot
Approval: see the ruleLaunches the independent real-time copilot for a goal you set and observes its stream of nudges.
stop_copilot
Approval: see the ruleEnds the active real-time copilot without touching the recording or the live transcription, which keep running.
ingest_meeting
Approval: see the ruleExtracts facts from a meeting and adds them to the knowledge base: person profiles, log and index.
resummarize_meeting
Approval: see the ruleRe-runs the AI pass on a meeting or memo you edited, previewing the result by default and keeping your own edits.
add_agent_annotation
Approval: see the ruleAppends 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.
Not documented as active (2)
2 toolsThese 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.
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.
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.
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.
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 connecting Minutes Conversation Memory to Claude?
A person reads every message.