pixel-composer-mcp
Related Servers
Alternatives to pixel-composer-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to automate the PlayCanvas Editor by managing projects, entities, assets, scripts, scenes, builds, and runtime sessions, and by verifying scenes through launching and capturing screenshots.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to automate the PlayCanvas Editor, managing entities, scripts, assets, scenes, builds, and viewport state, and to launch and inspect running scenes with screenshots, logs, and input simulation.-
- AlicenseAqualityAmaintenanceEnables AI agents to operate the Unreal Editor via MCP: reading, creating, and editing blueprints at the node level, authoring materials and UMG widgets, auditing projects, and verifying runtime behavior in PIE with read-back checks.341Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to automate the PlayCanvas Editor for project, entity, script, asset, scene, build, and runtime control, and to launch and inspect scenes to confirm they work.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to drive the PlayCanvas Editor directly, letting them create and edit entities, scripts, assets, templates, scenes, builds and project settings, then launch the game and inspect it through screenshots, logs and input to confirm scenes actually run.-
- AlicenseAqualityAmaintenanceEnables AI agents to read, edit, and render Compositor .comp projects, including layer inspection, image manipulation, and preview.1576 npm8MIT
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes: open_project launches the app, inspect_project reads the file, set_input mutates a node value, export runs export nodes, status reports connection, close quits. The only overlapping pair is set_input vs run_command, since a raw console command could also modify values, but the descriptions clarify that set_input targets node inputs specifically.
Most names follow a verb_noun pattern (open_project, inspect_project, set_input, run_command), with minor deviations where export, status, and close are bare verbs/nouns. The convention is still predictable and readable throughout.
Seven tools is well-scoped for a Pixel Composer control server, covering lifecycle (open/close/status), inspection, mutation, and export without padding. Each tool earns its place.
Lifecycle, inspection, mutation, and export are all covered, and run_command provides an escape hatch for anything missing (node creation, connections, GML calls). Some first-class operations like creating nodes or editing connections are absent, but the console fallback mitigates this.