jujugrowth-mcp 1.1.0 → 1.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "jujugrowth-mcp",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "description": "MCP server connecting your AI coding assistant (Claude, Cursor, Codex) to jujugrowth — pull your living marketing plan's dev tasks + recommendations and apply them in your repo.",
   "type": "module",
   "bin": {

package/server.mjs

@@ -88,6 +88,27 @@ const TOOLS = [
     run: async (a) =>
       call("GET", `/plan-tasks${a.tenantId ? `?tenantId=${encodeURIComponent(a.tenantId)}` : ""}`),
   },
+  {
+    name: "mark_plan_task_handled",
+    description:
+      "Report a marketing-plan dev-AI task DONE after you've shipped it in the repo. Pass the task's `action` (exactly as returned by list_plan_tasks) and a short `note` of what you changed. jujugrowth records it and the next plan regeneration marks that step done (and stops listing it). ALWAYS call this once a plan task is implemented — it's how the plan knows the work happened. Pass `tenantId` if your token spans more than one site.",
+    inputSchema: {
+      type: "object",
+      properties: {
+        tenantId: { type: "string", description: "the site (required only for multi-site tokens)" },
+        action: { type: "string", description: "the task's action text, exactly as listed" },
+        note: { type: "string", description: "1-3 sentences: what you implemented" },
+      },
+      required: ["action"],
+      additionalProperties: false,
+    },
+    run: async (a) =>
+      call("POST", "/plan-tasks/handled", {
+        action: a.action,
+        ...(a.tenantId ? { tenantId: a.tenantId } : {}),
+        ...(a.note ? { note: a.note } : {}),
+      }),
+  },
   {
     name: "get_recommendation",
     description:
@@ -171,7 +192,7 @@ async function handle(msg) {
           "2) get_recommendation for any rec you'll act on.\n" +
           "3) Before changing anything, VERIFY current-state claims against the actual code — they can be stale; skip what's already done.\n" +
           "4) Implement in the user's repo, scoped to wording/structure/SEO/tracking the plan asks for. Show a diff / open a PR for the user to review.\n" +
-          "5) ALWAYS call mark_recommendation_handled with a short note once a recommendation is shipped — don't wait to be told. (Plan-task progress is reflected automatically by the next plan regeneration's evidence-grounded status.)\n" +
+          "5) ALWAYS report completion once shipped, don't wait to be told: mark_recommendation_handled for a recommendation, or mark_plan_task_handled (with the task's action + a note) for a plan task — that's how the plan learns the work happened and marks the step done.\n" +
           "Campaigns and ad budgets are NOT here — those are owner decisions the jujugrowth system runs itself. This server is bound to ONE site; never act on another.",
       },
     });