@kadoa/mcp 0.7.2 → 0.7.3

package/README.md

@@ -163,6 +163,7 @@ Point your client to `https://mcp.kadoa.com/mcp` with OAuth authentication.
 |------|-------------|
 | `whoami` | Show current user details, auth method, and team memberships |
 | `team_list` | List all teams you belong to and see which is active |
+| `list_compliance_rules` | Read the compliance rules applied to your team (robots.txt, terms of service, blocked sources, PII, and similar), with each rule's enabled status and configuration. Read-only |
 
 Team switching (a team_switch tool) exists in the code but is currently
 disabled and hidden from every client's tool list — a credential is fixed to
@@ -544,15 +545,13 @@ A typical feature touches three repos — **`kadoa-backend` → `kadoa-sdks` →
 | Backend endpoint | `kadoa-backend/` | The HTTP API. Source of truth; the OpenAPI spec is generated from here. |
 | SDK low-level | `kadoa-sdks/sdks/node/src/generated/api/*` | Auto-generated axios client. Raw HTTP, typed from the OpenAPI spec. **Do not hand-edit.** |
 | SDK domain (high-level) | `kadoa-sdks/sdks/node/src/domains/<thing>/<thing>.service.ts` | Thin domain wrapper over the generated client. `client.<thing>.<action>(...)`. This is what callers use. |
-| CLI | `kadoa-cli/src/commands/<thing>.ts` | Commander action: flag parsing, spinner, table/json output. Calls SDK domain. |
 | MCP (this repo) | `kadoa-mcp/src/tools/<domain>.ts` | Zod input schema + tool description tuned for LLMs. Calls SDK domain. |
 
 Mental model:
 - **SDK** = pure function over HTTP.
-- **CLI** = SDK + human UX (flags, table output).
 - **MCP** = SDK + LLM UX (zod schema, prose description).
 
-CLI and MCP both call **identical** SDK domain methods. A new feature added to the SDK is picked up by both clients for free — as long as we keep the layering honest.
+MCP calls SDK domain methods, never raw HTTP. Any other SDK consumer gets new features for free — as long as we keep the layering honest.
 
 ### Adding a new feature
 
@@ -560,7 +559,7 @@ CLI and MCP both call **identical** SDK domain methods. A new feature added to t
    - Add or modify the HTTP endpoint.
    - Make sure the OpenAPI spec reflects the change (paths, request/response schemas).
 
-2. **SDK** (`kadoa-sdks`) — always do this **before** MCP/CLI work (the SDK-first rule). No bandaid `axios` calls in MCP.
+2. **SDK** (`kadoa-sdks`) — always do this **before** MCP work (the SDK-first rule). No bandaid `axios` calls in MCP.
    - Regenerate the low-level client:
      ```bash
      bun kadoa-codegen fetch-spec -e https://api.kadoa.com/openapi -f
@@ -581,8 +580,6 @@ CLI and MCP both call **identical** SDK domain methods. A new feature added to t
    - If the change intentionally alters a tool's name, title, description, schema, outputSchema or annotations, regenerate the snapshot: `UPDATE_TOOLS_SNAPSHOT=1 BUN_TEST=1 bun test tests/unit/tools-list-snapshot.test.ts`, then `./node_modules/.bin/biome format --write tests/unit/fixtures/tools-list.snapshot.json`. Advertised input and output schemas are normalised by `src/tools/shared/portable-schema.ts` (no `$ref`/`$defs`, `const`, `oneOf`, `additionalProperties`, `$schema`, etc.), so strict clients such as Gemini accept them; zod validation is unchanged.
    - Use a Conventional Commit message (`feat(mcp): ...`, `fix(mcp): ...`). Release Please will cut the next version on merge to `main`.
 
-4. **CLI** (`kadoa-cli`), if the feature is user-facing on the command line: mirror the MCP step in `src/commands/<thing>.ts`. Same SDK call, different UX.
-
 ### Anti-patterns
 
 - ❌ Raw `axios` calls or hand-rolled HTTP in `src/tools/`. Always go through `ctx.client.<thing>`.

package/dist/index.js

@@ -17,7 +17,7 @@ var package_default;
 var init_package = __esm(() => {
   package_default = {
     name: "@kadoa/mcp",
-    version: "0.7.2",
+    version: "0.7.3",
     description: "Kadoa MCP Server — manage workflows from Claude Desktop, Cursor, and other MCP clients",
     type: "module",
     main: "dist/index.js",
@@ -1377,6 +1377,37 @@ var init_assistant = __esm(() => {
   CLOSED_ASSISTANT_STATUSES = new Set(["failed", "errored", "aborted", "timed_out"]);
 });
 
+// src/tools/compliance.ts
+function registerComplianceTools(server, ctx, helpers) {
+  const { withErrorHandling } = helpers;
+  server.registerTool("list_compliance_rules", {
+    title: "List Compliance Rules",
+    description: "List the compliance rules that apply to your team: rule type, name, description, whether it is enabled, and its configuration. " + "Rules are set at the organization level and apply to every team in it. " + "Use this for questions about robots.txt, terms of service, blocked sources or countries, PII handling, captchas, or why a workflow went to compliance review. " + "Read-only: it cannot change rules or grant exceptions; for that, contact Kadoa support.",
+    inputSchema: strictSchema({}),
+    annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false }
+  }, withErrorHandling("list_compliance_rules", async () => {
+    const response = await ctx.client.axiosInstance.get(`/v4/team/${encodeURIComponent(ctx.teamId)}/compliance-rules`, { baseURL: ctx.client.baseUrl });
+    const rules = response.data?.complianceRules;
+    if (!Array.isArray(rules))
+      throw new Error("Unexpected response from the compliance rules API.");
+    return jsonResult({
+      complianceRules: rules.map((rule) => ({
+        ruleType: rule.ruleType,
+        ruleName: rule.ruleName,
+        description: rule.description ?? "",
+        isEnabled: rule.isEnabled,
+        configuration: rule.configuration ?? {},
+        ...rule.updatedAt ? { updatedAt: rule.updatedAt } : {}
+      })),
+      note: rules.length === 0 ? `No compliance rules are configured for your team. ${NO_CHANGES_NOTE}` : NO_CHANGES_NOTE
+    });
+  }));
+}
+var NO_CHANGES_NOTE = "Rules are set by Kadoa for your organization and are read-only here. To change a rule or request an exception, contact Kadoa support.";
+var init_compliance = __esm(() => {
+  init_schemas();
+});
+
 // src/notification-channels.ts
 import { createHash } from "node:crypto";
 function recipientKey(recipients) {
@@ -3997,11 +4028,13 @@ function registerTools(server, ctx, capabilities) {
   registerSupportTools(server, ctx, helpers);
   registerNotificationSettingsTools(server, ctx, helpers);
   registerTeamTools(server, ctx, helpers);
+  registerComplianceTools(server, ctx, helpers);
   registerVariableTools(server, ctx, helpers);
   registerTemplateTools(server, ctx, helpers);
 }
 var init_tools = __esm(() => {
   init_assistant();
+  init_compliance();
   init_notifications();
   init_observability();
   init_scrape();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kadoa/mcp",
-  "version": "0.7.2",
+  "version": "0.7.3",
   "description": "Kadoa MCP Server — manage workflows from Claude Desktop, Cursor, and other MCP clients",
   "type": "module",
   "main": "dist/index.js",