@init-computer/mcp 0.1.6 → 0.1.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -134,7 +134,7 @@ The server uses MCP stdio transport and returns JSON text content for every tool
134
134
 
135
135
  ## Repository init.json integration
136
136
 
137
- 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.
137
+ Use `init_apply_project_file` with an explicit local `init.json` path and an edit request. The MCP server reads that file, edits its project, and overwrites the file with the returned project summary. The current SDK returns an empty `tables` array in that summary, so back up or review any manifest with table definitions before using the file tool. For agents with a parsed document, `init_apply_project_manifest` returns the summary without touching the filesystem.
138
138
 
139
139
  ## Maintaining the public repository
140
140
 
package/bin/init-mcp.js CHANGED
@@ -47,7 +47,7 @@ const tools = [
47
47
  },
48
48
  {
49
49
  name: "init_apply_project_file",
50
- 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.",
50
+ description: "Read an explicit local init.json path, apply an Init project edit, and overwrite the file with the returned project summary. The summary currently has an empty tables array; back up or review manifests with table definitions before using this tool.",
51
51
  inputSchema: objectSchema({ path: stringSchema("Absolute or working-directory-relative init.json path."), prompt: stringSchema("Project change request.") }, ["path", "prompt"]),
52
52
  handler: async ({ path: filePath, prompt }) => {
53
53
  const absolute = path.resolve(filePath);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@init-computer/mcp",
3
- "version": "0.1.6",
3
+ "version": "0.1.7",
4
4
  "description": "Init is a programmable backend platform available through MCP for generating and running backend APIs.",
5
5
  "type": "module",
6
6
  "bin": {
package/server.json CHANGED
@@ -6,12 +6,12 @@
6
6
  "url": "https://github.com/init-computer/init-mcp",
7
7
  "source": "github"
8
8
  },
9
- "version": "0.1.6",
9
+ "version": "0.1.7",
10
10
  "packages": [
11
11
  {
12
12
  "registryType": "npm",
13
13
  "identifier": "@init-computer/mcp",
14
- "version": "0.1.6",
14
+ "version": "0.1.7",
15
15
  "transport": { "type": "stdio" },
16
16
  "environmentVariables": [
17
17
  {