@init-computer/mcp 0.1.2 → 0.1.3

package/README.md

@@ -120,4 +120,8 @@ Inspect available runtime packages and enabled connections. Filter by `category`
 
 ## Protocol behavior
 
-The server uses MCP stdio transport and returns JSON text content for every tool call. It does not upload local files, read repository secrets, or manage a local project directory. Use the CLI for terminal workflows and the SDK for application code.
+The server uses MCP stdio transport and returns JSON text content for every tool call. It does not upload repository secrets; its file tool reads and writes only the explicit `init.json` path supplied to it.
+
+## Repository init.json integration
+
+Use `init_apply_project_file` with an explicit local `init.json` path and an edit request. The MCP server reads that one file, finds `project.id`, applies the edit to the matching Init project, and writes the canonical contract back to the same path. For agents that already have a parsed document, use `init_apply_project_manifest`; it returns the updated `initJson` without touching the filesystem.

package/bin/init-mcp.js

@@ -1,4 +1,6 @@
 #!/usr/bin/env node
+import fs from "node:fs";
+import path from "node:path";
 import readline from "node:readline";
 import { InitApiError, createClient } from "../../sdk/dist/index.js";
 
@@ -34,6 +36,24 @@ const tools = [
 		inputSchema: objectSchema({ project_id: stringSchema("Project id."), prompt: stringSchema("Project change request.") }, ["project_id", "prompt"]),
 		handler: ({ project_id, prompt }) => client.project.edit(project_id, { prompt }),
 	},
+	{
+		name: "init_apply_project_manifest",
+		description: "Create a project from init.json, or apply an edit to the project identified by its init.json and return its updated canonical contract.",
+		inputSchema: objectSchema({ manifest: freeObjectSchema("The parsed init.json document."), prompt: optionalStringSchema("Change request when the manifest belongs to an existing project.") }, ["manifest"]),
+		handler: ({ manifest, prompt }) => client.project.applyInitJson(manifest, { prompt }),
+	},
+	{
+		name: "init_apply_project_file",
+		description: "Read an explicit local init.json path, apply an Init project edit, and write the returned canonical init.json back to that same path.",
+		inputSchema: objectSchema({ path: stringSchema("Absolute or working-directory-relative init.json path."), prompt: stringSchema("Project change request.") }, ["path", "prompt"]),
+		handler: async ({ path: filePath, prompt }) => {
+			const absolute = path.resolve(filePath);
+			const manifest = JSON.parse(fs.readFileSync(absolute, "utf8"));
+			const output = await client.project.applyInitJson(manifest, { prompt });
+			fs.writeFileSync(absolute, `${JSON.stringify(output.initJson, null, 2)}\n`, "utf8");
+			return { ...output.result, initJsonPath: absolute, initJsonUpdated: true };
+		},
+	},
   {
     name: "init_run",
     description: "Call a generated Init API route.",

package/package.json

@@ -1,13 +1,13 @@
 {
   "name": "@init-computer/mcp",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Init is a programmable backend platform available through MCP for generating and running backend APIs.",
   "type": "module",
   "bin": {
-    "init-mcp": "./bin/init-mcp.js"
+    "init-mcp": "bin/init-mcp.js"
   },
   "dependencies": {
-    "@init-computer/sdk": "0.1.5"
+    "@init-computer/sdk": "0.1.6"
   },
   "engines": {
     "node": ">=18"