lotux-mcp 0.27.0 → 0.29.0

package/README.md

@@ -58,6 +58,7 @@ Restart Claude, then try: *"list my LOTUX brands"*.
 | `set_concept_fields` | Update fields / links / team roles |
 | `save_script` | Write a script: markdown body for one language (`- **Hook:** …`, `- **1:** …`, `- **CTA:** …`), the shotlist, a rename. Pass `language` for a translation |
 | `add_script` / `delete_script` / `remove_script_language` / `set_base_language` | More scripts per concept; language housekeeping |
+| `add_reference` / `delete_reference` | Reference video by link (TikTok / Reels / Shorts); LOTUX saves a copy + Dropbox `00_Reference`. Listed in `get_concept` → `references` |
 | `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` |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lotux-mcp",
-  "version": "0.27.0",
+  "version": "0.29.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

@@ -75,7 +75,7 @@ export function registerTools(server, rpc) {
 
   server.tool(
     "plan_items",
-    "Plan 1–60 items on ONE person's calendar on a date. With start_time they run back to back, each as long as that person's HR output allows (40 h ÷ weekly output; tasks 1 h); without start_time they land all-day. The person becomes the maker (post: video editor on video concepts, static designer on statics) or media buyer (go_live); on a task they are added to the assignees. Planning concept blocks needs Creative edit rights. More than 10 items → returns a PREVIEW only and changes nothing: show the list, ask for a yes, then call apply_planning_preview. Never deletes anything.",
+    "Plan 1–60 items on ONE person's calendar from a date. Concepts (post) without start_time go into that person's day blocks, in the blocks the planner baseline keeps for the concept's client (the client's goal for the week, max clients a day, block changes, meetings and planned work respected), starting on the date and continuing on the next working days up to the planning horizon. Concepts that don't fit (goal covered, person not on the client's team, not ready, someone else's) stay in the Unplanned Log and come back in not_planned with the reason: tell the user. With start_time they run back to back from that time instead, each as long as that person's HR output allows (40 h ÷ weekly output; tasks 1 h); all_day: true = all-day. go_live and tasks without start_time land all-day. The person becomes the maker (post: video editor on video concepts, static designer on statics) or media buyer (go_live); on a task they are added to the assignees. Planning concept blocks needs Creative edit rights. More than 10 items → returns a PREVIEW only and changes nothing: show the list, ask for a yes, then call apply_planning_preview. Never deletes anything.",
     {
       person: z.string().describe("id, name or 'me'"),
       items: PLAN_ITEMS,
@@ -348,7 +348,7 @@ export function registerTools(server, rpc) {
 
   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.",
+    "Read the full state of one concept by id: fields, linked products/personas/angles/use-cases, references (the videos it is based on), scripts (markdown per language + shotlist), and linked copy. Use to confirm what was written.",
     { concept_id: z.string() },
     async ({ concept_id }) => ok(await rpc("get_concept", { concept_id }))
   );
@@ -476,6 +476,23 @@ export function registerTools(server, rpc) {
     async (args) => ok(await rpc("save_script", args))
   );
 
+  server.tool(
+    "add_reference",
+    "Add a reference (the video a concept is based on) by link: TikTok, Instagram Reels, Facebook Reels or YouTube Shorts (any other link is kept as a plain link). For TikTok / Instagram / Facebook LOTUX saves its own copy (usually under a minute) and puts it in the concept's Dropbox folder under 00_Reference. The first reference is the main one. Video FILES can't be sent here — upload those in the app.",
+    {
+      concept_id: z.string(),
+      url: z.string().describe("Full link to the video, e.g. https://www.instagram.com/reel/ABC123/"),
+    },
+    async (args) => ok(await rpc("add_reference", args))
+  );
+
+  server.tool(
+    "delete_reference",
+    "Remove a reference from its concept (id from get_concept → references). Also deletes LOTUX's saved copy and the file in the concept's Dropbox 00_Reference folder. Irreversible in LOTUX (Dropbox keeps deleted files in its trash for 30 days).",
+    { reference_id: z.string() },
+    async ({ reference_id }) => ok(await rpc("delete_reference", { reference_id }))
+  );
+
   server.tool(
     "add_script",
     "Add another script to a concept (every concept already has one — use save_script on it first). Returns the new script (starter template in the base language).",