What Orvain UI is, how it works with your AI tools,
and what you own when you buy it.
What Orvain UI is, what comes with it, and which frameworks it supports.
Orvain UI is a design system for React and Vue with a matching Figma library and a hosted MCP server. It ships 45 free components across 7 categories, 642 production-ready blocks in 54 families, and a token layer you override to make the whole system match your brand.
Orvain UI supports React and Vue, from the same design tokens and the same Figma source. The React package, @orvain/react, is tree-shakeable and safe to use in React Server Components, so importing one component does not pull the library into your client bundle.
A component is a single primitive: a button, an input, a checkbox. A block is a finished piece of interface built from those primitives, such as a pricing table, a sign-in screen or a data table with filters. Orvain UI has 45 components and 642 blocks, and every block is assembled from the components rather than drawn separately, so theming one themes both.
Yes, in part. Orvain UI's 45 documented components are free forever and need no account. The Figma library, the full block library and the MCP server are paid, and the Figma library is a one-time purchase rather than a subscription.
The free components cost nothing and need no account. The code library, with the full block library, the CLI and the hosted MCP server, is $179 (Solo), $449 (Studio) or $899 (Business) a year, including updates while renewed, or a one-time $349 (Solo), $899 (Studio) or $1,799 (Business) for the version available on the day you buy. The Figma library is a one-time $199 (Solo), $499 (Studio) or $999 (Business), and the bundle of code and Figma is a one-time $449 (Solo), $1,190 (Studio) or $2,390 (Business). Solo covers 1 person, Studio covers up to 8 people, Business covers up to 20 people. Prices are in US dollars.
Install the free Orvain UI components from npm with npm install @orvain/react or npm install @orvain/vue, and import @orvain/react/style.css once at the root of your app. The full library comes with the licence key from your purchase: run npx @orvain/cli login <licence-key> once, then add components by name, for example npx @orvain/cli add flat-button.
Yes. In Orvain UI, colour, typography, spacing and radius are all design tokens, so changing the token values re-themes every component, every block and the Figma file together. Nothing is hard-coded to the Orvain palette, so an agency can run several brands from one system.
How Orvain UI connects to Cursor, Claude Code, v0 and other AI coding tools.
The Orvain MCP server is a hosted Model Context Protocol endpoint at https://mcp.orvain.dev that gives AI coding tools live access to the real component API: props, variants, tokens and usage patterns. It needs the licence key from your purchase. MCP is an open standard for connecting AI assistants to external tools and data.
Without one, it guesses. An assistant working from training data invents props that do not exist and imports paths that were never published, and the code looks right until it is run. Pointed at the Orvain MCP server, the same assistant reads the current API and writes against what the library exports.
Orvain UI works with any client that speaks the Model Context Protocol, including Cursor, Claude Code and Windsurf, and with v0 through an adapter. The server is hosted, so connecting it is a URL in your tool's MCP settings rather than something to install and run yourself.
Point the tool at https://mcp.orvain.dev over Streamable HTTP and send your licence key as an Authorization: Bearer header. In Claude Code that is one command: claude mcp add --transport http orvain https://mcp.orvain.dev --header "Authorization: Bearer <licence-key>". In Cursor it is an "orvain" entry with that URL and header in ~/.cursor/mcp.json. The MCP docs have both in full.
What you own, how updates work, and how to reach a person.
Yes. Block and component source you copy from Orvain UI is yours to keep and modify, with no attribution required and no runtime dependency on Orvain. Your project does not break if you later stop paying, because the code already lives in your repository.
No. The Orvain UI Figma library is a one-time purchase and the file is yours permanently, including the updates published while your licence is active.
Yes, by construction. Both read the same token set and the same component names, and the Figma components are built with variables and variants that map one-to-one to the code props, so a handoff is a lookup rather than a translation.
Email hello@contactoussema.uk, or use the contact page. Messages go to the founder, and a reply usually arrives within one business day.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
What Orvain UI is, how it works with Cursor, Claude Code and v0, and what you own when you buy it.
What Orvain UI is, what comes with it, and which frameworks it supports.
Orvain UI is a design system for React and Vue with a matching Figma library and a hosted MCP server. It ships 45 free components across 7 categories, 642 production-ready blocks in 54 families, and a token layer you override to make the whole system match your brand.
Orvain UI supports React and Vue, from the same design tokens and the same Figma source. The React package, @orvain/react, is tree-shakeable and safe to use in React Server Components, so importing one component does not pull the library into your client bundle.
A component is a single primitive: a button, an input, a checkbox. A block is a finished piece of interface built from those primitives, such as a pricing table, a sign-in screen or a data table with filters. Orvain UI has 45 components and 642 blocks, and every block is assembled from the components rather than drawn separately, so theming one themes both.
Yes, in part. Orvain UI's 45 documented components are free forever and need no account. The Figma library, the full block library and the MCP server are paid, and the Figma library is a one-time purchase rather than a subscription.
The free components cost nothing and need no account. The code library, with the full block library, the CLI and the hosted MCP server, is $179 (Solo), $449 (Studio) or $899 (Business) a year, including updates while renewed, or a one-time $349 (Solo), $899 (Studio) or $1,799 (Business) for the version available on the day you buy. The Figma library is a one-time $199 (Solo), $499 (Studio) or $999 (Business), and the bundle of code and Figma is a one-time $449 (Solo), $1,190 (Studio) or $2,390 (Business). Solo covers 1 person, Studio covers up to 8 people, Business covers up to 20 people. Prices are in US dollars.
Install the free Orvain UI components from npm with npm install @orvain/react or npm install @orvain/vue, and import @orvain/react/style.css once at the root of your app. The full library comes with the licence key from your purchase: run npx @orvain/cli login <licence-key> once, then add components by name, for example npx @orvain/cli add flat-button.
Yes. In Orvain UI, colour, typography, spacing and radius are all design tokens, so changing the token values re-themes every component, every block and the Figma file together. Nothing is hard-coded to the Orvain palette, so an agency can run several brands from one system.
How Orvain UI connects to Cursor, Claude Code, v0 and other AI coding tools.
The Orvain MCP server is a hosted Model Context Protocol endpoint at https://mcp.orvain.dev that gives AI coding tools live access to the real component API: props, variants, tokens and usage patterns. It needs the licence key from your purchase. MCP is an open standard for connecting AI assistants to external tools and data.
Without one, it guesses. An assistant working from training data invents props that do not exist and imports paths that were never published, and the code looks right until it is run. Pointed at the Orvain MCP server, the same assistant reads the current API and writes against what the library exports.
Orvain UI works with any client that speaks the Model Context Protocol, including Cursor, Claude Code and Windsurf, and with v0 through an adapter. The server is hosted, so connecting it is a URL in your tool's MCP settings rather than something to install and run yourself.
Point the tool at https://mcp.orvain.dev over Streamable HTTP and send your licence key as an Authorization: Bearer header. In Claude Code that is one command: claude mcp add --transport http orvain https://mcp.orvain.dev --header "Authorization: Bearer <licence-key>". In Cursor it is an "orvain" entry with that URL and header in ~/.cursor/mcp.json. The MCP docs have both in full.
What you own, how updates work, and how to reach a person.
Yes. Block and component source you copy from Orvain UI is yours to keep and modify, with no attribution required and no runtime dependency on Orvain. Your project does not break if you later stop paying, because the code already lives in your repository.
No. The Orvain UI Figma library is a one-time purchase and the file is yours permanently, including the updates published while your licence is active.
Yes, by construction. Both read the same token set and the same component names, and the Figma components are built with variables and variants that map one-to-one to the code props, so a handoff is a lookup rather than a translation.
Email hello@contactoussema.uk, or use the contact page. Messages go to the founder, and a reply usually arrives within one business day.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.