rootr-cli 0.4.1 → 0.6.0

package/README.md

@@ -204,7 +204,7 @@ rootr ask "왜 결제 실패가 늘었지?" --workspace ws_123
 
 ## MCP 서버로 사용하기
 
-`rootr mcp`는 stdio로 MCP(Model Context Protocol) 서버를 구동합니다. 제공 도구 29종:
+`rootr mcp`는 stdio로 MCP(Model Context Protocol) 서버를 구동합니다. 제공 도구 96종:
 
 노드를 가리키는 인자(`target`, `databaseId`, `spreadsheetId`, `formId`, `crmId`, `trackerId`,
 `recordingId`, `presentationId`, `whiteboardId`, `logId`, `parentId` 등)는 **노드 id와 경로를 모두**
@@ -282,6 +282,28 @@ rootr ask "왜 결제 실패가 늘었지?" --workspace ws_123
 | `rootr_create_webhook` | 웹훅 생성 — 응답의 secret은 **1회만 노출** |
 | `rootr_delete_webhook` | 웹훅 삭제 |
 
+#### 표(DATABASE) — 행과 열 (docs:read/docs:write)
+
+| 도구 | 설명 |
+|---|---|
+| `rootr_read_database` | 스키마(열 정의)+행 전체 읽기 — **다른 표 도구를 쓰기 전에 먼저** |
+| `rootr_list_rows` | 행만 조회(스키마 제외) |
+| `rootr_add_row` | 행 추가 (`values`는 열 이름 또는 id로 지정) |
+| `rootr_update_row` | 행 수정 (칸반 카드 이동 = select 열 값 변경) |
+| `rootr_delete_row` | 행 삭제 |
+| `rootr_add_column` | **열 추가** — 기존 열·행은 그대로 |
+| `rootr_update_column` | 열 이름 변경 / select 선택지 교체 |
+| `rootr_delete_column` | 열 삭제(파괴적) |
+
+열은 **한 번에 하나씩** 다룹니다. REST의 `PATCH /databases/:id`는 `properties`
+배열을 통째로 교체하기 때문에, 에이전트가 배열을 다시 만들다 빠뜨린 열이 그대로
+사라집니다. 위 세 도구는 서버가 병합하므로 나머지 열이 없어지지 않습니다.
+
+- **열을 추가해도 기존 행 데이터는 건드리지 않습니다** — 새 열은 값이 채워지기 전까지 빈 칸으로 읽힙니다.
+- **열의 `type`은 바꿀 수 없습니다**(모든 행의 값을 다시 써야 하므로). 새 열을 만들어 값을 옮기세요.
+- `title` 열은 추가로 만들 수도, 삭제할 수도 없습니다.
+- 삭제한 열의 값은 행 안에 남아 있지만 화면에는 나오지 않습니다 — 사용자 확인 후 호출하세요.
+
 #### 문서 버전 / 삭제
 
 | 도구 | 설명 |
@@ -289,10 +311,13 @@ rootr ask "왜 결제 실패가 늘었지?" --workspace ws_123
 | `rootr_document_versions` | 문서 버전 히스토리 조회 |
 | `rootr_delete_node` | 노드를 휴지통으로 이동(복구 가능) |
 
-#### 프레젠테이션 (현재 REST 전용 — 전용 MCP 도구는 예정)
+#### 프레젠테이션
 
-프레젠테이션(PRESENTATION) 노드는 아직 전용 MCP 도구가 없고, **같은 API 키로 REST를
-직접 호출**해 저작합니다 (`x-api-key` 헤더, `docs:write`):
+프레젠테이션(PRESENTATION)은 전용 MCP 도구(`rootr_create_presentation`,
+`rootr_read_presentation`, `rootr_append_presentation_slides`,
+`rootr_update_presentation_slide`, `rootr_reorder_presentation_slides`,
+`rootr_update_presentation`)로 저작합니다. 아래처럼 **같은 API 키로 REST를 직접
+호출**해도 됩니다 (`x-api-key` 헤더, `docs:write`):
 
 ```bash
 # 덱 생성 (슬라이드 포함 가능)
@@ -307,6 +332,33 @@ curl -X POST "$BASE/presentations/$ID/slides"  -d '{"slides":[...]}' ...
 curl -X POST "$BASE/presentations/$ID/reorder" -d '{"order":["SLD-002","SLD-001"]}' ...
 ```
 
