Riveのエディタを起動せずに.rivファイルを作成・編集できるMCPサーバーを作ったThe author built and released an MCP server that creates and edits .riv…

Rive, a widely used tool for building interactive animations, exports compact .riv files that ship inside apps, games, and websites. A developer has now released a Model Context Protocol (MCP) server that can create and edit those .riv files programmatically, without ever launching the Rive editor. The project matters because it targets a specific and long-standing gap: until now there were few practical ways to manipulate .riv files directly from code, which limited how animation work could be automated or driven by AI assistants.

Writing on Qiita, the author frames the effort around personal frustration rather than a grand ambition. They say they genuinely like Rive as an interactive-animation tool, but found almost no way to touch .riv files from a program. The official MCP server assumes the Rive editor is already running, and the third-party options they came across were paid. The stated goal of the new server is to work as long as a .riv file exists — an editor-free approach that could suit headless environments where launching a desktop application is impractical.

To understand why this is useful, it helps to recall what each piece does. MCP is an open standard, introduced by Anthropic, that lets AI assistants and other client applications connect to external tools and data through a consistent interface. An MCP server exposes capabilities that a client, such as an AI coding assistant, can call on demand. Over the past year a large community of MCP servers has appeared, many of them wrapping design and creative tools so that language models can inspect or modify project files. This Rive server fits squarely into that pattern.

Rive itself is a design-and-code tool for real-time graphics and animation. Designers build motion and interactive logic in its editor and export the result as a .riv file, a binary runtime format that is deliberately small and fast to load. Rive publishes runtimes for the web, Flutter, React, iOS, Android, and other platforms, so a single .riv file can be reused across targets. Its state machine feature lets animations respond to inputs, which makes Rive popular for UI micro-interactions, animated characters, and data-driven visuals.

Because the .riv format is binary and not widely documented, editing it directly from code is a nontrivial task, and the author's server appears to implement its own reading and writing of that structure rather than relying on the editor's export path. That design is what allows it to run without a GUI, but it also comes with the usual caveats of an independent, community project: coverage of Rive's many features is likely to be partial, and behavior may vary across Rive versions or specific file contents. Anyone adopting it would be wise to validate output against the official runtimes before depending on it in production.

The editor-dependency point is central to the motivation. A server that needs a running editor cannot easily