lotux-mcp 0.21.0 → 0.23.0

package/README.md

@@ -61,10 +61,11 @@ Restart Claude, then try: *"list my LOTUX brands"*.
 | `set_beats` / `set_beat_translations` | **Compatibility** for older prompts: a beat list is stored as the script document. Prefer `save_script` |
 | `list_copy` / `create_copy` / `update_copy` / `delete_copy` / `link_copy` / `unlink_copy` / `add_copy_translation` | Ad copy library + concept links. `update_copy` edits in place; `delete_copy` removes it everywhere (status stays app-only) |
 | `list_landing_pages` / `create_landing_page` | A brand's landing pages + the agency pool; link them with `set_concept_fields` |
+| `list_concept_stages` / `move_concept` | The pipeline's stages in board order; move a concept to any of them (copy-check gate applies, Dropbox folder follows) |
 | `iterate_concept` | Spawn a variation ({root}_Var{n}), the same as the app's Iterate button |
 | `list_kb_*` / `get_kb_doc` / `create_kb_doc` / `update_kb_doc` | Kennisbank pages |
 | `content_options` / `create_flywheel` / `update_flywheel` / `list_flywheels` / `get_flywheel` | Content flywheels (Marketing → Content, agency-only): one long-form video. Start with `content_options`; give flywheels a `key` so re-runs reuse them |
-| `push_assets` / `add_asset` / `get_asset` / `list_assets` / `update_asset` / `set_asset_status` / `add_comment` / `delete_asset` | Content assets, upserted on their `key`. Statuses: scripting → production → ready_for_post → post_production → to_review → revisions → approved → live → testing → scaling → turned_off. Content you write lands in `to_review`; Claude can't set revisions, approve, or set live / testing / scaling / turned_off; deleting signed-off work needs `force`. Each asset carries `raw_footage_url` (raw files folder) and `final_asset_url` (the export — a change sends it to review), plus its content ID (`code`) and `name` = `"<code> - <title>"`; pass `code` instead of `asset_id` anywhere |
+| `push_assets` / `add_asset` / `get_asset` / `list_assets` / `update_asset` / `set_asset_status` / `add_comment` / `delete_asset` | Content assets, upserted on their `key`. Statuses: scripting → production → ready_for_post → post_production → to_review → revisions → approved → live → testing → scaling → turned_off. Content you write lands in `to_review`; `set_asset_status` moves a piece to any status (new pieces start in the early ones); deleting signed-off work needs `force`. Each asset carries `raw_footage_url` (raw files folder) and `final_asset_url` (the export — a change sends it to review), plus its content ID (`code`) and `name` = `"<code> - <title>"`; pass `code` instead of `asset_id` anywhere |
 | `get_setup_checks` / `set_setup_check` | A flywheel's setup checklist (Instagram auto-replies, setter replies, reel covers, YouTube, Klaviyo flow) — tick a step by `check_key` after doing it |
 | `list_team` / `get_team_member` / `update_team_member` | HR (agency-only, needs HR access): the team — role, lead, status, dates, KPIs, archive/restore. No pay, no delete, no invites (app only) |
 | `list_job_roles` / `get_job_role` / `update_job_role` / `create_job_role` | HR → Responsibilities: role templates (responsibilities, KPIs, capacity, owned columns). Lists are replaced whole |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lotux-mcp",
