# Bluedot and Claude Code: make meeting recordings useful beyond the call

Follow the Apple Watch-to-MCP route, then check the information behind questions and emailed summaries.

[HTML](https://lukejbyrne.com/library/guides/zpffmtenh2q/)
Content language: en
Author: Luke Byrne
Video published: 2026-05-27
Guide published: 2026-11-02

[Watch the video](https://www.youtube.com/watch?v=zpfFmtENh2Q)
Video language: English

## Record and check the source meeting

The 27 May 2026 description connects an Apple Watch recording workflow with Bluedot’s meeting archive and MCP server. The aim is searchable context for Claude or Claude Code, not simply another audio file. Begin with one meeting whose content you can recognise before asking questions across an entire history.

1. Use the retained Bluedot link: https://bluedothq.com?referralToken=69a6f3a069ecc93de30802e4-69a6f396834df820cb7b73be.
2. Follow the Apple Watch recording segment at 0:52 and the sync segment at 2:16.
3. Check that the intended meeting appears in Bluedot and inspect its available content before treating it as complete context.

## Connect MCP and ask a bounded question

The connection sequence starts at 4:42, followed by meeting questions at 6:14. A successful connection and a correct answer are separate checks. Start with a question you can verify from the meeting, then expand to themes or decisions across several recordings.

1. Follow the demonstrated Bluedot-to-Claude MCP setup with the client you intend to use.
2. Ask about one known decision, specifying the meeting or time period.
3. Compare the answer with the underlying meeting material; keep missing details distinct from conclusions inferred by the assistant.

## Review a daily routine before relying on email

At 7:57 Luke builds a daily meeting-summary routine; Gmail delivery follows at 12:12. Define what the summary should cover and where it should go before adding recurrence. The described demonstration does not establish that later unattended runs will always retrieve every meeting or deliver successfully.

1. Specify the date window, desired takeaways and intended email destination.
2. Run a small summary check and compare it with the meetings included in that window.
3. Inspect the actual email and its recipient, then check later run results rather than assuming a saved routine is working.

## The takeaway

A useful meeting assistant preserves a checkable path from recorded conversation to answer and delivered summary.

## Workflow resources

- [bluedothq.com](https://bluedothq.com?referralToken=69a6f3a069ecc93de30802e4-69a6f396834df820cb7b73be)

## Chapters

- [0:00 Claude Code in every meeting](https://www.youtube.com/watch?v=zpfFmtENh2Q&t=0s)
- [0:52 Record meetings from Apple Watch](https://www.youtube.com/watch?v=zpfFmtENh2Q&t=52s)
- [2:16 Sync meetings into Bluedot](https://www.youtube.com/watch?v=zpfFmtENh2Q&t=136s)
- [4:42 Connect Bluedot to Claude with MCP](https://www.youtube.com/watch?v=zpfFmtENh2Q&t=282s)
- [6:14 Ask Claude about your meetings](https://www.youtube.com/watch?v=zpfFmtENh2Q&t=374s)
- [7:57 Create a daily meeting summary routine](https://www.youtube.com/watch?v=zpfFmtENh2Q&t=477s)
- [12:12 Email summaries to Gmail](https://www.youtube.com/watch?v=zpfFmtENh2Q&t=732s)
- [15:35 Final result and recap](https://www.youtube.com/watch?v=zpfFmtENh2Q&t=935s)

## Sources and limitations

Prepared 2 November 2026 from this exact published description and chapters. The recording was not independently watched or transcribed and no fresh hands-on test was performed. Steps are editorial adaptations; current setup, availability and offer terms may differ.

[Original video](https://www.youtube.com/watch?v=zpfFmtENh2Q)