Skip to content
mountly

Why mountly

You have a React, Vue, or Svelte component. You need it on a page (or in an MCP host) that should not own that framework’s lifecycle. Mountly is the delivery layer for that.

Interactive UI on a static or CMS page

Section titled “Interactive UI on a static or CMS page”

Marketing needs a pricing calculator or signup form. You already have the component in the product app. Publish it as a tag; they add one script and drop the element in. The component and its CSS load when the element connects.

See Script-tag embeds.

Replace a legacy section without a rewrite

Section titled “Replace a legacy section without a rewrite”

A Rails or Django page still owns the shell. You replace one region at a time with a widget that mounts and unmounts cleanly. The host architecture stays put until the last section is gone.

Several teams on one page you run

Section titled “Several teams on one page you run”

Payments, support, and content each ship a widget on their own cadence. The host pins URLs in a manifest and shares one framework through an import map. That is the runtime track, not a script tag per team with its own React copy.

Different frameworks during a migration

Section titled “Different frameworks during a migration”

One team still ships Vue while another ships React. Each wraps with its adapter. Widgets mount in their own containers. You do not force a rewrite to share a page.

MCP-hosted UI

Section titled “MCP-hosted UI”

The same component can render inside Claude or ChatGPT when a tool is called. mountly-mcp builds the View artifact and registers it on a server you already own. See MCP Apps.

Where to go next

Section titled “Where to go next”