MCP covers most stored authoring results in Misaki Studio, but it does not reproduce every editor gesture or session control. Use this map to choose a route and to see where the current result is partial, UI-only, or machine-oriented.
There is no fixed operation count here. Tool registration and schemas change with the product; the connected client's current production schemas are the exact operation reference.
Area: Project selection and metadata · Coverage: UI + MCP · UI route: Dashboard and project menu · MCP route and current difference: list-projects, select-project, project reads and supported metadata operations. MCP selection is per session and independent of the visible editor.
Area: Open tabs, file history, Explorer expansion, zoom, panel layout · Coverage: UI only · UI route: Top bar, Explorer, canvas, panels · MCP route and current difference: These are editor-session navigation, not stored project content.
Area: Files and folders · Coverage: UI + MCP · UI route: File Explorer menus · MCP route and current difference: Project file/folder tools cover discovery and main mutations. Whole-file deletion is not design-file undo.
Area: Element hierarchy · Coverage: UI + MCP · UI route: Element Explorer and canvas · MCP route and current difference: Tree reads/search plus add, move, duplicate, convert, and delete operations for supported nodes. MCP uses IDs rather than drag gestures.
Area: Canvas drawing and direct manipulation · Coverage: UI + MCP for many results · UI route: Draw tools, canvas handles, resize and move · MCP route and current difference: Structured node, path, canvas, and style operations can reach many stored results; precise freehand/spatial judgment remains easier in the UI.
Area: Design inspector · Coverage: UI + MCP · UI route: Right bar Design · MCP route and current difference: Broad style, attribute, content, screen, variant, and component-instance operations. Coverage is result-based and can differ property by property.
Area: Responsive screens · Coverage: UI + MCP · UI route: screen frames and screen controls · MCP route and current difference: Screen discovery/mutation plus per-screen style layers. Export behavior must be checked for the affected property and timeline.
Area: Properties, states, events, and variants · Coverage: UI + MCP · UI route: Component data-structure controls · MCP route and current difference: Typed slot and logic operations cover the main contracts. Use current IDs and read the data structure before changing it.
Area: Animation and timelines · Coverage: UI + MCP, with exceptions · UI route: Animate inspector and bottom timeline · MCP route and current difference: Timeline/keyframe operations cover main authoring. A Code Component's own timeline is MCP-only because its editor has Logic/Code panels; parent design files can animate an instance in the UI.
Area: Logic, bindings, conditions, repeats, and data mounts · Coverage: UI + MCP, with exceptions · UI route: Logic inspector and logic editors · MCP route and current difference: Dedicated logic/data operations plus logic-format. True node.data.popup and listener expressions are currently editor-only.
Area: Preview and debugging · Coverage: Partial MCP · UI route: Preview button and interactive Preview · MCP route and current difference: MCP adds screenshots, DOM/state reads, computed styles, measurements, interactions, logs, and diagnostics. It depends on the running host and does not replace visual review.
Area: Undo and redo · Coverage: UI + MCP for design-file content · UI route: standard editor undo/redo · MCP route and current difference: undo/redo move one shared design-file history step. They do not reverse whole-file or external operations.
Area: Colors, fonts, images, radius, spacing, themes, audio, and video registries · Coverage: UI + MCP, with per-file exceptions · UI route: corresponding design-system files · MCP route and current difference: Dedicated families cover most registry work. Font-weight authoring remains incomplete, and a registered video is not a native canvas Video node.
Area: Image collections · Coverage: Partial MCP · UI route: Image collection file workspace · MCP route and current difference: Project/file discovery is available, but there is no complete dedicated image-collection mutation family.
Area: Content and database tables · Coverage: UI + MCP · UI route: Content/Table workspace · MCP route and current difference: Row, column, View, mount, and action operations cover core data workflows. Runtime/export and credential boundaries still require separate verification.
Area: API and storage · Coverage: UI + MCP · UI route: API/Storage file workspaces and Logic · MCP route and current difference: Dedicated file operations and component data-source mounts. Test without real secrets and verify the intended runtime environment.
Area: Documents and blogs · Coverage: Partial MCP · UI route: Document/Blog workspaces · MCP route and current difference: Structured document/blog operations exist, but some editor presentation controls and generated-output behavior remain incomplete.
Area: Code Components · Coverage: UI + MCP · UI route: Code Component Logic and Code panels · MCP route and current difference: Create/read/update/compile operations are available. Visual animation of the Code Component's own animatable contract uses MCP timeline authoring.
Area: Scripts · Coverage: UI + MCP · UI route: Script file editor · MCP route and current difference: Script file operations cover source/configuration; runtime side effects depend on where and how the script runs.
Area: Project libraries and environments · Coverage: UI + MCP · UI route: settings and corresponding files · MCP route and current difference: Dedicated operations cover current configuration. Consumer compatibility still needs a real build.
Area: Generated code inspection · Coverage: UI + MCP · UI route: file export/code views · MCP route and current difference: export-code and diagnostics provide machine-readable evidence for supported design files. Mockups do not use normal code export.
Area: Local and Git export configuration · Coverage: UI + MCP · UI route: project controls and Export Settings · MCP route and current difference: Read/update operations exist; writing or pushing affects an external destination and needs explicit authorization.
Area: Package and website publication · Coverage: UI + MCP where configured · UI route: project controls/publish flow · MCP route and current difference: Production operations require valid destination configuration and independent remote verification. They are not covered by design-file undo.
Area: Boilerplates · Coverage: UI + MCP for project configuration and output inspection · UI route: boilerplate selection/setup routes · MCP route and current difference: Current readiness differs by boilerplate. Read the boilerplate guide before promising a deployable output.
Some MCP operations intentionally have no ordinary UI button equivalent. They include structured discovery, operation-schema inspection, Preview DOM/state reads, computed-style inspection, diagnostics, and automated interaction evidence. They expose project or runtime facts for an agent; they do not imply that editor navigation should also be agent-controlled.
Development-only dev-* tools can drive Misaki Studio's own windows in an opted-in repository development environment. They are excluded from the ordinary packaged customer authoring surface and should not appear in visitor instructions as a product dependency.
For any important workflow:
Identify the stored result, not only the visible gesture.
Read the connected tool's current schema.
Check the relevant Learn or Workflow guide for prerequisites and export/runtime limits.
Verify the result through both structure and behavior or rendering.
Treat deletion and every external destination as a separate authorization boundary.
See MCP limitations for cross-cutting constraints.