Klaket Mcp

io.github.huseyinstifPublished by GitHub account huseyinstifv0.7.1Updated Oct 24, 2026

Let AI agents watch videos: local transcripts, speakers, scenes, chapters and moment search

Overview

AI-generated overview

Lets an assistant ingest a video or audio URL and retrieve timestamped transcripts, speakers, scenes, chapters and in-video moment search results.

What you can do
Klaket turns video and audio into structured, LLM-ready data. The MCP server exposes tools named klaket_ingest, klaket_job_status and klaket_get_result, so an agent can submit a video URL or file, poll the job, and fetch one JSON timeline containing timestamped transcript, speaker labels, scenes with keyframes, on-screen OCR text, chapters and a summary. It also supports searching inside a finished job to find the exact moment a phrase occurs.
When to use it
Use it when an assistant needs to work with video or podcast content: summarizing a talk, extracting the commands a presenter runs, finding where a topic is mentioned, or producing subtitles and chapter data. It is aimed at local or self-hosted deployments rather than a hosted service.
Requirements
Runs as a local stdio process via npx klaket-mcp, so Node.js is needed. It talks to a Klaket API whose base URL comes from KLAKET_API_URL (default that API is normally self-hosted, for example with Docker Compose, and the README says the core pipeline needs no API key and no GPU. KLAKET_API_KEY is only for cloud or authenticated deployments. Desktop only.
Before you install
The server sends the video or audio URL or file to the configured Klaket API, so point KLAKET_API_URL at a deployment you trust; a remote endpoint means your media and its derived transcript leave your machine. KLAKET_API_KEY is a secret and should be supplied through the environment, not committed. Jobs write result files and derived media on the API host. The project is pre-1.0 and moving fast, and a paid hosted cloud API is only planned.

Installation

In SourceWeft

  1. Open Klaket Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

🎬 Klaket

Turn any video into LLM-ready data.

[License: AGPL-3.0] [PRs welcome] [Self-host]

[Klaket demo]

A klaket is a clapperboard — the tool that syncs sound and image on a film set. Klaket syncs video with LLMs.

LLMs read text. The web became readable with scrapers — but video, the largest store of human knowledge, is still locked away. Klaket unlocks it: give it a video URL or file, get back structured, timestamped, LLM-ready data.

bash
pip install klaketklaket ingest "https://youtube.com/watch?v=..." --wait
jsonc
{  "transcript": [    { "start": 14.32, "end": 19.80, "speaker": "S1", "text": "So let's deploy this with docker compose..." }  ],  "scenes": [    { "start": 190.0, "end": 342.5, "keyframes": ["scene_004_01.jpg"] }  ],  "chapters": [...],  "summary": "..."}

Features

  • 📝 Transcript — timestamped speech-to-text in ~100 languages (auto-detected) with word-level timestamps; pick the model per job ("model": "medium")
  • 🎙️ Podcasts too — pass an audio file/URL (mp3, m4a…) and Klaket skips the visual stages, deriving chapters from speech pauses
  • 🗣️ Speaker diarization — who said what (S1/S2/…), local & keyless (sherpa-onnx)
  • 💬 Subtitles — ready-to-use .srt / .vtt files with speaker labels
  • 🎞️ Scene detection — content-aware scene boundaries + keyframes per scene
  • 🔎 On-screen text (OCR) — reads slides, terminals and captions per scene, local & keyless
  • 🧩 One JSON timeline — transcript, scenes, frames and on-screen text aligned on a single timeline
  • 🔌 Works offline, no API key required — the core pipeline uses zero LLM calls
  • 🧠 Pluggable model layer — optional scene descriptions via local VLMs (Ollama) or any OpenAI-compatible endpoint (KLAKET_VLM=off by default)
  • 🤖 MCP server — let coding agents "watch" any video and find moments inside it
  • 🔍 In-video search — GET /v1/jobs/{id}/search?q=… finds the exact moment
  • ▶️ Playground — the dashboard plays the video with a click-to-seek, live-highlighted transcript

SDKs

python
# pip install klaketfrom klaket import Klaketresult = Klaket().process("https://youtube.com/watch?v=...", num_speakers=2)
ts
// npm i klaket-sdkimport { Klaket } from "klaket-sdk";const result = await new Klaket().process("https://youtube.com/watch?v=...");

Give your agent eyes

bash
# Claude Codeclaude mcp add klaket -- npx klaket-mcp   # KLAKET_API_URL defaults to localhost:8484

Then: "Watch https://youtube.com/watch?v=… and summarize the commands the presenter runs." The agent gets klaket_ingest, klaket_job_status and klaket_get_result tools.

Quick start

bash
git clone https://github.com/huseyinstif/klaket.git && cd klaketdocker compose up --build# API on :8484, dashboard on :5180curl -X POST localhost:8484/v1/ingest \  -H "Content-Type: application/json" \  -d '{"url": "https://youtube.com/watch?v=..."}'

That's it — no API keys, no GPUs required. make help lists developer shortcuts (make up, make test, make e2e).

Architecture

client ──► Go API ──► Redis queue ──► Python worker (ffmpeg · faster-whisper · scenedetect)                │                          │            dashboard ◄────────────────────┘   /data/jobs/<id>/result.json
  • apps/api — Go, job orchestration
  • apps/worker — Python, media pipeline
  • apps/dashboard — React dashboard

Self-host vs Cloud

Klaket is open source (AGPL-3.0) and fully self-hostable. A hosted, pay-per-minute cloud API with managed GPUs is planned — join the waitlist (coming soon).

Status

🚧 v0.7 — pre-1.0, moving fast. Star the repo to follow along.

License

AGPL-3.0. SDKs and clients will be MIT.

Contact

Built by Hüseyin Tıntaş — X (@1337stif) · LinkedIn

Source: README.md at commit d1dda7b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.7.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts