@wootsup/yt-builder-mcp 2.0.0 → 2.1.0

package/package.json

@@ -1,17 +1,12 @@
 {
     "name": "@wootsup/yt-builder-mcp",
-    "version": "2.0.0",
+    "version": "2.1.0",
     "type": "module",
-    "description": "YT Builder MCP — drive your page builder from Claude, Cursor, Codex, Gemini and 5 other MCP-capable AI assistants. Built for YOOtheme Pro 4.0+. Independent third-party project, not affiliated with YOOtheme GmbH.",
+    "description": "MCP for YOOtheme Pro — drive your page builder from Claude, Cursor, Codex, Gemini and 5 other MCP-capable AI assistants. Built for YOOtheme Pro 4.0+. Independent third-party project, not affiliated with YOOtheme GmbH.",
     "license": "MIT",
     "author": "WootsUp <hello@wootsup.com>",
     "homepage": "https://wootsup.com",
-    "repository": {
-        "type": "git",
-        "url": "git+https://github.com/wootsup/yt-builder-mcp.git",
-        "directory": "packages/mcp"
-    },
-    "bugs": "https://github.com/wootsup/yt-builder-mcp/issues",
+    "bugs": "https://wootsup.com/contact/",
     "keywords": [
         "mcp",
         "model-context-protocol",
@@ -45,10 +40,10 @@
         "access": "public"
     },
     "engines": {
-        "node": ">=20.13.0"
+        "node": ">=22.15.0"
     },
     "scripts": {
-        "prepublishOnly": "node -e \"if (process.env.RELEASE_PHP_PUBLISH !== '1') { console.error('Manual npm publish is no longer supported. Use: php scripts/release.php release yt-builder-mcp <bump> followed by php scripts/release.php push-tag yt-builder-mcp <version>, which triggers the GitHub Actions publish workflow (.github/workflows/yt-builder-mcp-publish.yml). Set RELEASE_PHP_PUBLISH=1 only if you know you are running from that workflow.'); process.exit(1); }\" && node ./scripts/prepublish-floor-check.mjs",
+        "prepublishOnly": "node -e \"if (process.env.RELEASE_PHP_PUBLISH !== '1') { console.error('Manual npm publish is no longer supported. Use: php scripts/release.php release yt-builder-mcp <bump> followed by php scripts/release.php push-tag yt-builder-mcp <version>, which triggers the automated publish workflow. Set RELEASE_PHP_PUBLISH=1 only if you know you are running from that workflow.'); process.exit(1); }\" && node ./scripts/prepublish-floor-check.mjs",
         "build": "tsc",
         "dev": "tsc --watch",
         "test": "vitest run",

package/skills/yt-builder-mcp/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: yt-builder-mcp
-description: Drive the YOOtheme Pro Page Builder on WordPress or Joomla 5/6. Discover pages, inspect layouts, add/move/clone/delete elements, bind dynamic sources, diagnose 401/403 auth failures. Use when the user works with a YOOtheme Pro site via the YT Builder MCP server.
+description: Drive the YOOtheme Pro Page Builder on WordPress or Joomla 5/6. Discover pages, inspect layouts, add/move/clone/delete elements, bind dynamic sources, diagnose 401/403 auth failures. Use when the user works with a YOOtheme Pro site via the MCP for YOOtheme Pro server.
 ---
 
-# YT Builder MCP for YOOtheme Pro (unofficial). Skill
+# MCP for YOOtheme Pro. Skill
 
 > Independent third-party project. YOOtheme® is a registered trademark of YOOtheme GmbH
-> ([yootheme.com](https://yootheme.com)). YT Builder MCP is built by WootsUp (getimo
+> ([yootheme.com](https://yootheme.com)). MCP for YOOtheme Pro is built by WootsUp (getimo
 > productions) and is not affiliated with, endorsed by, or sponsored by YOOtheme.
 > The integration uses YOOtheme Pro's public extension points and works on both
 > WordPress and Joomla 5/6.
@@ -22,10 +22,10 @@ tools reachable through the gateways. The write-capable
 (inspect_sublayout, layout_query, local_content_types,
 local_content_read, pages_audit, heading_outline, navigation) and is itself
 read-only-annotated, so MCP hosts can auto-allow pure inspection without a
-per-call write-approval prompt. This 3-lane split exists because Cursor (and
-similar hosts) cap a server at roughly 40 first-class `tools/list` entries —
-it keeps the advertised surface small while every catalogued tool stays
-fully reachable through the gateways.
+per-call write-approval prompt. The 3-lane split keeps the advertised
+surface smaller than the reachable one, which matters for AI clients that
+handle long tool lists poorly; every catalogued tool stays fully reachable
+through the gateways either way.
 
 ## How to use this MCP server
 
@@ -37,10 +37,10 @@ Joomla 5/6 host plugin:
 1. The user installs the host plugin for their CMS:
    - **WordPress**. Install the `yt-builder-mcp` plugin (download + install guide
      at [wootsup.com/docs](https://wootsup.com/docs/mcp/yootheme-wordpress/installation))
-     and generate a Bearer key in **wp-admin → Tools → "YT Builder MCP" → Bearer Keys**.
+     and generate a Bearer key in **wp-admin → Tools → "MCP for YOOtheme Pro" → Bearer Keys**.
    - **Joomla 5/6**. Install the `yt-builder-mcp` package (download + install guide
      at [wootsup.com/docs](https://wootsup.com/docs/mcp/yootheme-joomla/installation))
-     and generate a Bearer key in **Components → YT Builder MCP → Bearer Keys**. The package
+     and generate a Bearer key in **Components → MCP for YOOtheme Pro → Bearer Keys**. The package
      installs three sub-extensions (system plugin, webservices plugin, component).
 2. The user runs `npx -y @wootsup/yt-builder-mcp setup` once; the wizard probes
    the host plugin, validates the key, and writes the MCP server entry into every
@@ -53,14 +53,14 @@ Joomla 5/6 host plugin:
 ### Two picker entries (activate both)
 
 Some clients (notably Claude Desktop with the `.mcpb` bundle) expose **two**
-entries when the user types "YT Builder MCP" into the picker:
+entries when the user types "MCP for YOOtheme Pro" into the picker:
 
-- **`YT Builder MCP for YOOtheme Pro (unofficial)`**: the MCP **server**.
+- **`MCP for YOOtheme Pro`**: the MCP **server**.
   Provides the 49 first-class tools (45 essential, 2 direct, 2 gateways).
   The `yootheme_builder_advanced` gateway routes all 13 advanced tools; the
   read-only `yootheme_builder_advanced_read` gateway routes the read-only
   subset without a write-approval prompt.
-- **`Von YT Builder MCP for YOOtheme Pro`**: the bundled **skill** (this
+- **`Von MCP for YOOtheme Pro`**: the bundled **skill** (this
   document). Gives the agent the workflow knowledge needed to drive those
   tools correctly on first try.
 
@@ -637,7 +637,7 @@ Do not loop on auth errors.
 
 > **Joomla note.** On the Joomla API surface (`com_api`), the Bearer token's
 > scope is the **sole** authority. The L2 article-write `core.edit` ACL gate
-> was intentionally removed (see ADR at https://github.com/wootsup/yt-builder-mcp/blob/main/docs/adr/2026-05-24-l2-bearer-as-authority.md).
+> was intentionally removed.
 > Joomla ACL still governs the admin component (`com_ytbmcp`). On WordPress,
 > capabilities like `manage_options` gate the admin settings page only; the
 > REST API surface is Bearer-gated.
@@ -2497,9 +2497,9 @@ guessing, and without rotating the user's key unnecessarily.
 2. **Interpret the result:**
    - **The call itself failed** (a transport error, not a payload) → the
      WordPress / Joomla install is down OR the host plugin is deactivated.
-     Send the user to **wp-admin → Plugins → activate "YT Builder MCP"**
+     Send the user to **wp-admin → Plugins → activate "MCP for YOOtheme Pro"**
      (WordPress) or **Joomla administrator → Extensions → Plugins → enable
-     "System - YT Builder MCP" and the matching webservices + component
+     "System - MCP for YOOtheme Pro" and the matching webservices + component
      entries** (Joomla). Do not retry until they confirm.
    - `auth_bound: false` → the Bearer key is wrong (typo, revoked, or wrong
      key for this install). Check `site_url` first: a key that is valid
@@ -2508,10 +2508,10 @@ guessing, and without rotating the user's key unnecessarily.
      probes `/etag` itself and answers `bearer_valid` + `summary`; diagnose
      names no status of its own, because the request it is answering already
      got through. Then send the user to:
-     - **WordPress:** wp-admin → Tools → "YT Builder MCP" → Bearer Keys
+     - **WordPress:** wp-admin → Tools → "MCP for YOOtheme Pro" → Bearer Keys
        → copy the existing key into their MCP client config, or
        generate a new one.
-     - **Joomla:** Components → YT Builder MCP → Bearer Keys → same.
+     - **Joomla:** Components → MCP for YOOtheme Pro → Bearer Keys → same.
    - `auth_bound: true, etag_ok: true` but the original
      tool returned a 403 → the key works but the scope is too low for
      the tool's required scope (`write` for mutations, `admin` for
@@ -2526,8 +2526,8 @@ guessing, and without rotating the user's key unnecessarily.
      rights, or grant that user the capability. A write-scoped token
      alone is not enough.
 3. **Walk the user through key rotation if needed:**
-   - WordPress: "wp-admin → Tools → YT Builder MCP → Bearer Keys."
-     Joomla: "Components → YT Builder MCP → Bearer Keys."
+   - WordPress: "wp-admin → Tools → MCP for YOOtheme Pro → Bearer Keys."
+     Joomla: "Components → MCP for YOOtheme Pro → Bearer Keys."
    - "Click 'Generate New Key', pick the scope (admin for full access)."
    - "Copy the key. It's shown ONCE; you cannot recover it later."
    - "Update your AI client config: replace `YTB_MCP_BEARER_TOKEN`
@@ -2574,7 +2574,7 @@ yootheme_builder_diagnose({})
 //   site_url: "https://example.com",   // ← check this FIRST: right key, wrong install?
 //   active_site: { site_id: "default", via: "registry_default", process_scoped: true }
 // }
-// → diagnosis: rotate the key. Send user to Tools/Components → YT Builder MCP.
+// → diagnosis: rotate the key. Send user to Tools/Components → MCP for YOOtheme Pro.
 // → for the upstream HTTP status: yootheme_builder_sites_test({ site_id: "default" }).
 ```