flatkit
The open language, compiler, and player for the animation format — a modern, web-native take on the "one file that just plays" idea behind the old SWF.
Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y @flatkit/[email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add flatkit-mcp -- npx -y @flatkit/mcp@0.3.22Execute em um terminal.
{ "mcpServers": { "flatkit-mcp": { "command": "npx", "args": [ "-y", "@flatkit/[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirWrite a scene as readable text, compile it to a single self-contained .flatpack, and play it in any <canvas> with a runtime small enough to drop into someone else's bundle. Animations and interactivity — drags, drop zones, scratch-to-reveal, connect-the-dots, per-frame logic, sound — all in plain data, no plugin, no black box.
Status: beta. The packages and the
.flatpackformat are still moving; expect breaking changes (and tell us when something feels wrong).
The fastest way in is the visual studio: flatink.zwyk-studio.com.
Draw shapes, key your timeline, wire up interactions by clicking — then export to the open .flatpack that this toolchain compiles and plays. The editor is the friendly front door; flatkit is the code-first half of the same format: author by hand, generate from a script or an LLM, diff it in git, test it in CI. Same .flatpack either way — pick the workflow that fits the moment.
drag/drop, turn (dials), trace (follow a path), reveal (scratch cards), link (connect pairs), plus per-frame logic (every frame) and a tiny expression language..flatpack JSON, media embedded as data: URIs (or served as local files), played by a runtime with no editor and no heavy dependencies.The player must stay tiny — it gets embedded in third-party bundles — so it never pulls in the compiler. The compiler is bigger and lives in build/CLI tools. engine is the shared core, types the common leaf. The boundary is enforced in CI: the public packages never import editor-only or heavy code.
pnpm add @flatkit/player # play a .flatpack
pnpm add -D @flatkit/compiler # the flatc CLI
Write a program, compile it, play it:
flatc scene.flatink -o scene.flatpack # text sources → one playable file
flatc scene.flatink --render -o frame.png # headless PNG (see what you draw)
flatc scene.flatink --play --script gestures.json # headless replay + assertions (great in CI)
import { FlatPlayer } from '@flatkit/player'
const player = new FlatPlayer(canvas, doc, { autoplay: true })
Learn the DSL in docs/ — a guided set from getting started to
scene & drawing, behavior & interactions,
expressions & stdlib, and the flatc tooling.
Embedding it in an app (receiving send events, driving variables) →
host integration. See examples/cli for an end-to-end project.
pnpm install
pnpm verify # lint + english check + typecheck + tests
The four core packages (types, engine, compiler, player) are versioned together, sugarflat and mcp on their own. All are in place and tested; the .flatpack format and public APIs are still moving (beta), so expect breaking changes.
A .flatink program or a .flatpack document is untrusted input. The toolchain hardens the two boundaries accordingly: path confinement when compiling, data:-only assets (with an opt-in same-origin resolver for local files), and bounded per-tick work and recursion in the player. See SECURITY.md for the threat model and how to report an issue.
MIT © Zwyk Studio
FlatInk MCP server: exposes the asset library + the forge's compile/preview/publish as tools for LLM agents.
{ "mcpServers": { "flatkit-mcp": { "command": "npx", "args": [ "-y", "@flatkit/[email protected]" ] } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
@flatkit/mcp roda localmente via stdio.
Última verificação: 2026-11-13. FlatInk MCP server: exposes the asset library + the forge's compile/preview/publish as tools for LLM agents.