Kuchi

● Active

io.github.KalarisLabs/kuchi

Pick a real launch video as a template, get its frame-by-frame breakdown and plan your own remake.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "kuchi": {
      "url": "https://kuchi.kalarislabs.com/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http kuchi https://kuchi.kalarislabs.com/mcp
VS Code
code --add-mcp '{"name":"kuchi","type":"http","url":"https://kuchi.kalarislabs.com/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Health & Science
Version
1.4.1
Registry
active
Published
11/20/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: Kuchi is maintained, open source, hosted endpoint answering without a key.

Maintained
Active
Last commit 2 days ago (Nov 20, 2026), 0 open issues.
Official registry
Active
Published as io.github.KalarisLabs/kuchi in the official MCP registry, version 1.4.1.
Source
Open source, MIT
Public repository under the MIT licence, 1 stars, 0 forks.
Runs
Hosted by the publisher
Your client talks to kuchi.kalarislabs.com: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 08:08 UTCStatus history & uptime →
● Working336 msprotocol 2025-06-18v1.4.2toolspromptsresources

The endpoint answered the MCP handshake as "Kuchi" and listed 14 tools. Answering since Nov 20, 2026.

Context cost ≈ 7.1k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 14 tools.

Tools (14)

  • kuchi_get_workflow1 param

    Get Kuchi's workflow for turning a reference into the user's own launch video: how to pick a reference, how to analyse each shot from the storyboard sheets, what to ask the user for, how to match timing to the frame, and how to check the result against the reference. Returns Markdown. Pass step to get one step ("find", "study", "plan", "build" or "check") with the rules that hold for all of them, or leave it out for the whole workflow. Read it before a first remake; the other tools return the data each step works on.

    Show parameters
    • stepstring'all' (default) for the whole workflow, or one step: 'find', 'study', 'plan', 'build' or 'check'
  • kuchi_suggest_templates10 params

    Get a short list of Kuchi launch videos for the user to choose their template from, ranked against what they want and what they can supply. Pass what is known: a few words on the product and the feel wanted, preferred styles, theme, pace, aspect ratio, target length and the kinds of asset the user has. All are optional, and they rank rather than filter. Returns up to 6 numbered choices, each with what fits, what differs, what the user would need to supply, a poster and a watch link; a recommended choice; a question to put to the user; and the gallery link, where the user can pick any video and paste its link instead. Use it when the user wants a launch video and has not picked a reference. Use kuchi_search_videos to browse or filter the whole library.

    Show parameters
    • looking_forstringA few words on the product and the feel wanted, e.g. 'AI note-taking app, calm and premium'
    • stylesarrayPreferred motion styles, e.g. ['UI motion', 'Kinetic type']; kuchi_list_filters has the full list
    • themestringPreferred overall brightness
    • pacestringPreferred cutting pace
    • aspect_ratiostringOutput ratio wanted, e.g. '16:9', '1:1', '9:16'
    • target_secondsintegerLength wanted, in seconds
    • available_assetsarrayThe kinds of asset the user can supply. Templates that need something else rank lower and say so.
    • excludearrayVideos the user has already turned down
    • countintegerChoices to return (1-6, default 3)
    • response_formatstring'markdown' (default) for readable text, 'json' for structured data
  • kuchi_search_videos12 params

    Search Kuchi's launch-video references by product type, brand, motion style, format, pace, theme, aspect ratio or length. Returns one page of videos with notes on their motion, measured rhythm (shots, pace, theme), a poster image, a storyboard sheet and a playable Kuchi link. Use kuchi_list_filters for valid filter values, kuchi_get_video for one video's details and kuchi_get_breakdown for its shot list. Examples: - "dark cinematic AI launch" -> query="AI", theme="dark" - "a short vertical teaser" -> aspect_ratio="9:16", max_seconds=20 - "launch videos built from app UI" -> style="UI motion" - "fast-cut launch with charts" -> pace="fast", style="Charts"

    Show parameters
    • querystringKeywords matched against titles, brands, styles, formats, motion notes and shot descriptions
    • stylestringExact motion style, e.g. 'UI motion', 'Kinetic type', 'Device motion'
    • categorystringExact category, e.g. 'AI launch', 'Feature clip', 'Startup launch'
    • formatstringFormat id or name, e.g. 'pastel-ui-cursor-demos'
    • aspect_ratiostringExact ratio, e.g. '16:9', '1:1', '9:16'
    • pacestringMeasured cutting pace: slow is under 1.5 shot changes per 10 s, rapid is 7 or more
    • themestringMeasured overall brightness
    • max_secondsnumberOnly videos at most this long
    • sortstring'relevance' (default) or 'newest'
    • limitintegerVideos per page (1-20, default 6)
    • offsetintegerVideos to skip, for pagination
    • response_formatstring'markdown' (default) for readable text, 'json' for structured data
  • kuchi_get_video2 params

    Get one Kuchi reference by id, slug, Kuchi link or X post URL: playable video file, poster, storyboard sheet, length, size, aspect ratio, styles, measured rhythm and notes on its motion. Use kuchi_search_videos to find ids and kuchi_get_breakdown for the shot list.

    Show parameters
    • referencestringrequiredA Kuchi video id ('34'), slug, Kuchi link (https://kuchi.kalarislabs.com/#video-34) or the original X post URL
    • response_formatstring'markdown' (default) for readable text, 'json' for structured data
  • kuchi_list_filters1 param

    List every motion style, category, format, aspect ratio, pace and theme in Kuchi, with how many videos each has, to use as filters in kuchi_search_videos. Also lists the shot kinds a shot is classified into when you analyse a storyboard.

    Show parameters
    • response_formatstring'markdown' (default) for readable text, 'json' for structured data
  • kuchi_get_breakdown6 params

    Get the shot-by-shot breakdown of one Kuchi reference, measured from every frame of its video file. Returns exact facts (fps, frame count, length), every shot's start and end in seconds and frames, how it enters (cut, animated transition, hold or blank frame), how much of the frame moves, its tone and colors, motion and loudness per second, and storyboard sheets: grids of real frames stamped with their time and shot number. Each shot says where to see it: its frame on the overview sheet, when it has one, and the detail sheets that show it. Kuchi measures when things happen; what each shot shows is read from the frames. The result lists the shot kinds to classify against, and the analysis goes to kuchi_plan_remake as shot_analysis. Set storyboard="overview" (one frame per shot, or per longest shot when there are many) or "detail" (evenly spaced frames that cover every shot, page with detail_sheet) to receive that sheet as an image. Use it before kuchi_plan_remake to study a reference, and while building to match each shot.

    Show parameters
    • referencestringrequiredA Kuchi video id ('34'), slug, Kuchi link (https://kuchi.kalarislabs.com/#video-34) or the original X post URL
    • storyboardstring'links' (default) returns sheet URLs only; 'overview' or 'detail' also returns one sheet as an image
    • detail_sheetintegerWhich detail sheet to return when storyboard="detail" (1 is the start of the video)
    • shot_offsetintegerShots to skip, for videos with many shots
    • shot_limitintegerShots per page (1-60, default 40)
    • response_formatstring'markdown' (default) for readable text, 'json' for structured data
  • kuchi_plan_remake18 params

    Plan a launch video for the user's product, using a Kuchi reference as an inspiration template. Pass the user's own product details and assets, and your shot_analysis: the kind of each reference shot, read from the storyboard sheets of kuchi_get_breakdown. Returns what to borrow from the reference (rhythm, color roles, motion), a blueprint that re-times the reference's shots to the target length on whole frames and says what content of the user's goes in each shot, the rules for using a reference, and missing_inputs: questions to ask the user before building. ready=false means required inputs are missing. Shots without a kind keep their exact timing and get placeholder content. Call it again with the user's answers and your analysis until ready=true and every shot has a kind. Only list assets the user actually gave you. It does not render video; build it with your own tools, then call kuchi_check_remake.

    Show parameters
    • referencestringrequiredA Kuchi video id ('34'), slug, Kuchi link (https://kuchi.kalarislabs.com/#video-34) or the original X post URL
    • product_namestringThe user's product name. Without it, the plan asks for it in missing_inputs.
    • product_descriptionstringWhat the product does and who it is for, in the user's words
    • audiencestringWho the video is for
    • key_featuresarray1-3 features or moments to show, most important first
    • call_to_actionstringThe closing line or URL, e.g. 'Try it at acme.com'
    • brand_colorsarrayBrand colors, e.g. ['#0B0B0F', '#7C5CFF']
    • fontsarrayBrand typefaces
    • tonestringe.g. 'calm and premium', 'playful'
    • assetsarrayAssets the user has provided. Only list assets the user actually gave you.
    • shot_analysisarrayYour reading of the reference's shots from its storyboard sheets. One entry per shot; send as many as you have analysed.
    • target_secondsintegerTarget length in seconds; defaults to the reference's length
    • fpsnumberFrame rate you will render at, e.g. 30 or 60; defaults to the reference's. The blueprint's frame numbers use it.
    • aspect_ratiostringOutput ratio; defaults to the reference's
    • soundstringHow the video sounds: 'sfx' (open-license sound effects on each shot's cue, the default), 'music_and_sfx' (an open-license music bed too), 'user_track' (the use
    • shot_offsetintegerBlueprint shots to skip, for references with many shots
    • shot_limitintegerBlueprint shots per page (1-40, default 40)
    • response_formatstring'markdown' (default) for readable text, 'json' for structured data
  • kuchi_check_remake6 params

    Check a drafted or finished remake against the rules for using a Kuchi reference. Pass your shot list: timing, the reference shot each one rebuilds, how it enters, the on-screen text, and where each asset came from. Flags text that carries over the reference's brand, assets taken from the reference, generated logos or product UI, placeholders, timing gaps, and shots whose length or entrance drifted from the reference shot they rebuild. Also returns compare_frames: the exact time in your video and in the reference that show the same moment, to set side by side. passed=false means there are errors to fix. It checks what you report, not the rendered file: Kuchi never receives your video. Be accurate about each asset's source.

    Show parameters
    • referencestringrequiredA Kuchi video id ('34'), slug, Kuchi link (https://kuchi.kalarislabs.com/#video-34) or the original X post URL
    • product_namestringThe user's product name, to check it appears on screen
    • target_secondsnumberThe length you were aiming for
    • music_sourcestringWhere the music came from: 'none' when there is no music (sound effects alone are reported as assets)
    • shotsarrayrequiredYour shots in order
    • response_formatstring'markdown' (default) for readable text, 'json' for structured data
  • kuchi_list_components5 params

    List Kuchi's copy-paste Remotion video components: animated text and kinetic type, captions, AI-input and UI screens, cursors, logos, scenes and transitions. It is the set on https://kuchi.kalarislabs.com/components, read from the latest published registry. Returns one page of components, each with its name, title, what it animates, category, npm and Kuchi dependencies, files, registry URL and shadcn install command, plus every category with its count. Filter by keywords or category. Shared library code that components build on is left out unless category="library". Use kuchi_get_component for one component's source. Use it while building a remake, to find a ready-made component for a shot before writing one from scratch.

    Show parameters
    • querystringKeywords matched against names, titles and descriptions, e.g. 'typewriter', 'captions', 'chat prompt'
    • categorystringExact category, e.g. 'text', 'scenes', 'screens', 'ai-input', 'captions', 'cursor', 'logos' or 'library'; the result lists them all
    • limitintegerComponents per page (1-50, default 20)
    • offsetintegerComponents to skip, for pagination
    • response_formatstring'markdown' (default) for readable text, 'json' for structured data
  • kuchi_get_component4 params

    Get one Kuchi video component by name: its description, npm and Kuchi dependencies, shadcn install command, registry URL, usage notes and the full source of its files, read from the latest published registry. Returns one file's source per call (file=1 is the main file); a file longer than about 20k characters comes in parts, and the result says which file and part comes next. Kuchi components it depends on (such as kuchi-ui) are components of their own: get each the same way, or use the install command, which fetches them too. Use kuchi_list_components to find names.

    Show parameters
    • namestringrequiredComponent name from kuchi_list_components, e.g. 'text-reveal', or its registry URL (https://kuchi.kalarislabs.com/r/text-reveal.json)
    • fileintegerWhich file to return the source of (1-based, default 1)
    • partintegerWhich part of a long file to return (default 1)
    • response_formatstring'markdown' (default) for readable text, 'json' for structured data
  • kuchi_get_skill2 params

    Get one of Kuchi's agent skills: step-by-step methods for the build and finish of a remake, bundled with the server so every client has them. - kuchi: the whole remake workflow in short (find, study, plan, build, check). - kuchi-product-launch-video: the whole job of making a product launch video, from the brief to the delivered MP4 (brief, choose a reference, study, plan, storyboard, build, sound, check, render per platform). Start here when the user wants a launch video. - kuchi-remotion: building the blueprint in Remotion: project setup, the @ alias Kuchi components need, one Sequence per shot, entrances, fonts, assets, rendering and exporting frames to compare. - kuchi-sound: sound without hearing it: turning each blueprint shot's sound cue into an open-license sound effect (or the user's track) placed on its frame, chosen and trimmed by measuring with ffmpeg, with every license logged. - kuchi-audio-check: measuring the rendered mix: loudness, true peak, clipping, silence and whether each sound lands on its cue frame. Returns the skill's Markdown. Use kuchi-product-launch-video when a launch video is asked for, and the others before writing video code (kuchi-remotion), before adding audio (kuchi-sound) and before delivering (kuchi-audio-check).

    Show parameters
    • namestringrequiredWhich skill: 'kuchi', 'kuchi-audio-check', 'kuchi-product-launch-video', 'kuchi-remotion', 'kuchi-sound'
    • filestringWhich file of the skill (default 'SKILL.md')
  • search1 param

    Search Kuchi launch-video references. Returns ids to pass to fetch. Same catalog as kuchi_search_videos.

    Show parameters
    • querystringrequiredKeywords, e.g. "pastel UI cursor demo"
  • fetch1 param

    Fetch one Kuchi reference by the id from search, with its notes, links and metadata.

    Show parameters
    • idstringrequiredVideo id from search
  • kuchi_send_feedback8 params

    Send feedback about this server to its developers: a capability you needed that no tool provides, a tool that failed or misled you, or something that worked well. Records the feedback; it does not add or change tools. Leave out personal or sensitive details.

    Show parameters
    • feedback_typestringrequiredWhat kind of feedback this is. Use 'missing_capability' when the tool you needed does not exist in the tool list - nothing failed, the capability is absent. Use
    • summarystringrequiredOne self-contained sentence. For 'missing_capability': the capability you needed, e.g. 'No way to filter videos by music genre.' For 'issue': the tool and the p
    • detailsstringOptional longer context: what you tried, exact parameter values, the error text you saw, and any workaround you used. Omit when the summary says it all.
    • friction_pointsstringOptional: the specific moments that slowed you down, as short bullet-like sentences, quoting exact tool names, parameters, or error text.
    • suggested_improvementstringOptional: the concrete change that would have helped, e.g. the tool to add, the description to reword, or the error message to improve.
    • tool_namestringOptional: the existing tool this feedback is about (for 'issue' or 'praise'). Leave empty for 'missing_capability' - the point is that no tool fits.
    • sentimentstringOptional: how the experience felt overall.
    • task_completedbooleanOptional: whether you still completed the user's task despite the problem.

Checked by Serverdex with a plain initialize + tools/list call to kuchi.kalarislabs.com/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 22, 2026
Stars
1
Forks
0
Last push
Nov 20, 2026
License
MIT

TypeScript

From the README

Kuchi AI for viral launch videos. Real launch videos, measured frame by frame, that your AI agent can remake for your product. Website · Connect your agent · The collection · Contribute What is Kuchi? Kuchi is a library of launch videos that spread, built to be copied in spirit. Each one is a template: Kuchi measures its exact shots, timing and transitions, and your agent copies that motion and taste and fills it with your own product, assets and copy. It never reuses the reference's brand, footage or music. For founders, designers and builders making their next product launch. Browse a style, watch a reference, then hand it to your agent. Every reference has a playable video, a frame-by-frame breakdown, a remake prompt and credit to the original creator. Kuchi measures and plans; your agent does the seeing and the building. Kuchi does not render video. How a remake works Connect your agent Add the MCP server https://kuchi.kalarislabs.com/mcp (Streamable HTTP, read-only, no sign-in), or paste this into your agent: In Claude Code, install the plugin (MCP server + skill): Setup for Claude, ChatGPT, Codex, Cursor & more · Skill file · Plugin New videos reach connected agents within a minute, with no reinstall. Without MCP, the same data is at /agent/catalog.json and /agent/workflow.md. What is in this repository The collection Every reference below has an inline player, the video file, a remake prompt and credit to the original creator.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://kuchi.kalarislabs.com/mcp

The most-starred Health & Science servers in the index, with their live-check result.

ServerStarsLast pushLive check
Arxiv MCP Server3,284Nov 2026Local / not checked
com.medplum MCP2,802Nov 2026Needs sign-in
Tooluniverse1,791Nov 2026Local / not checked
Mirobody1,639Nov 2026Local / not checked
Tavotto728Nov 2026Local / not checked

Kuchi: questions people ask

Is Kuchi a remote or a local MCP server?
According to its entry in the official MCP registry, Kuchi ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does Kuchi need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is Kuchi safe to use?
Looks healthy: Kuchi is maintained, open source, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Kuchi still maintained?
Active: the repository's last commit 2 days ago. Last push Nov 20, 2026, 1 GitHub stars, MIT licence. Read from GitHub on Nov 22, 2026.
What tools does Kuchi expose?
14 tools as listed by the server itself during the live check, including kuchi_get_workflow, kuchi_suggest_templates, kuchi_search_videos, kuchi_get_video, kuchi_list_filters. The full list with parameters is in the Live check section above.
How do I add Kuchi to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Health & Science →

Add the badge to your site

Show visitors that Kuchi is listed here — it’s also the link we check for a free listing.

Kuchi — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-kalarislabs-kuchi?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Kuchi — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Kuchi — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-kalarislabs-kuchi?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-kalarislabs-kuchi) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-kalarislabs-kuchi) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-kalarislabs-kuchi)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-kalarislabs-kuchi"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-kalarislabs-kuchi"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-kalarislabs-kuchi"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).