+##### 슬라이드에 다이어그램 그려 넣기
+
+구조도·업무 흐름도·순서도·데이터 흐름도·상태도는 손으로 SVG를 짜지 말고
+`rootr_create_diagram_slide`에 **형식이 정해진 JSON 스펙**을 넘기세요. 서버가
+검증하고 그려서 슬라이드에 바로 꽂습니다 — 화면은 물론 PDF·PPTX 내보내기에도
+그대로 나옵니다. 슬라이드의 `diagram`(mermaid) 필드는 **뷰어가 그리지 않으므로**
+이 도구를 쓰는 것이 유일한 방법입니다.
+
+종류마다 스펙 모양이 다르니 **`rootr_diagram_schema`로 스키마와 예제를 먼저
+받아보세요.** 맞지 않는 스펙은 어느 항목이 왜 틀렸는지와 고치는 법을 달아 거절되니,
+그대로 고쳐 다시 부르면 됩니다.
+
+```bash
+# 스펙 모양 보기 (architecture | workflow | sequence | dataflow | lifecycle)
+curl "$BASE/diagram-types/workflow/schema" -H "x-api-key: $KEY"
+
+# 그려서 슬라이드에 꽂기 (slideId를 주면 그 슬라이드를 다시 그린다)
+curl -X POST "$BASE/presentations/$ID/diagram-slides" -H "x-api-key: $KEY" \
+  -H 'Content-Type: application/json' \
+  -d '{"type":"workflow","spec":{...},"title":"이슈는 검수를 통과해야만 main에 들어간다",
+       "blocks":[{"heading":"검수가 관문","body":"..."}]}'
+```
+
+`quality`는 기본 `standard`이고, `showcase`는 손으로 다듬은 대표 그림용 엄격
+기준이라 `standard`가 통과시키는 스펙도 거절합니다. 그림 속 글자는 지식 그래프에
+들어가지 않으니 사실은 `title`·`blocks`·`notes`에도 남기세요.
+
 **고품질 덱을 만들 때는 슬라이드 `html` 필드에 1280×720 완결 HTML을 직접 구워
 넣는 방식을 권장**합니다 — 뷰어가 기본 템플릿 대신 그대로 렌더합니다(완전 자유
 디자인). 필수 규칙(외부 요청 차단이라 전부 인라인, 이미지=data URI 내장, 폰트

package/lib/client.js

@@ -565,6 +565,31 @@ export class RootrClient {
     );
   }
 
+  // ---- DB-COL: one column at a time --------------------------------------
+  // PATCH /databases/:id replaces the whole properties array, so rebuilding it
+  // client-side drops any column left out. These merge server-side instead.
+
+  async addColumn(databaseId, { name, type, options } = {}) {
+    return this.request(`/databases/${encodeURIComponent(databaseId)}/columns`, {
+      method: 'POST',
+      body: { name, type, options },
+    });
+  }
+
+  async updateColumn(databaseId, propertyId, { name, options } = {}) {
+    return this.request(
+      `/databases/${encodeURIComponent(databaseId)}/columns/${encodeURIComponent(propertyId)}`,
+      { method: 'PATCH', body: { name, options } },
+    );
+  }
+
+  async deleteColumn(databaseId, propertyId) {
+    return this.request(
+      `/databases/${encodeURIComponent(databaseId)}/columns/${encodeURIComponent(propertyId)}`,
+      { method: 'DELETE' },
+    );
+  }
+
   // ---- CRM ----------------------------------------------------------------
 
   /** Create a CRM node. pipelines/fields/config optional (server fills sane defaults). */
@@ -852,6 +877,24 @@ export class RootrClient {
     });
   }
 
+  /** Diagram families the server can draw, for discovery. */
+  async diagramTypes() {
+    return this.request('/diagram-types');
+  }
+
+  /** JSON Schema + a worked example for one diagram family. */
+  async diagramSchema(type) {
+    return this.request(`/diagram-types/${encodeURIComponent(type)}/schema`);
+  }
+
+  /** Render a typed diagram spec onto a slide (appends, or replaces slideId). */
+  async createDiagramSlide(presentationId, payload) {
+    return this.request(`/presentations/${encodeURIComponent(presentationId)}/diagram-slides`, {
+      method: 'POST',
+      body: payload,
+    });
+  }
+
   async updatePresentationSlide(presentationId, slideId, slide) {
     return this.request(
       `/presentations/${encodeURIComponent(presentationId)}/slides/${encodeURIComponent(slideId)}`,

package/lib/mcp-tools/databases.js

@@ -171,4 +171,102 @@ export function registerDatabaseTools(server) {
       }
     },
   );
