How does Orvain UI help with AI and vibe coding?

Orvain UI is built so AI coding tools such as Cursor, Claude Code, Windsurf and v0 can read the real component API through a hosted MCP server, which means generated screens use props, variants and tokens that exist instead of ones the model invented.

By the Orvain team. Orvain UI is made by Oussema Ajmi, founder. Published October 4, 2026, updated October 20, 2026.

Why does AI-generated UI break?#

An assistant predicts code from a snapshot of public repositories, not from the library you installed. It invents props, imports paths that were never published and hard-codes colours. The code looks right until it is built, and the fix is a source of truth the model can query.

How does Orvain UI help?#

  • A hosted MCP server exposes components, props, variants, tokens and accessibility rules.
  • Generation is checked against the component schemas, so an invented prop is rejected before code is written.
  • Tokens mean a generated screen follows your brand, not default colours.
  • Any MCP-compatible tool connects with one config entry; v0 uses an adapter.

Can I use it today?#

Yes. The hosted MCP server is live at mcp.orvain.dev and comes with the code library. Connect it with the licence key from your purchase. In Claude Code that is claude mcp add --transport http orvain https://mcp.orvain.dev, with the key sent as an Authorization: Bearer header; the Editor and MCP docs have the full command and the config for Cursor.

What does it not do?#

It does not make an assistant good at design. It tells the assistant what exists; choosing what suits the page is still the job of whoever is prompting.

Questions#

What is vibe coding?

Vibe coding is building software by describing what you want to an AI assistant and iterating on what it writes, with little hand-written code. A design system helps because it constrains what the assistant can produce to components that exist.

Which tools does the Orvain MCP server work with?