Status check: is this project still in progress or deprecated? (MCP + AI agent integration idea)

Start with the README's statement that the project is experimental and untested, then review the repository's current direction before assessing the MCP and AI-agent proposal. Done would require a clear decision about whether the project is active, deprecated, or superseded, plus guidance on any recommended alternative.

Hi Rive team 👋

First — this repo looks really promising for simplifying runtime integration by generating type-safe wrappers / JSON / templates from .riv files.

1) Status check (in progress vs deprecated)

Could you confirm the current status and intended direction of this project?

• Is rive-code-generator-wip still actively developed and recommended to build on?
• Or is it considered experimental / paused / superseded by another internal or public codegen approach?

I saw the README mentions it’s “experimental and untested”, so I’m trying to understand whether it’s expected to mature or whether users should treat it as a prototype only.

2) Feature request / idea: MCP + AI agent + bring-your-own AI key

Given the recent momentum around MCP workflows, I think this project could become extremely useful if it can be used as an MCP tool (or paired with an MCP server), enabling AI agents (Cursor/Claude/etc.) to:

• Inspect a .riv file (artboards, state machines, inputs, etc.)
• Generate code wrappers/templates automatically (Dart, TS, etc.)
• Optionally apply project-specific conventions via templates or prompts
• Support a custom AI key (bring-your-own-key) for teams that prefer their own provider/billing/security model

Even without AI, exposing the generator as an MCP tool would be valuable (structured introspection + deterministic codegen). With AI, it becomes a “Rive integration copilot” for large apps.

3) If this is deprecated…

If it’s deprecated, could you point to the recommended alternative (repo, roadmap, or internal tooling direction) so the community can align?

Thanks!