LabscoMCP early access ↗
pedramaminiMCP SERVER

RewindDB

Search your own Rewind.ai history — meeting transcripts and screen OCR, by time window or keyword.

by pedramamini ↗Session & Transcript RecallCommunity

LABSCO SUMMARY

Your own recall, queryable.

Pairing audio with screen OCR is what makes it more than a transcript search: what was said in a meeting and what was on screen during it are two halves of the same memory, and both are addressable by the same time window.

What it is

A reader for the Rewind.ai SQLite database on your Mac. Rewind captures audio transcripts and screen OCR continuously; this exposes both to an assistant, so a question about a meeting last Tuesday or what was on screen during it becomes a query rather than a scroll through a timeline.

What you get

  • Transcripts — get_transcripts_relative for a period such as 1hour or 1week, get_transcripts_absolute for a specific window such as a 3 PM meeting, and get_transcript_by_id to pull one session's full text after the first call showed a preview
  • search_transcripts — keyword and phrase matches with context snippets across sessions, for finding where a topic came up rather than summarising a known meeting
  • Screen OCR — get_screen_ocr_relative and get_screen_ocr_absolute for everything visible in a period, organised by application and timestamp, and search_screen_ocr for keywords that appeared on screen
  • Application discovery — get_ocr_applications_relative and get_ocr_applications_absolute show which applications were active and how busy, so you can filter OCR content before pulling it
  • get_activity_stats — audio recordings, screen captures and application usage over a period
  • Voice filtering on the CLI side: --speech-source separates your own voice from other speakers, with text, JSON and audio export

Requirements

A Mac running Rewind.ai, since it reads that application's own database. Python 3.6+, then pip install . from a clone. Connection details go in a .env — DB_PATH pointing at the Rewind database and DB_PASSWORD — kept in your project directory or at ~/.rewinddb.env, with --env-file for anywhere else. The MCP server is mcp_stdio.py, which takes the same --env-file argument. Everything it can reach is your own recorded activity, so treat the database path and password like any other credential.

Setup effort

Build from source — git clone https://github.com/pedramamini/RewindMCP.git