breakpoint-mcp 1.2.0 → 1.2.1

package/README.md

@@ -15,10 +15,28 @@ architecture.
 
 ## Install
 
+The fastest path — from your Godot project folder, one command installs and enables the
+editor addon (bundled in this package) and prints your MCP-client config:
+
+```bash
+npx breakpoint-mcp init
+```
+
+Then open the project in Godot and verify the setup:
+
+```bash
+npx breakpoint-mcp doctor
+```
+
+`init` copies the addon into `addons/breakpoint_mcp/`, enables it in `project.godot`, and
+prints — or, with `--client claude-code|claude-desktop|cursor|windsurf|vscode`, writes —
+the client config. `doctor` checks the Godot binary, the addon, and the four bridges
+(add `--require-live` once the editor is open; `--json` for a machine-readable report).
+
+To install the `breakpoint-mcp` command globally instead of invoking it via `npx`:
+
 ```bash
-npx breakpoint-mcp          # run on demand
-# or
-npm i -g breakpoint-mcp     # install the `breakpoint-mcp` command
+npm i -g breakpoint-mcp
 ```
 
 Requires **Node ≥ 18**. The host targets the `@modelcontextprotocol/sdk` `1.x` line
@@ -60,10 +78,11 @@ section for each client's config file and format.
 
 ## The addon (required for the editor / runtime planes)
 
-Install the `breakpoint_mcp` editor addon into your Godot project (drop
-`addons/breakpoint_mcp/` in and enable it under Project Settings → Plugins). It opens the
-loopback servers this host connects to and auto-registers the in-game runtime bridge.
-Without it, only the headless-CLI (`godot_*`) plane works.
+`breakpoint-mcp init` installs and enables this for you — the editor addon ships **inside
+this package**, so you don't need the repository to get it. To do it by hand instead, copy
+`addons/breakpoint_mcp/` into your project and enable it under Project Settings → Plugins.
+Either way it opens the loopback servers this host connects to and auto-registers the
+in-game runtime bridge; without it, only the headless-CLI (`godot_*`) plane works.
 
 ## Local-first
 

package/addon/breakpoint_mcp/plugin.cfg

@@ -3,5 +3,5 @@
 name="Breakpoint MCP"
 description="Exposes the live Godot editor and the running game to an MCP host so an AI assistant can drive them: scene/node/resource CRUD with full undo/redo, project settings, ClassDB, editor + in-game screenshots, and an in-game runtime bridge (live SceneTree, property get/set, method calls, signals, input injection, Performance monitors). Pairs with the breakpoint-mcp MCP host."
 author="James Livingston"
-version="1.2.0"
+version="1.2.1"
 script="plugin.gd"

package/dist/index.js

@@ -43,7 +43,7 @@ async function main() {
     // so long jobs (export/import/headless script) support poll/await/cancel.
     // D3: also advertise resources.subscribe so clients can subscribe to
     // godot://… resources and receive notifications/resources/updated.
-    const server = new McpServer({ name: "breakpoint-mcp", version: "1.2.0" }, { capabilities: { ...TASK_CAPABILITIES, ...RESOURCE_CAPABILITIES }, taskStore });
+    const server = new McpServer({ name: "breakpoint-mcp", version: "1.2.1" }, { capabilities: { ...TASK_CAPABILITIES, ...RESOURCE_CAPABILITIES }, taskStore });
     // B1: enforce frozen output schemas on every structured tool. Must run before
     // the register*Tools calls below — it wraps server.registerTool.
     applyOutputSchemas(server);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "breakpoint-mcp",
-  "version": "1.2.0",
+  "version": "1.2.1",
   "description": "MCP server exposing Godot to AI coding assistants over the Model Context Protocol — developed and tested with Claude — across four planes (CLI, live editor, LSP+DAP, runtime) with elicitation-gated destructive tools, long jobs on the formal MCP task model, captured console output, and MCP resources.",
   "type": "module",
   "license": "MIT",