Your AI assistant, fluent in Orvio.
Connect Orvio to the AI tools you already use. Ask for a product, a page or a component, and it arrives in your project as real source.
- One remote MCP serverEvery product in the catalog, one address.
- Approved in your browserNo keys to paste. Revoke any time in Account.
- Real source filesAs authored, in the product's own structure.
How it works
Four steps, once. Solid cards happen in Orvio; outlined cards happen in your AI tool.
Copy the server address
One address for every product in the catalog.
Add it as a remote MCP server
Paste the address in your tool's MCP settings.
Approve it in your browser
Your tool opens an Orvio page. Sign in and allow access. Each tool gets its own authorization.
Ask by name
Name a product, a page or a component. Your tool searches, reads and fetches the files.
Every request checks your active membership. Without one, your tool gets an access error.
Your tool always works from a product's current release, never an older one.
Tools only read. Files arrive byte for byte as the publisher wrote them, with a SHA-256 to check.
Revoke any tool's access at any time in Account › Integrations.
Set it up
Pick how you work. Remote MCP works from any AI tool that supports it; the CLI is on npm for terminals, scripts and CI. Every product is static HTML, CSS and JavaScript, so your agent can rebuild it in your framework: React, Vue, Svelte, Astro or plain HTML.
Connect your tool once. Use every product.
- 1Copy the server addressFrom the panel on this page.
- 2Add a remote MCP serverIn your tool's MCP or connector settings.
- 3Approve in your browserYour tool opens Orvio. Sign in and allow access.
- 4Ask for what you needBy name, or with an identifier from a product page.
search_productsFind products, or list the catalogget_productA product's current release, framework, pages and componentsread_releaseOverview, licence, publisher instructions and file treelist_release_filesThe file tree with sizes and SHA-256 digestsread_fileOne file, byte-identical to the archiveget_pageA page with the source files it needsget_componentA component with the source files it needsread_tokensThe design tokens and the files that define themlist_bookmarksProducts you saved on the websiteTwo ways to use a product
Choose on any product page. Your agent gets something different for each, with the same membership.
Use as template
The complete source of the release, in its own framework, structure and file names. By MCP, or as a ZIP from the product page.
Use as inspiration
The product's design tokens and the pages or components you name, as reference. Your agent rebuilds the look in your own stack and brand.
Both ways, every product.
Template or inspiration, by MCP or ZIP. Members can use any product in the catalog, always in its latest release.
Join OrvioAsk by name, or be exact.
Plain words work: "the Homepage page from Sotto". When you want precision, every product page lists an identifier for the release, each page and each component. Paste it into your prompt and your agent fetches exactly that.
- 01
sottoWhole release · Every file, as authored - 02
sotto/pages/homepageOne page · With what it needs - 03
sotto/tokensDesign tokens · Colours, type and spacing
The AI tools you already build with.
Any assistant or editor that can add a remote MCP server can connect to Orvio. Builders that import code can still take the ZIP from any product page.
If something goes wrong
Your tool reports the problem. Here's what it usually means.
Sign-in required
Not connected yet, or the approval expired.
Access revoked
Access was removed in Account › Integrations.
Release not available
That release was withdrawn.
Server unreachable
A network or Orvio service issue.
One membership.
Every product, on request.
While your membership is active, your agent can fetch any product, page or component in the catalog, always from its latest release.