SkillAgentSearch skills...

meetscribe

Record, transcribe, and extract action items from meetings inside Claude Code. Bring your own API key. macOS, Node 18+.

Install / Use

claude mcp add qa-aman -- npx -y github:qa-aman/meetscribe

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

74/100

Supported Platforms

Claude Code
Claude Desktop

Tags

Our assessment of meetscribe

meetscribe scores 74/100 on our quality scale, 1053rd of 1,995 Development & Engineering skills we index.

Its MCP Server is 7.0 KB long, well organised into 26 sections with 12 code examples: a thorough specification that gives an agent plenty to work with.

It has 3 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
29/30
Structure
20/20
Description
12/15
Adoption
3/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-09-12 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 90/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-25. Automated pattern scan on 2026-09-25. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

meetscribe compared with similar skills

All 4 of these similar skills score higher than meetscribe; compare them before choosing.

SkillScoreStarsUpdatedFormat
meetscribe (this skill)by qa-aman7434mo agoMCP Server
Agent-Reachby Panniantong10085.5k10d agoCLAUDE.md
headroomby headroomlabs-ai10073.8ktodayCLAUDE.md
rufloby ruvnet10073.3k1d agoCLAUDE.md
CowAgentby zhayujie10047.1ktodayCLAUDE.md

Frequently asked questions

How do I install meetscribe?
Run claude mcp add qa-aman -- npx -y github:qa-aman/meetscribe. The install tabs above show the steps for each supported agent.
Which AI agents does meetscribe work with?
It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
Is meetscribe safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 90/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is meetscribe still maintained?
The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

MeetScribe

License: MIT Node Platform: macOS

Record, transcribe, and extract action items from meetings - directly inside Claude Code. No subscriptions, no separate app. Bring your own API key and get structured meeting notes in seconds.

Think of it as your own Granola, running as a Claude Code plugin.

What it does

  1. Record - captures mic audio (+ system audio if BlackHole is installed) via ffmpeg
  2. Transcribe - streams to Deepgram in real time, or batch-transcribes with AssemblyAI or OpenAI Whisper
  3. Extract - MeetScribe pulls out action items, decisions, blockers, and a summary
  4. Save - writes everything to a clean markdown file in your project

One command to start, one to stop. Everything else is automatic.

Quick start