-  "version": "0.21.0",
+  "version": "0.23.0",
   "type": "module",
   "description": "Local MCP server that lets Claude create LOTUX concepts (fetch brand-DB entities, create concepts, fill scripts + copy). Talks to the LOTUX app with a personal token; no business logic or secrets live here.",
   "bin": {

package/tools.mjs

@@ -6,7 +6,7 @@
 
 import { z } from "zod";
 
-export const SERVER_INFO = { name: "lotux", version: "0.21.0" };
+export const SERVER_INFO = { name: "lotux", version: "0.22.0" };
 
 export function registerTools(server, rpc) {
   const ok = (result) => ({
@@ -317,6 +317,23 @@ export function registerTools(server, rpc) {
     async ({ account_id }) => ok(await rpc("list_concepts", { account_id }))
   );
 
+  server.tool(
+    "list_concept_stages",
+    "The stages of a brand's concept pipeline in board order (key + name), from Archive and Idea all the way to Testing, Scaling and Turned off. needs_approve = moving there needs approve rights. Use the key or name with move_concept.",
+    { account_id: z.string().describe("Brand id from list_brands") },
+    async ({ account_id }) => ok(await rpc("list_concept_stages", { account_id }))
+  );
+
+  server.tool(
+    "move_concept",
+    "Move a concept to any stage of the pipeline (forward or back, all the way to the end), like dragging its card on the board: stage key or name from list_concept_stages. The copy-check gate still applies (missing fields are listed), the Dropbox folder moves with it and the team gets the usual Slack update.",
+    {
+      concept_id: z.string(),
+      stage: z.string().describe('Stage key ("ready_for_post") or name ("Ready for post")'),
+    },
+    async (args) => ok(await rpc("move_concept", args))
+  );
+
   server.tool(
     "get_concept",
     "Read the full state of one concept by id: fields, linked products/personas/angles/use-cases, scripts (markdown per language + shotlist), and linked copy. Use to confirm what was written.",
@@ -353,7 +370,7 @@ export function registerTools(server, rpc) {
 
   server.tool(
     "create_concept",
-    "Create a new concept in the brand's first (Idea) stage, optionally linking products/personas/angles/offers/use-cases (a concept needs ≥1 product, persona, angle and offer before it can enter Copy check). Returns { id, script_id } — the concept id plus the id of its pre-seeded script (starter template). Write the script with save_script(script_id, body); do NOT add_script for the first script. A human moves the concept through the copy-check gate later in the app.",
+    "Create a new concept in the brand's first (Idea) stage, optionally linking products/personas/angles/offers/use-cases (a concept needs ≥1 product, persona, angle and offer before it can enter Copy check). Returns { id, script_id } — the concept id plus the id of its pre-seeded script (starter template). Write the script with save_script(script_id, body); do NOT add_script for the first script. Move it on later with move_concept.",
     {
       account_id: z.string().describe("Brand id from list_brands"),
       title: z.string(),
@@ -385,6 +402,12 @@ export function registerTools(server, rpc) {
       country: z.string().optional(),
       promotion: z.string().optional(),
       brief: z.string().optional().describe("Concept brief (markdown)"),
+      delivered_date: z
+        .string()
+        .optional()
+        .describe(
+          "YYYY-MM-DD, today or earlier — the day the work was delivered to the client (the drawer's Delivered date; the client delivery dashboard counts by it). The first forward move from before Client approval into it or a later stage stamps today when the date is empty; set this when the work was delivered on another day."
+        ),
       base_language: z.string().optional(),
       sub_buckets: z.array(z.string()).optional(),
       bucket: z.string().optional().describe("Main bucket option key (see list_options.fields)"),
@@ -707,8 +730,8 @@ export function registerTools(server, rpc) {
   // (defaults to your agency). Call content_options first for the allowed values.
 
   const PLATFORMS = ["youtube", "youtube_shorts", "instagram", "tiktok", "linkedin", "x", "email", "meta_ads", "opt_in_page", "google_doc", "internal"];
-  // Statuses follow production. You may set the first five; revisions,
-  // approved, to_launch, live, testing, scaling, turned_off and archived are a human's call.
+  // Statuses follow production. set_asset_status moves to any of them; new
+  // assets (push / update fields) start in the first five only.
   const STATUSES = ["scripting", "production", "ready_for_post", "post_production", "to_review", "revisions", "approved", "to_launch", "live", "testing", "scaling", "turned_off", "archived"];
   const CLAUDE_STATUSES = ["scripting", "production", "ready_for_post", "post_production", "to_review"];
   // video = "To long form".
@@ -893,10 +916,10 @@ export function registerTools(server, rpc) {
 
   server.tool(
     "set_asset_status",
-    "Move an asset through scripting, production, ready_for_post, post_production or to_review (to_review hands it to a human). Revisions, approved, to_launch, live, testing, scaling, turned_off and archived are a human's call in LOTUX.",
+    "Move an asset to any status, all the way to the end: scripting, production, ready_for_post, post_production, to_review (hands it to a human), revisions, approved, to_launch, live, testing, scaling, turned_off, archived. The Dropbox folder follows; approving a lead-magnet page publishes it.",
     {
       ...assetRef,
-      status: z.enum(CLAUDE_STATUSES),
+      status: z.enum(STATUSES),
       comment: z.string().optional().describe("Shown in the asset's activity"),
       account_id: z.string().optional(),
     },