Use this page for the product-level answers. Continue with Designer questions, Developer questions, React and Next.js questions, UI and MCP questions, Export and boilerplate questions, or Accounts and collaboration questions when the decision becomes specific.
Misaki Studio is a visual workspace for building interface components with design, responsive behavior, animation, logic, and data in one project. It also provides code, export, package, and publishing workflows and exposes project authoring through MCP.
The documentation is designed for interface designers, developers, and React/Next.js developers. Designers can begin from the canvas and component model; developers can go deeper into logic, data, source, debugging, MCP, and generated output.
Choose the shortest path for your role.
It combines both concerns. Pages, visual Components, and Mockups use a visual Component editor, while the same project can also contain code components, scripts, APIs, storage, database/content files, documents, design-system files, and export settings.
No for the first visual workflows. You can create and style a Component without writing React. React and framework knowledge becomes important when you inspect generated output, integrate it into an application, choose dependencies, use source components, or define your team's re-export boundary.
No. The visual editor is a direct way to work with supported project and file surfaces. MCP is an additional route for inspection, authoring, verification, and repeatable operations.
Compare UI and agent workflows.
Yes. A useful pattern is to inspect and refine visually, delegate a bounded operation, require the agent to verify it, then review the affected file in the editor. Desktop activity indicators can show which files or elements the MCP server read or changed.
Not as a one-to-one copy of every gesture. Production MCP tools cover broad project and Component operations, while tab order, panel sizing, expanded rows, zoom, and other session navigation remain UI concerns. Some MCP inspection and automation capabilities also have no ordinary visible control.
Each workflow guide labels its coverage as UI + MCP, Partial MCP, UI only, MCP only, or Desktop required.
The MCP server exposes undo and redo for a selected or referenced file's content history. Whole-file operations and external actions such as deletion, export, Git, package publication, or website publication have different recovery behavior and must be reviewed separately.
A project can contain visual Pages, Components, and Mockups alongside design-system, image/media, document, API, storage, script, database/content, environment, and export-related files. The exact creation rules, workspace, and MCP coverage differ by file type.
Misaki Studio contains code preview, local and Git export routes, package publication, and website publication surfaces. Before choosing one, check the destination, app mode, framework compatibility, dependencies, overwrite behavior, and recovery model in the rewritten Export & Ship guides.