editor-mcp-server and pref-editor-mcp-server

These are ecosystem siblings: the PlayCanvas server enables AI-driven automation of a specific game engine's editor, while the preference editor server provides generic configuration management functionality that could support multiple MCP applications including PlayCanvas workflows.

editor-mcp-server
55
Established
Maintenance 10/25
Adoption 9/25
Maturity 18/25
Community 18/25
Maintenance 6/25
Adoption 2/25
Maturity 18/25
Community 15/25
Stars: 98
Forks: 18
Downloads:
Commits (30d): 0
Language: TypeScript
License: MIT
Stars: 2
Forks: 4
Downloads:
Commits (30d): 0
Language: TypeScript
License: Apache-2.0
No risk flags
No risk flags

About editor-mcp-server

playcanvas/editor-mcp-server

MCP Server for AI automation of the PlayCanvas Editor

Exposes 25+ tools spanning entity/component manipulation, asset management, scripting, material editing, and viewport control through an MCP interface that communicates via a Chrome extension bridge. Built on TypeScript/tsx with stdio transport, it integrates directly with Claude Desktop or Cursor's agent mode, requiring the extension to establish a WebSocket connection between the Editor and the MCP server running locally on a configurable port.

About pref-editor-mcp-server

charlesmuchene/pref-editor-mcp-server

Preference Editor MCP server

Wraps Android Debug Bridge (adb) to expose preference file operations—read, add, modify, and delete—as MCP tools callable by AI clients via stdio transport. Integrates with Claude Desktop, GitHub Copilot, and VS Code through standardized MCP configuration, enabling natural language control of Android app preferences without manual XML editing. Built on the Android Preference Editor library and available as both npm package and Docker image for flexible deployment.

Related comparisons

Scores updated daily from GitHub, PyPI, and npm data. How scores work