Documents
Welcome
Introducing
Why Misaki Studio
Compare
Start Here
Learn
Workflows
Export & Ship
AI & MCP
Questions & Answers
Reference
Project interface reference
File types
Element types
Design properties
Keyboard shortcuts
MCP capabilities
Export output reference
Dependencies and compatibility
Browser versus desktop
Current limitations
Troubleshooting
Examples

MCP capabilities

Misaki Studio's production MCP server exposes structured project authoring, inspection, Preview, diagnostics, export, and reconstruction operations. Use this family map for discovery; use the connected client's current schemas for exact names, fields, enums, and descriptions.

No fixed tool count is published because registration changes with the product.

Capability families

  • Family: Projects · Main results: list/select/create/rename/describe/delete projects; publish template

  • Family: Files and folders · Main results: full tree/raw reads; create/move/rename/duplicate/convert/delete

  • Family: Design-file history · Main results: one-step undo/redo for eligible design files

  • Family: Screens and elements · Main results: create/search/read/reparent/duplicate/convert/delete visual structure

  • Family: Styles · Main results: layered design values, attributes, links, refs, tooltip/cursor behavior

  • Family: Component contracts · Main results: props/states/events/validators/variants/children/test cases/slots

  • Family: Logic and data · Main results: conditions, repeats, bindings, listeners, actions, API/Storage/View mounts

  • Family: Timelines · Main results: timeline config, commands, segments, keyframes, specialized captures, audio

  • Family: Preview/debug · Main results: screenshots, DOM, computed style, geometry, interaction, interpreter, breakpoints

  • Family: Design system · Main results: color/font/image/radius/spacing/theme/audio/video registries

  • Family: Tables/Content · Main results: schema, records, Views/actions, aggregates, identity, Preview/execution

  • Family: Documents/Document Pages · Main results: blocks/media/Components and route trees/SEO

  • Family: API/Storage/Scripts/Code Components · Main results: typed definitions, source, declarations, calls, mounts

  • Family: Libraries/Environment/Export Settings · Main results: project dependencies, variables, destinations, local export

  • Family: Generated output · Main results: code, diagnostics, PDF/video/training-data, source location

  • Family: Site capture · Main results: crawl/capture, tokens, manifest/build, measurement/diff/refinement

  • Family: Operation discovery · Main results: list/describe/run registered low-level operations

  • Family: Agent guidance · Main results: build playbook, logic format, code-to-design, design-to-code

Required working sequence

  1. list-projects, then select-project in the current session.

  2. Read project/file/node state and resolve current IDs or copied references.

  3. For visual builds, call build-playbook once.

  4. Make one bounded coherent change with the highest-level matching operation.

  5. Read it back and verify structure plus visible/behavioral/generated outcome.

  6. Stop before deletion or external writes unless separately authorized.

Important result differences

  • MCP project selection is not the visible editor selection.

  • UI navigation state has no production MCP counterpart.

  • Preview/diagnostic reads add machine-oriented evidence with no required UI button.

  • run-operation currently supports Component-target operations; other target kinds can return unsupported.

  • dev-* window-driving operations are opt-in repository development tools, not customer authoring capabilities.

  • Whole-file deletion, local/Git output, publishing, package actions, and external data mutations have different recovery from design-file Undo.

Use the UI-to-MCP capability map, prompt guide, and limitations for safe application.

On this page
MCP capabilities
Capability families
Required working sequence
Important result differences