Prerequisites

  • macOS (recording uses ffmpeg's avfoundation; other platforms can still use meeting_import)
  • Node.js 18+
  • ffmpeg (brew install ffmpeg)
  • A transcription API key (any one of the three providers)

Install

# Clone the plugin
git clone https://github.com/qa-aman/meetscribe.git
cd meetscribe
npm install

# Add your API key
cp .env.example .env
# Edit .env and add your key

Connect to Claude Code

Option A - all projects (recommended). From the cloned folder, run:

npm run connect

That's it - no paths to figure out. It registers MeetScribe at user scope so it works in every project. Restart Claude Code, then verify with /mcp - meetscribe should be listed as connected.

Under the hood it runs:

claude mcp add meetscribe --scope user -- node "$(pwd)/src/index.js"

Option B - single project. Add to that project's .mcp.json with the absolute path:

{
  "mcpServers": {
    "meetscribe": {
      "command": "node",
      "args": ["/absolute/path/to/meetscribe/src/index.js"]
    }
  }
}

Either way, meeting notes always save into the project you run it from (<project>/meetscribe/), and the API key is read from the MeetScribe install directory - no per-project key setup.

Use it

You:     meeting_setup              # check prerequisites
You:     meeting_start "Sprint 14"  # start recording
         ... have your meeting ...
You:     meeting_stop               # stop, transcribe, extract, save

Your notes land in meetscribe/YYYY-MM-DD_Sprint-14/.

Tools

| Tool | What it does | |------|-------------| | meeting_setup | Check prerequisites (ffmpeg, API keys, config) | | meeting_start | Start recording with a title | | meeting_stop | Stop recording and run the full pipeline | | meeting_import | Import an existing audio or transcript file | | meeting_save | Save extracted notes (called automatically) | | meeting_list | List all past meetings | | meeting_config | View current configuration |

Transcription providers

| Provider | Free tier | Speaker labels | Streaming | Languages | |----------|-----------|---------------|-----------|-----------| | Deepgram (default) | $200 credit | Yes | Yes (live) | 60+ | | AssemblyAI | $50 credit | Yes | No (batch) | 6 | | OpenAI Whisper | None (pay-as-you-go) | No | No (batch) | 50+ |

Switch providers in meetscribe/config.yaml:

provider: assemblyai    # deepgram | assemblyai | whisper

Streaming vs batch

With Deepgram (the default), MeetScribe streams audio over WebSocket and writes the transcript in real time as you speak. meeting_stop returns extraction-ready text instantly.

For AssemblyAI and Whisper, audio is uploaded and transcribed after meeting_stop (batch mode). Streaming auto-falls-back to batch if the WebSocket connection fails.

Disable streaming explicitly in config.yaml:

streaming: false

Multi-language support

Set the language field in config.yaml:

language: en          # ISO code: en, hi, es, fr, de, ja, ...
# or
language: multi       # Deepgram auto-detects language per utterance

Import existing recordings

Already have an audio file or transcript? Import it directly:

meeting_import '/path/to/recording.m4a'
meeting_import '/path/to/transcript.txt'

Supported audio formats: .m4a, .mp3, .wav, .ogg, .flac, .aac Supported transcript formats: .txt, .srt, .vtt

Speaker mapping

Create a team.md file in your project root with your team members:

# Team

- Alice Chen - Engineering Lead
- Bob Park - Backend Developer
- Carol Liu - Product Manager

MeetScribe will map "Speaker 0", "Speaker 1" to real names using context from the conversation (who's addressed by name, who discusses what, role references).

Requirements:

  • Provider must return speaker labels - works with Deepgram and AssemblyAI, automatically skipped for Whisper
  • If team.md doesn't exist, mapping is skipped silently (no error)
  • Configure the path in meetscribe/config.yaml via team_file, or set to null to disable

Customizing extraction

Edit meetscribe/extract.md to change what gets extracted. The default template pulls:

  • Action items (owner, task, deadline)
  • Key decisions
  • Open questions and blockers
  • 3-sentence summary

System audio capture (optional)

To capture all meeting participants (not just your mic):

  1. Install BlackHole: brew install blackhole-2ch
  2. Open Audio MIDI Setup
  3. Create a Multi-Output Device combining your speakers + BlackHole

MeetScribe auto-detects BlackHole and switches to dual-capture mode.

Configuration

All config lives in meetscribe/config.yaml:

provider: deepgram          # deepgram | assemblyai | whisper
language: en                # ISO code, or "multi" for Deepgram auto-detection
streaming: true             # real-time transcription (deepgram only, auto-disabled for whisper/assemblyai)
output_dir: ./meetscribe    # where meeting folders are created
keep_audio: true            # keep audio files after transcription
extraction_prompt: ./meetscribe/extract.md
auto_extract: true          # run extraction automatically on meeting_stop
team_file: ./team.md        # path to team file, or null to skip

Safety features

  • Recordings auto-stop after 4 hours (ffmpeg hard cap)
  • Stale recording state auto-expires after 4h5m
  • Transcription API calls timeout after 5 minutes (10 min for AssemblyAI)
  • Orphaned ffmpeg processes are detected and cleaned up on restart
  • SIGKILL fallback if ffmpeg doesn't respond to graceful shutdown

Output structure

meetscribe/
  config.yaml
  extract.md
  2026-04-15_Sprint-14/
    2026-04-15_sprint-14.md     # final notes
    recording.m4a                # audio file
    transcript.txt               # raw transcript

Feedback

Found a bug? Have an idea? Want to share how you're using it?

  • Issues: https://github.com/qa-aman/meetscribe/issues (bug reports and feature requests use the built-in templates)
  • Email: connect@shipwithai-labs.com
  • GitHub: @qa-aman

License

MIT

Author

Aman Parmar

Related Skills

View on GitHub
GitHub Stars3
CategoryDevelopment
Updated3mo ago
Forks0

Languages

JavaScript

Trust signals

90/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 low1 info