PlayCanvas Editor
A PlayCanvas Editor interface that enables AI assistants to interact with the PlayCanvas game engine through WebSockets. This server implementation provides tools for managing entities, assets, materials, scripts, and scene settings in PlayCanvas projects. It establishes a bidirectional communication channel between the PlayCanvas Editor and external tools, allowing for programmatic creation, modification, and deletion of game objects and assets. The implementation includes a Chrome extension that injects a WebSocket client into the PlayCanvas Editor page, making it particularly valuable for automating workflows, rapid prototyping, and AI-assisted game development tasks.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.
Scan details: Circle-IR · 2026-09-28 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- productivity
- Source
- PulseMCP
- Repository
- github.com/playcanvas/editor-mcp-server
- Author type
- human
- Last scanned
- 2026-09-28
- Updated
- 2026-09-28
Use via MCP
Resolve PlayCanvas Editor from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.