loopctl-mcp-server 2.42.0 → 2.43.0

package/index.js

@@ -402,6 +402,17 @@ async function createProject({ name, slug, repo_url, description, tech_stack, mi
   return toContent(result);
 }
 
+async function createKbScope({ name, slug, repo_url, description, tech_stack }) {
+  const body = { name, slug };
+  if (repo_url) body.repo_url = repo_url;
+  if (description) body.description = description;
+  if (tech_stack) body.tech_stack = tech_stack;
+  // Uses the AGENT key (not ORCH): a KB scope is agent-createable on the KB tier — that is
+  // the whole point. The server forces kind: :kb; a body-supplied kind is ignored.
+  const result = await apiCall("POST", "/api/v1/kb-scopes", body, process.env.LOOPCTL_AGENT_KEY);
+  return toContent(result);
+}
+
 async function deleteProject({ project_id }) {
   const result = await apiCall(
     "DELETE",
@@ -2100,6 +2111,25 @@ const TOOLS = [
       required: ["name", "slug"],
     },
   },
+  {
+    name: "create_kb_scope",
+    description:
+      "Create a knowledge-only project scope (kind: kb) for the current tenant. Unlike create_project (work project, orchestrator+ / human-anchored), this is available to an agent-rooted (KB-tier) tenant with an agent key: a kb scope carries NO chain-of-custody / work-breakdown surface (it cannot host epics/stories/dispatch/ui-tests), it exists only to partition knowledge articles by repo so captured/created articles can be project-scoped. Then resolve_project by its repo_url/slug and pass the returned id as project_id on article/knowledge writes. Counts toward the tenant's max_projects budget.",
+    inputSchema: {
+      type: "object",
+      properties: {
+        name: { type: "string", description: "Scope name (often the repo name)." },
+        slug: { type: "string", description: "URL-safe slug (often the repo basename)." },
+        repo_url: {
+          type: "string",
+          description: "Repo URL, so resolve_project can map a repo to this scope.",
+        },
+        description: { type: "string", description: "Scope description." },
+        tech_stack: { type: "string", description: "Tech stack summary." },
+      },
+      required: ["name", "slug"],
+    },
+  },
   {
     name: "delete_project",
     description:
@@ -4860,6 +4890,9 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
     case "create_project":
       return await createProject(args);
 
+    case "create_kb_scope":
+      return await createKbScope(args);
+
     case "delete_project":
       return await deleteProject(args);
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "loopctl-mcp-server",
-  "version": "2.42.0",
+  "version": "2.43.0",
   "description": "MCP server for loopctl — structural trust for AI development loops",
   "type": "module",
   "main": "index.js",