+
+  // ---- DB-COL: columns ----------------------------------------------------
+  // Row tools above cover the data; these cover the SHAPE. Deliberately one
+  // column per call: the underlying PATCH /databases/:id takes the entire
+  // properties array, and a model rebuilding that array drops whatever it
+  // forgets. Here the server merges, so nothing else in the table can be lost.
+
+  server.registerTool(
+    'rootr_add_column',
+    {
+      title: 'Add a column to a database',
+      description:
+        'Add ONE column to a Rootr (루터) DATABASE. The existing columns and every row are left untouched — ' +
+        'rows simply read empty for the new column until you fill them with rootr_update_row. ' +
+        'type ∈ text | number | select | multi_select | date | checkbox | url | person ' +
+        '("title" is not allowed: a database already has exactly one title column). ' +
+        'For select/multi_select pass options: [{ name, color }]. Returns the created column WITH ITS id.',
+      annotations: { readOnlyHint: false, destructiveHint: false },
+      inputSchema: {
+        databaseId: z.string().describe(DATABASE_TARGET_DESC),
+        name: z.string().describe('Column header, e.g. "담당자"'),
+        type: z
+          .enum(['text', 'number', 'select', 'multi_select', 'date', 'checkbox', 'url', 'person'])
+          .describe('Column type'),
+        options: z
+          .array(z.object({ name: z.string(), color: z.string() }))
+          .optional()
+          .describe('select/multi_select only: the choices, e.g. [{ name: "진행중", color: "blue" }]'),
+      },
+    },
+    async ({ databaseId, name, type, options }) => {
+      try {
+        const client = makeClient();
+        const id = await resolveNodeId(client, databaseId);
+        const property = await client.addColumn(id, { name, type, options });
+        return jsonResult({ property });
+      } catch (err) {
+        return errorResult(err);
+      }
+    },
+  );
+
+  server.registerTool(
+    'rootr_update_column',
+    {
+      title: 'Rename a column / set its options',
+      description:
+        'Rename ONE column of a Rootr (루터) DATABASE, and/or replace the choices of a select/multi_select column. ' +
+        'The column TYPE cannot be changed — that would rewrite every row — so add a new column and move the values instead. ' +
+        'Call rootr_read_database first to get the exact propertyId.',
+      annotations: { readOnlyHint: false, destructiveHint: false },
+      inputSchema: {
+        databaseId: z.string().describe(DATABASE_TARGET_DESC),
+        propertyId: z.string().describe('Column id from rootr_read_database (NOT the header text)'),
+        name: z.string().optional().describe('New header text'),
+        options: z
+          .array(z.object({ name: z.string(), color: z.string() }))
+          .optional()
+          .describe('select/multi_select only: REPLACES the full choice list'),
+      },
+    },
+    async ({ databaseId, propertyId, name, options }) => {
+      try {
+        const client = makeClient();
+        const id = await resolveNodeId(client, databaseId);
+        const property = await client.updateColumn(id, propertyId, { name, options });
+        return jsonResult({ property });
+      } catch (err) {
+        return errorResult(err);
+      }
+    },
+  );
+
+  server.registerTool(
+    'rootr_delete_column',
+    {
+      title: 'Delete a column from a database',
+      description:
+        'Remove ONE column from a Rootr (루터) DATABASE. The values stored under it are NOT erased from the rows, ' +
+        'so re-adding a column is not enough to bring them back in the UI — confirm with the user before calling this. ' +
+        'The title column cannot be deleted. Views grouped/dated by the column are cleared automatically.',
+      annotations: { readOnlyHint: false, destructiveHint: true },
+      inputSchema: {
+        databaseId: z.string().describe(DATABASE_TARGET_DESC),
+        propertyId: z.string().describe('Column id from rootr_read_database'),
+      },
+    },
+    async ({ databaseId, propertyId }) => {
+      try {
+        const client = makeClient();
+        const id = await resolveNodeId(client, databaseId);
+        const property = await client.deleteColumn(id, propertyId);
+        return jsonResult({ deleted: true, property });
+      } catch (err) {
+        return errorResult(err);
+      }
+    },
+  );
 }

