scratch-mcp
Related Servers
Alternatives to scratch-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to programmatically edit Scratch .sb3 projects and preview changes live in TurboWarp Desktop via MCP tools and a live-reload bridge.2Mozilla Public 2.0
- AlicenseAqualityAmaintenanceEnables AI clients to create, edit, run, and inspect ScratchJr Desktop projects using natural language, including characters, backgrounds, text, sounds, and programming blocks.17MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to create, compile, and run Scratch projects by editing plain text and using a live editor loop.28 npm1Mozilla Public 2.0
- AlicenseAqualityCmaintenanceEnables AI agents to programmatically edit CapCut Desktop and JianYing Pro projects by directly manipulating native draft files, supporting multi-track timelines, keyframing, transitions, subtitles, and headless previews.24MIT
- AlicenseAqualityCmaintenanceEnables creating real Scratch 3 projects from natural language prompts, producing editable .sb3 files with sprites, scripts, sounds, and backdrops.16MIT
- AlicenseNot gradedqualityCmaintenanceEnables Roblox Studio workflow automation beyond the built-in MCP, including opening places, managing assets via Open Cloud, safe Luau execution, and extracting place contents.MIT
TDQS
Scored across 43 tools
Tools are organized by clear resource categories — project I/O, sprite/target editing, block schemas, comments, assets, VM execution, and screenshots — so an agent can usually tell them apart. The main ambiguity is intentional duplication like screenshot vs screenshot_jpeg and the separate live vs headless run/stop tool pairs, though prefixes help a lot.
The naming is overwhelmingly snake_case verb-first and predictable: open_, save_, list_, get_, set_, add_, remove_, delete_, and the vm_* family. Minor deviations like project_info, scratch_login, and vm_green_flag break the pattern slightly, and delete vs remove is used inconsistently across similar resources.
43 tools is well above the 25+ threshold for a coherent MCP surface, and while each tool has a real purpose, the set feels heavy for agent selection. Several groups (the VM runtime tools, comment tools, asset tools, and screenshot variants) could plausibly be consolidated without losing much capability.
The surface covers the full editing lifecycle for sprites, scripts, variables, lists, comments, costumes, sounds, and project saving with both local and online workflows. Notable gaps include no way to create a brand-new project, list existing online projects, or remove broadcasts, but patch_target provides a low-level workaround for most of these.