@bettercms-ai/mcp 0.25.1 → 0.26.0

package/dist/index.js

@@ -3306,6 +3306,13 @@ function buildToolDefs(deps) {
         z.object({}).shape,
         async (c) => ok("Conversion brief.", await data(c, "GET", `/management/projects/current/conversion-brief`))
       ),
+      def(
+        "get_conversion_plan",
+        "Get the approved conversion to apply",
+        "The APPROVED conversion a human reviewed in the BetterCMS dashboard: the exact new contents of each template file, already checked against this project's real field paths. Apply it instead of writing the bindings by hand. Check out `baseHeadOid` (the exact commit it was written against \u2014 a plan applied to a different base is a different change), branch from there, write each file's `content` verbatim (whole file, no merge, no reformatting), then push or deploy however this project ships. `stale.head` / `stale.brief` say the repository or the CMS moved since it was approved: stop and ask for a fresh proposal rather than applying it anyway. Finish the loop the same way as a hand conversion \u2014 get_binding_report until `unmatched` is empty, then set_binding_mode { declaredBindings: true } and release once more. 404 with `code: \"no-approved-plan\"` means nobody has approved one: use get_conversion_brief and do the conversion yourself. Requires a project-scoped connection carrying artifact:write.",
+        z.object({}).shape,
+        async (c) => ok("Approved conversion plan.", await data(c, "GET", `/management/projects/current/conversion-plan`))
+      ),
       def(
         "get_analytics_overview",
         "Get traffic overview",
@@ -4314,6 +4321,13 @@ first: it lists those pages, their routes, every bindable path with its current
 value, and the attributes to declare. SKIP steps 3 and 4 below and bind the keys it names \u2014
 registering the schema again builds a second one over the first.
 
+**Or let BetterCMS propose the edit.** \`get_conversion_plan\` returns an APPROVED conversion \u2014 the
+exact new contents of each template file, reviewed by a human in the dashboard and already checked
+against this project's real field paths. When there is one, apply it instead of doing step 5 by
+hand: check out its \`baseHeadOid\`, branch from there, write each file's \`content\` verbatim, and
+carry on from step 6. A 404 with \`code: "no-approved-plan"\` means nobody approved one, so the
+conversion is yours to write.
+
 **The steps.**
 
 1. \`pull_project_source\` (or clone the \`github\` remote it returns). Read the SOURCE. Never