Log inSubmit server
Minutes logo

Minutes

Record, transcribe, and search locally stored meetings, voice memos, dictation, commitments, and meeting context through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Minutes

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "minutes": {
      "command": "npx",
      "args": [
        "-y",
        "minutes-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

minutes MCP server connects MCP clients to locally stored meeting records, voice memos, recordings, and dictation. It can start and stop capture, transcribe and summarize recordings, search transcripts, inspect decisions and commitments, and retrieve bounded desktop context such as activity, rewind data, and verified screenshots. Records are stored as Markdown with YAML frontmatter under `~/meetings/`, while capture, transcription, and storage run locally. Reach for it when an agent needs searchable conversation memory, meeting follow-up, or relationship context without moving the entire meeting library to a hosted service.

Use cases

  • Record and summarize a live meeting
  • Search past meetings for decisions and commitments
  • Review overdue action items by person
  • Compare decisions across a meeting history
  • Retrieve bounded desktop context around a meeting

Key features

  • Local Markdown meeting storage
  • On-device recording and transcription
  • Transcript and voice memo search
  • Commitment and decision tracking
  • Speaker overlays and meeting insights
  • Restricted-record access controls

Tools34

What Minutes lets your agent do. Expand a tool for its parameters.

Verified live~6.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

10/10 checks healthy over the last 45d

What it can do

From the 34 tools this server returned when we ran it; 34 declare their own safety hints.

Makes network requests · 2Read-only tools · 34
Network at startup3 connections
Files written at startup1
Install scriptsNone
npm provenanceSigned build
Package age206 days
Maintainers1

Observed 2026-10-15 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · minutes-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1.6kStargazers on the source repository.
npm downloads3.8kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Tools exposed34Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Minutes works

What minutes does

minutes exposes a local conversation-memory layer through MCP. It works with meeting recordings, voice memos, dictation sessions, transcripts, summaries, decisions, questions, action items, and structured relationship data. The underlying records are Markdown files with YAML frontmatter in ~/meetings/, so they can also be inspected with ordinary Markdown tools such as Obsidian or grep.

Agents can capture a new recording, check its state, stop it for processing, and add timestamped notes while it is active. They can also start and stop dictation, start live transcription, and process a bounded WAV file from the Minutes inbox or Downloads on macOS and Linux. Recording is controlled through explicit tool calls; the server does not listen for a spoken stop command.

How it works

Capture and transcription take place on the device. Stopping a recording sends it through transcription, speaker processing, and summarization. Recent processing jobs can be inspected for states including queued, transcript-ready, needs-review, failed, and completed.

Search and retrieval operate over the local meeting corpus. Tools can list meetings, search transcript text, retrieve a full transcript with speaker overlays, query extracted insights, research a topic, and build a person profile. Commitment tracking surfaces open or stale action items and explicit intent commitments, while consistency reports identify conflicting decisions and stale commitments across meetings.

Desktop-context tools are constrained to one exact normal meeting source. Within that boundary, an agent can request activity summaries, context events, local rewind data, or up to three verified PNG screenshots. Restricted meetings are excluded from normal retrieval and relationship views. Access to restricted records requires an operator launch grant, include_restricted=true, and durable auditing where the tool supports that override.

Setup and configuration

Install the desktop application or standalone CLI with Homebrew, or install the CLI through Cargo. Add the MCP process to an agent with:

Terminal
claude mcp add minutes -- npx -y minutes-mcp

Other MCP clients can run npx minutes-mcp using their standard server configuration. The desktop application includes a CLI setup option. Sample meetings can be created with minutes demo --full, and removed with minutes demo --clean.

Tools and capabilities

  • Record, stop, transcribe, summarize, and monitor meetings.
  • Search meetings and voice memos, list recent records, and retrieve transcripts.
  • Track commitments, compare decisions, research topics, and inspect meeting insights.
  • Build relationship maps and person profiles from policy-authorized meeting data.
  • Start dictation, live transcription, and the independent real-time copilot.
  • Add timestamped recording notes and allow approved agent annotations.
  • Retrieve bounded activity context, rewind data, and verified screenshots.
  • Process supported WAV files from the local inbox or Downloads folder.

Limitations and notes

Restricted meetings are deliberately omitted from ordinary listing, search, profiles, reports, commitment views, and relationship projections. Full restricted access is separately gated and audited. The server does not expose retained meeting-library audio to agent surfaces.

Compressed or private audio containers are not processed by process_audio, and Windows fails closed for that operation without reading the audio. Speaker confirmation must be completed in the Minutes app or a human CLI session; the MCP compatibility tool does not mutate speaker identity. Agent annotations require the agent ID to be allowed in ~/.minutes/agents.allow.

If a cloud assistant or summarizer is selected, only the meeting context authorized for that provider leaves the machine. The MCP copilot tools control or observe the independent Minutes CLI copilot; MCP itself does not generate nudges or run model inference.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Minutes

minutes is an MCP server that connects AI clients to local Minutes meeting files, recordings, voice memos, and dictation. Its main tools record and process audio, search transcripts, retrieve meetings, track commitments, analyze decisions, inspect authorized context, and control live transcription or the independent copilot.

Install the MCP package with `npx` and register it with your client, for example `claude mcp add minutes -- npx -y minutes-mcp`. Install the Minutes desktop app or CLI separately with Homebrew or Cargo when you need local recording, processing, or command-line workflows.

Minutes stores meeting records as Markdown files with YAML frontmatter in `~/meetings/`. Capture, transcription, and storage run locally, while authorized context can be sent to a cloud assistant or summarizer when you choose one.

Restricted meetings are excluded from normal search and retrieval. Tools that support an override require both an operator launch grant and `include_restricted=true`, with the access durably audited; some views, including consistency reports, always exclude restricted meetings.

Yes, minutes works with Cursor through its MCP server configuration. The same local meeting files can be searched from Cursor, including transcripts, voice memos, decisions, commitments, and other policy-authorized meeting data.

Related MCP servers

All in Knowledge & Memory All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMinutes AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/minutes?style=directory)](https://allmcps.com/mcp/minutes)
HTML Embed
<a href="https://allmcps.com/mcp/minutes"><img src="https://allmcps.com/api/badge/minutes?style=directory" alt="Minutes on AllMCPs" /></a>