Editor Mcp Server

Created By
playcanvasa year ago
MCP Server for AI automation of the PlayCanvas Editor
Overview

What is PlayCanvas Editor MCP Server?

The PlayCanvas Editor MCP Server is a server designed for AI automation of the PlayCanvas Editor, enabling developers to enhance their workflow with AI-driven features.

How to use PlayCanvas Editor MCP Server?

To use the MCP Server, install the necessary dependencies via npm, set up the Chrome extension, and configure the server with either Claude Desktop or Cursor.

Key features of PlayCanvas Editor MCP Server?

  • AI-driven automation for PlayCanvas Editor
  • Compatibility with Claude Desktop and Cursor
  • Easy installation and setup process

Use cases of PlayCanvas Editor MCP Server?

  1. Automating repetitive tasks in the PlayCanvas Editor.
  2. Enhancing development efficiency with AI assistance.
  3. Streamlining the workflow for game developers using PlayCanvas.

FAQ from PlayCanvas Editor MCP Server?

  • What is required to run the MCP Server?

You need to have Claude Desktop or Cursor installed and configured to use the MCP Server effectively.

  • Is there a recommended subscription for Claude?

Yes, it is recommended to subscribe to a Pro Claude account for better performance and reliability.

  • Can I use the MCP Server without Claude?

No, the MCP Server is designed to be driven by Claude, and its functionality relies on it.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
playcanvas
Star
38
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago