MCP limitations

Misaki Studio MCP is a broad authoring and inspection surface, but it is not remote desktop control, an automatic deployment guarantee, or a universal undo system. These current boundaries help you choose safe prompts and recognize when the UI, desktop host, or an external verification step is still required.

Connection and trust boundary

• The production endpoint exists while the packaged desktop app is running and defaults to http://localhost:16472/mcp.

• If the default port is occupied, the app can bind a higher free port; a client configured for 16472 does not discover that move automatically.

• The current route has no separate MCP authentication token. Connect trusted clients only and do not tunnel, proxy, port-forward, or publish the endpoint.

• Host-assisted Preview, screenshots, interactions, PDF/video work, and related operations require a healthy connection to the running desktop host.

• Development-only dev-* tools are opt-in repository instrumentation and are not part of the packaged customer authoring workflow.

Read Connect an agent for setup and recovery.

Session and target boundaries

• Every MCP session begins without a selected project.

• MCP project selection is independent of the project visible in the editor.

• Reconnection, server restart, or a new client session requires project selection again.

• Copied file/folder references use project-relative paths and can become stale after move or rename.

• Element IDs belong to one file and can become stale after deletion or replacement.

• Structured references are resolved in supported top-level fields, not inside arbitrary nested JSON.

• Folder references are accepted only by the currently supported path fields; other fields may require a plain project-relative path.

Always read current project and element trees before a consequential write.

Parity is about results, not every gesture

MCP does not reproduce editor-only session state such as open tabs, Previous/Next file navigation, expanded rows, canvas zoom, or panel layout. That does not prevent the agent from changing the same stored project content with explicit IDs.

Known user-facing coverage boundaries include:

• true anchored node.data.popup configuration and listener expressions are currently editor-only;

• a Code Component's own animatable timeline is MCP-only in its file because its UI exposes Logic and Code rather than an Animate panel;

• generic run-operation currently executes Component-target operations; other declared target kinds return unsupported;

• Mockups have an editor-canvas capture but no runtime Preview or ordinary generated-component export;

• Image collection mutation does not have a complete dedicated MCP family;

• dedicated Font Weight authoring is incomplete;

• a registered Video design-system item does not create a native canvas Video node;

• some Document/Blog presentation and generated-output behavior remains incomplete.

For the broader mapping, see UI-to-MCP capability map.

Verification boundaries

• A successful tool response is not proof of visual or behavioral correctness.

• Activity marks identify recent work but are volatile and bounded; they are not an audit log.

• A screenshot proves one state and viewport, not every screen, variant, theme, or interaction.

• Preview typing and keyboard input require the intended field to be focused first.

• Computed styles and measurements can be incomplete or stale when the rendered state has not refreshed; investigate contradictory evidence.

• Diagnostics are useful but do not replace compiling and testing the generated output in its intended consumer.

• External export or publication must be verified at the folder, repository, registry, site, database, or service it affected.

Use Verify agent work rather than relying on a completion summary.

Mutation and recovery boundaries

• UI and MCP share one eligible design-file content history.

• undo and redo each move one design-file step; an intervening UI or MCP edit changes what is on top.

• Whole-file operations, non-design-file edits, and external destinations are not generally covered by those tools.

• delete-file cannot be undone.

• An unknown top-level field can be ignored with a warning while recognized fields are still applied.

• A handler failure does not guarantee that attempted work was rolled back. Read current state before retrying.

See Undo agent changes for the recovery procedure.

Product and generated-output boundaries

MCP can author product data that the current Preview or exporter does not fully ship. Important examples documented elsewhere include:

• per-screen timeline mode is stored, but exported element animation targets are not currently scoped to the corresponding container-query breakpoint;

• shader keyframes can be edited and previewed, while current generated output remains static for that shader;

• Preview can author and exercise some authentication flows, but the Component exporter does not emit a complete client authentication implementation;

• public backend boilerplate action execution and complete exclusion of sensitive Users/password data from frontend output are still unfinished;

• boilerplate readiness differs, so a configured output is not automatically a production-ready deployment.

Read Animation and timelines, Logic and data, and Choose a boilerplate before using those areas in shipped work.

Side effects require explicit authorization

Do not treat an ordinary design request as permission to delete project content, write a local destination, change Git, publish a package or site, run a database action, or mutate another external service. Ask for the exact target, effect, and verification separately.