Narrated screen recordings into agent-ready data: local transcript, keyframes, OCR, wall-clock.
Talkthrough MCP server exists for a simple reason — assistants are far more useful when they can act on Talkthrough directly instead of describing what you should do. Narrated screen recordings into agent-ready data: local transcript, keyframes, OCR, wall-clock.
Give Claude Code or Codex a narrated .mov/.mp4 — talkthrough turns it into searchable transcript, exact frames, OCR and wall-clock timestamps, locally — so your agent writes an evidence-backed issue draft or investigates the fix.
The server ships on PyPI as args, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Once Talkthrough is connected, these are the calls the assistant has available:
Prompt — Workflowbug — One recording → evidence-backed GitHub issue draft (silent, narration-free recordings work too)triage-recording — Narrated screencast → precise findings JSON (bug/feature/question routing, frame evidence)spec-from-workshop — Recorded workshop → structured spec with quoted decisions and open questionsbacklog-from-demo — Product demo → prioritized backlog with timestamped evidencemeeting-actions — Meeting audio → action items, decisions, open questionscorrelate-with-logs — Recording remarks ↔ system logs via wall-clock windowsThis sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Talkthrough's toolset — Prompt, bug, triage-recording and 4 more — is a fair guide to whether it matches your workflow. It is maintained by korovin-aa97; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Talkthrough's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Prompt | Workflow |
| bug | One recording → evidence-backed GitHub issue draft (silent, narration-free recordings work too) |
| triage-recording | Narrated screencast → precise findings JSON (bug/feature/question routing, frame evidence) |
| spec-from-workshop | Recorded workshop → structured spec with quoted decisions and open questions |
| backlog-from-demo | Product demo → prioritized backlog with timestamped evidence |
| meeting-actions | Meeting audio → action items, decisions, open questions |
| correlate-with-logs | Recording remarks ↔ system logs via wall-clock windows |
{
"mcpServers": {
"talkthrough": {
"command": "uvx",
"args": ["args"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.