mBlock MCP
Related Servers
Alternatives to mBlock MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI clients to create, edit, run, and inspect ScratchJr Desktop projects using natural language, including characters, backgrounds, text, sounds, and programming blocks.17MIT
- AlicenseBqualityBmaintenanceEnables MCP clients to drive a live MIT App Inventor editor session: create and import projects, add and configure components, write and diagnose Blockly code, apply layout specs, validate results, compile an APK, and install and test it on an emulator with UI assertions. Every edit goes through the real editor and is read back for verification, so App Inventor remains the source of truth.13MIT
- AlicenseAqualityDmaintenanceEnables LLMs to interact with MIT App Inventor, AndroidBuilder, Kodular, or Niotron IDEs in real-time, controlling the Designer and Blocks workspace via Chrome DevTools Protocol.101MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to programmatically edit Scratch .sb3 projects and preview changes live in TurboWarp Desktop via MCP tools and a live-reload bridge.3Mozilla Public 2.0
- AlicenseBqualityBmaintenanceEnables an agent to drive the Bambu Lab CyberBrick desktop app over the Chrome DevTools Protocol, covering the whole device setup workflow — planning hardware connections, authoring and reading firmware configuration, managing projects, and flashing firmware, MPY and config files to boards.4150 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI clients to control Cocos Creator editor projects, scenes, nodes, components, assets, Prefabs, building, and diagnostics via the MCP protocol.-
TDQS
Scored across 36 tools
Each tool targets a distinct operation—project management, block manipulation, live app control, or asset listing. Overlaps like add_script vs add_block vs app_put_script are clearly differentiated by context (file-based vs live bridge). No two tools serve the same purpose.
Naming is inconsistent: some tools use hyphens (project-validate, project-list, bridge-files) while others use underscores (list_targets, get_block, add_script). Verb styles also vary (list, get, add, set, delete, move, rename, export, import, run, put). Not a predictable pattern.
With 36 tools, the server is over-scoped for an MCP surface. Even though it covers a broad domain, the count exceeds the 25+ threshold for 'too many'. Many tools are narrow (e.g., app_sensor_snapshot, list_costumes), contributing to bloat.
The server covers project lifecycle (new, open, duplicate, archive, validate), block/script editing (add, delete, move, set, get), and live app integration (put, run, read vars, get code). Minor gaps exist—no project deletion or block field retrieval—but core workflows are well-supported.