# Turn recorded all-hands into meeting notes

> Import the recording, generate meeting notes with decisions and action items, archive searchable — done before lunch.

- For: Ops lead
- Category: Team Knowledge & Library Ops
- MCP tools: library_import_youtube_video, run_youtube_tool
- HTML version: https://veridive.com/mcp/use-cases/allhands-meeting-notes

## The problem

The all-hands happened, the recording exists, and now the epistemics get weird: half the company watched live and remembers different emphases; the other half "will watch the recording" (they won't); and the decisions announced in minute thirty-four exist officially nowhere — until someone asks in Slack three weeks later and four people paraphrase four versions.

Meeting notes solve this and nobody writes them for all-hands, because an hour-long town hall is miserable to minute manually. So the company's most important recurring communication produces its least reliable record: vibes, differentially remembered.

## How veridive MCP helps

**library_import_youtube_video** archives each all-hands as it's posted — most companies already upload them unlisted; the import adds the transcript and makes the archive queryable. **run_youtube_tool**'s `meeting-notes` and `action-items` do the miserable part: structured notes with the decisions, announcements and owners extracted, from what was actually said.

Twenty minutes after the recording posts, the canonical record exists: notes for the skimmers, action items for the owners, and a searchable archive for the three-weeks-later Slack question — answered with a link to the minute instead of four paraphrases. The same pipeline covers every recorded recurring meeting the company runs.

## How to run it

1. **Connect veridive MCP** — One-time setup: add the veridive MCP server to Claude, ChatGPT, Cursor or any MCP client and generate your API key. Takes about two minutes.
2. **Import the recording** — Tagged by meeting and date — the archive builds itself meeting by meeting.

   ```
   Import this all-hands recording into my library, tagged 'all-hands <date>': <video URL> — use veridive's library_import_youtube_video.
   ```
3. **Generate the record** — Meeting notes plus extracted action items — the canonical version, twenty minutes after upload.

   ```
   Generate meeting notes and action items from the imported all-hands — decisions, announcements, owners, with timestamps.
   ```
4. **Serve the archive** — The three-weeks-later questions get answered from the record, not from memory.

   ```
   Search my all-hands archive: when did we announce <decision/change>, and what exactly was said? Cite the meeting and minute.
   ```

## Problems it solves

- All-hands decisions live in differential memory and Slack paraphrase wars.
- Nobody minutes an hour-long town hall manually, so the record is vibes.
- 'Watch the recording' is a promise, not a behavior — non-attendees stay unsynced.
- Finding when something was announced means scrubbing months of recordings.

## Why it's valuable

- A canonical record twenty minutes after upload — notes, decisions, owners, timestamps.
- Skimmers read five minutes; the archive answers the retroactive questions with links.
- Action items stop evaporating between the announcement and the follow-up.
- One pipeline covers every recorded recurring meeting, not just all-hands.

## Example prompts

```
Import this all-hands, tagged 'all-hands <date>': <URL> — use veridive's library_import_youtube_video.
```

```
Meeting notes + action items with owners and timestamps.
```

```
When did we announce <change>, and what was said exactly? Cite meeting and minute.
```

## FAQ

**Our all-hands recordings are unlisted — does that work?**

Unlisted YouTube videos import by URL like any other. Private videos don't — for those, the recording needs to be accessible to the importing account's view.

**Which tools produce the notes?**

run_youtube_tool's meeting-notes for the structured record and action-items for the extraction — both running on the imported recording. The archive layer is the library itself.

**Is this a Circleback/meeting-assistant replacement?**

Different layer: meeting assistants live in the call; this processes the published recording and — crucially — builds the searchable archive across months of meetings, which call-time tools don't.

## Related use cases

- [Make your own webinars institutional memory](https://veridive.com/mcp/use-cases/own-webinar-institutional-memory.md) — Import your company's channel; three years of webinars stop being dead links and start answering questions.
- [Send a weekly digest of new library imports](https://veridive.com/mcp/use-cases/weekly-import-digest.md) — List the week's additions and draft a newsletter-style digest — the team reads one email instead of watching six hours.
- [Settle debates by citing the exact minute](https://veridive.com/mcp/use-cases/cite-the-exact-minute.md) — "He never said that" — yes he did, at 23:41, here's the transcript. Team debates end with links, not memories.

---

Part of the veridive MCP use-case library: https://veridive.com/mcp/use-cases.md
Server docs for agents: https://veridive.com/mcp.md