OSS Tanbou

Minutes — Local conversation memory that turns meetings into Markdown searchable through MCP

OSS health 96
About these scores

Discovery score is an unbounded weighted, log-compressed index of stars, watchers, forks, and contributors. Growth momentum is its change over the observed period; OSS health is a 0–100 score from available repository recency, Community Health, and release data.

Stars
1,479
Primary language
Rust
License
MIT
Repository last updated
Sep 16, 2026

Overview

Minutes records and transcribes meetings, calls, voice memos, and dictation on-device, storing the results as Markdown under `~/meetings/`. Claude Code, Codex, Cursor, and other clients can search history you authorize through MCP. The latest stable release is v0.26.3 under MIT.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Keep recording, transcription, and primary storage local with Markdown as the durable format

The README states that capture, transcription, and storage run locally and that meeting records are owned as Markdown with structured YAML frontmatter. The project exposes a desktop app, a 58-command CLI, a 34-tool MCP server, and a TypeScript SDK.

Sources: [2]

Query meeting history from Claude Code, Codex, Cursor, and other MCP clients

The documented setup includes commands such as claude mcp add minutes -- npx -y minutes-mcp, exposing local meeting files through MCP. Release v0.26.3 also ships desktop and CLI binaries across supported operating systems.

Sources: [2][3]

For agent-first users who want meeting notes to remain owned local knowledge

It fits users who want to fold meeting records into Markdown vaults or existing knowledge workflows and selectively provide context to an agent rather than storing everything in a hosted meeting workspace.

Local-first storage does not remove cloud-context and recording-consent responsibilities

The README explicitly says that authorized meeting context is sent to a cloud AI assistant or summarizer when one is selected. Recording also requires consent practices appropriate to the jurisdiction and organization; local processing does not automatically satisfy those requirements.

Sources: [2]

Official sources

  1. [1]silverstein/minutes — GitHub repository metadata(2026-09-16)
  2. [2]Minutes — README(2026-09-16)
  3. [3]Minutes v0.26.3 release(2026-09-16)
Supplemental curator note

Recording, transcription, and storage are local, but authorized meeting context can be sent to cloud agents or summarizers. Recording consent is part of the operational model.

Try it in 3 steps

  1. 1

    Install the desktop app

    The desktop app bundles a CLI. Use About Minutes → Set up CLI to add it to PATH.

    brew install --cask silverstein/tap/minutes
  2. 2

    Record and transcribe one meeting

    Record a meeting, stop it, and verify local transcription plus the Markdown output under ~/meetings/.

    minutes record → minutes stop
  3. 3

    Connect an agent through MCP

    This is the Claude Code example. Codex, Cursor, OpenCode, and other supported clients can connect to the same local meeting files using the integration guide.

    claude mcp add minutes -- npx -y minutes-mcp
Check the official README

Growth

Growth trends · Last 30 days

1,479 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
358
Open PRs
8

Development activity is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • agent-skills
  • meetings
  • ai
  • claude
  • mcp
  • meeting-notes
  • privacy
  • rust
  • speech-to-text
  • transcription
  • voice-memo
  • whisper
Stars
1,479
Forks
163
Watchers
2
Open issues
55
Primary language
Rust
License
MIT
Repository last updated
Sep 16, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.