@endiagram/mcp 0.2.23 → 0.2.25

package/dist/index.js

@@ -74,10 +74,20 @@ for (const tool of toolsConfig.tools) {
                     isError: result.isError,
                 };
             }
-            const outDir = join(process.cwd(), ".endiagram");
-            if (!existsSync(outDir))
-                mkdirSync(outDir, { recursive: true });
-            const filePath = join(outDir, `en-${Date.now()}.svg`);
+            const outputPath = args.output;
+            let filePath;
+            if (outputPath) {
+                const dir = dirname(outputPath);
+                if (!existsSync(dir))
+                    mkdirSync(dir, { recursive: true });
+                filePath = outputPath;
+            }
+            else {
+                const outDir = join(process.cwd(), ".endiagram");
+                if (!existsSync(outDir))
+                    mkdirSync(outDir, { recursive: true });
+                filePath = join(outDir, `en-${Date.now()}.svg`);
+            }
             writeFileSync(filePath, result.svg);
             return {
                 content: [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@endiagram/mcp",
-  "version": "0.2.23",
+  "version": "0.2.25",
   "description": "MCP server for EN Diagram — deterministic structural analysis backed by named theorems",
   "type": "module",
   "main": "dist/index.js",

package/tools.json

@@ -1,5 +1,5 @@
 {
-  "instructions": "EN Diagram is a structural verification engine for concurrent systems. No AI inside.\n\nTo describe a system, write one statement per line:\n  actor do: action needs: input1, input2 yields: output1, output2 at: context\n\nShared names between yields and needs create connections automatically. Multi-word names work fine. Use commas to separate multiple inputs or outputs. at: scopes the action to a context (service, team, region, domain, layer — whatever boundary fits the system).\n\nSix tools answer six questions from concurrency theory. Each answer includes who (actors) and where (locations) alongside the structural findings.\n\n1. structure — what is this system?\n2. invariant — what's always true?\n3. live — can it deadlock? can entities overflow?\n4. reachable — can X reach Y?\n5. equivalent — are two systems the same?\n6. compose — how do parts combine?\n\nEvery tool output contains node names, values, and structural properties that can be fed directly into other tools. Read the output. Find the surprising node, the unexpected value, the structural anomaly. Then pick the tool that investigates THAT specific finding.\n\nDo not stop at one tool call. The first call reveals the structure — the real insight comes from the second, third, fourth call that digs into what the first one found.\n\nSpeak in the user's domain, not in graph theory. Only call render when the user explicitly asks to visualize.",
+  "instructions": "EN Diagram is a structural verification engine for concurrent systems. No AI inside.\n\nTo describe a system, write one statement per line:\n  actor do: action needs: input1, input2 yields: output1, output2 at: context\n\nEvery statement requires: actor, do:, needs:, and yields:. Shared names between yields and needs create connections automatically. Multi-word names work fine. Use commas to separate multiple inputs or outputs. at: scopes the action to a context (service, team, region, domain, layer — whatever boundary fits the system).\n\nSix tools answer six questions from concurrency theory. Each answer includes who (actors) and where (locations) alongside the structural findings.\n\n1. structure — what is this system?\n2. invariant — what's always true?\n3. live — can it deadlock? can entities overflow?\n4. reachable — can X reach Y?\n5. equivalent — are two systems the same?\n6. compose — how do parts combine?\n\nEvery tool output contains node names, values, and structural properties that can be fed directly into other tools. Read the output. Find the surprising node, the unexpected value, the structural anomaly. Then pick the tool that investigates THAT specific finding.\n\nDo not stop at one tool call. The first call reveals the structure — the real insight comes from the second, third, fourth call that digs into what the first one found.\n\nSpeak in the user's domain, not in graph theory. Only call render when the user explicitly asks to visualize.",
   "tools": [
     {
       "name": "structure",
@@ -62,7 +62,8 @@
       "parameters": [
         {"name": "source", "type": "string", "description": "EN source code describing the system", "required": true},
         {"name": "theme", "type": "string", "description": "Color theme: dark or light", "required": false},
-        {"name": "quality", "type": "string", "description": "Output quality: small, mid, or max", "required": false}
+        {"name": "quality", "type": "string", "description": "Output quality: small, mid, or max", "required": false},
+        {"name": "output", "type": "string", "description": "File path to save the SVG", "required": false}
       ]
     }
   ]