package/lib/mcp-tools/documents.js

@@ -265,7 +265,9 @@ export function registerDocumentTools(server) {
         'and propose git-style edit suggestions the owner can merge. Publishing is an owner-level action: it needs ' +
         'MANAGE permission, which workspace-scoped keys (including remote-connector tokens) do not carry — use an ' +
         'ACCOUNT key (PAT) of the owner, or ask the user to publish from the share dialog. ' +
-        'Returns the slug/URL. Check rootr_document_public_status first; unpublish via rootr_set_document_public.',
+        'Safe to call again on an already-published document (republish): the public slug/URL never changes, so ' +
+        'links already shared out stay valid — republishing just creates a new published version from the current draft. ' +
+        'Returns the slug/URL. Check rootr_document_public_status first; unpublish or change settings via rootr_set_document_public.',
       annotations: { readOnlyHint: false, destructiveHint: false },
       inputSchema: {
         target: z.string().describe('Document path (starting with "/") or node id'),
@@ -287,19 +289,58 @@ export function registerDocumentTools(server) {
     {
       title: 'Update public settings of a Rootr document',
       description:
-        'Update a published Rootr (루터) document\'s public settings — e.g. {"isPublic": false} to unpublish. ' +
+        'Partially update a published Rootr (루터) document\'s public settings — only the fields you pass are ' +
+        'changed, everything else (including slug) is left as-is. Examples: {"isPublic": false} to unpublish; ' +
+        '{"allowCommits": true} to let public readers propose edits; {"skin": "tech-dark"} or ' +
+        '{"layout": {"cover": true}} to restyle the public page; {"expiresAt": "2026-12-31T00:00:00Z"} to set an ' +
+        'auto-close date, or {"expiresAt": null} to clear it. ' +
         'Owner-level action (MANAGE): works with an account key (PAT), not with workspace-scoped/connector tokens.',
       annotations: { readOnlyHint: false, destructiveHint: false },
       inputSchema: {
         target: z.string().describe('Document path (starting with "/") or node id'),
         isPublic: z.boolean().optional().describe('false to unpublish, true to re-enable'),
+        allowCommits: z.boolean().optional().describe('Whether public readers can propose git-style edit suggestions'),
+        expiresAt: z
+          .union([z.string(), z.null()])
+          .optional()
+          .describe('ISO date to auto-close the public page, or null to clear an existing expiry'),
+        skin: z
+          .enum([
+            'classic',
+            'minimal',
+            'magazine',
+            'paper',
+            'tech-dark',
+            'vivid',
+            'manual',
+            'book',
+            'editorial',
+            'bento',
+            'glass',
+            'mesh',
+            'immersive',
+            'brutal',
+            'neumorph',
+            'y2k',
+          ])
+          .optional()
+          .describe('Visual skin for the public page'),
+        layout: z
+          .object({
+            cover: z.boolean().optional().describe('Show a cover banner'),
+            toc: z.boolean().optional().describe('Show a table of contents'),
+            width: z.enum(['narrow', 'wide']).optional().describe('Body width'),
+            paging: z.boolean().optional().describe('Paginate long documents'),
+          })
+          .optional()
+          .describe('Layout options; only the sub-fields you pass are changed'),
       },
     },
-    async ({ target, isPublic }) => {
+    async ({ target, isPublic, allowCommits, expiresAt, skin, layout }) => {
       try {
         const client = makeClient();
         const id = requireResolved(await resolveTarget(client, target));
-        return jsonResult(await client.setDocumentPublic(id, { isPublic }));
+        return jsonResult(await client.setDocumentPublic(id, { isPublic, allowCommits, expiresAt, skin, layout }));
       } catch (err) {
         return errorResult(err);
       }

package/lib/mcp-tools/presentations.js

@@ -361,4 +361,90 @@ export function registerPresentationTools(server) {
       }
     },
   );
+
+  server.registerTool(
+    'rootr_diagram_schema',
+    {
+      title: 'Get the spec shape for a diagram type',
+      description:
+        'Return the JSON Schema and a worked example for one Rootr (루터) diagram family: architecture (components, ' +
+        'services, stores, boundaries), workflow (swimlane process with approvals/retries), sequence (call order ' +
+        'between participants), dataflow (pipelines, lineage), or lifecycle (states, retries, outcomes). ' +
+        'ALWAYS call this before rootr_create_diagram_slide for a family you have not authored yet — every family ' +
+        'has a different shape (a workflow wants lanes/nodes/edges, an architecture wants components/connections), ' +
+        'and the renderer rejects a spec that does not match. Reading the schema first turns a guess-and-fail into ' +
+        'one correct call. Pass no type to list the available families.',
+      annotations: { readOnlyHint: true },
+      inputSchema: {
+        type: z
+          .enum(['architecture', 'workflow', 'sequence', 'dataflow', 'lifecycle'])
+          .optional()
+          .describe('Diagram family; omit to list the available families'),
+      },
+    },
+    async ({ type }) => {
+      try {
+        const client = makeClient();
+        return jsonResult(type ? await client.diagramSchema(type) : await client.diagramTypes());
+      } catch (err) {
+        return errorResult(err);
+      }
+    },
+  );
+
+  server.registerTool(
+    'rootr_create_diagram_slide',
+    {
+      title: 'Draw a diagram onto a slide',
+      description:
+        'Render a typed diagram spec into a Rootr (루터) presentation slide — architecture, workflow, sequence, ' +
+        'dataflow, or lifecycle. The drawing is baked into the slide, so it shows on screen AND in the PDF/PPTX ' +
+        'exports. Use this instead of the mermaid `diagram` field, which the slide viewer does not draw.\n' +
+        'Call rootr_diagram_schema first to get the exact shape for the family you want — the spec is validated ' +
+        'fail-closed and a mismatch is rejected with the offending field named and a suggested fix, which you ' +
+        'should apply and retry.\n' +
+        'Meaning must live in TEXT: `title` (one assertion-style claim, e.g. "Checkout fails when the cache is ' +
+        'cold" — not a topic label like "Checkout"), `blocks[]`, and `notes` are what connects into the knowledge ' +
+        'graph. The picture itself is NEVER indexed, so never put a fact only in the drawing.\n' +
+        'Pass `slideId` to redraw an existing slide; omit it to append a new one. Quality defaults to "standard"; ' +
+        '"showcase" adds a strict composition bar (turn run-ups, legend fit) meant for a hand-tuned hero diagram ' +
+        'and will reject specs that "standard" accepts.',
+      annotations: { readOnlyHint: false, destructiveHint: false },
+      inputSchema: {
+        presentationId: z.string().describe(`PRESENTATION node id${NODE_TARGET_HINT}`),
+        type: z
+          .enum(['architecture', 'workflow', 'sequence', 'dataflow', 'lifecycle'])
+          .describe('Diagram family — see rootr_diagram_schema'),
+        spec: z.record(z.any()).describe('The typed diagram spec matching that family\'s JSON Schema'),
+        title: z.string().optional().describe('Assertion-style slide title — text spine, also drawn as the heading'),
+        subtitle: z.string().optional().describe('One supporting line drawn under the title'),
+        blocks: z
+          .array(z.object({ heading: z.string().optional(), body: z.string().optional() }).passthrough())
+          .optional()
+          .describe('Text spine — the facts the diagram shows, so they reach the knowledge graph'),
+        notes: z.string().optional().describe('Speaker notes — also part of the text spine'),
+        slideId: z.string().optional().describe('Redraw this slide instead of appending a new one'),
+        quality: z.enum(['standard', 'showcase']).optional().describe('Default "standard"'),
+      },
+    },
+    async ({ presentationId, type, spec, title, subtitle, blocks, notes, slideId, quality }) => {
+      try {
+        const client = makeClient();
+        presentationId = await resolveNodeId(client, presentationId);
+        const result = await client.createDiagramSlide(presentationId, {
+          type,
+          spec,
+          title,
+          subtitle,
+          blocks,
+          notes,
+          slideId,
+          quality,
+        });
+        return jsonResult(result);
+      } catch (err) {
+        return errorResult(err);
+      }
+    },
+  );
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "rootr-cli",
-  "version": "0.4.1",
+  "version": "0.6.0",
   "description": "Official Rootr CLI + MCP server — read, write, edit and search Rootr documents from the shell or from an AI agent.",
   "type": "module",
   "bin": {