mcp-zenskar 1.2.0 → 1.3.0

package/README.md

@@ -279,6 +279,9 @@ cd mcp-zenskar
 # Install dependencies
 npm install
 
+# Build the bundle (produces dist/server.mjs + dist/mcp-config.json)
+npm run build
+
 # Run the server
 npm start
 ```
@@ -288,19 +291,20 @@ npm start
 If you want Claude Desktop to use a local checkout instead of the npm package:
 
 ```bash
-# Install dependencies once
+# Install dependencies + build the bundle
 npm install
+npm run build
 
-# Optional: install the local build globally
+# Optional: install the local build globally (requires dist/ from the previous step)
 npm install -g .
 ```
 
-Then either point Claude to the globally-installed binary (usually `$(npm bin -g)/mcp-zenskar`) or call the repo copy directly:
+Then either point Claude to the globally-installed binary (usually `$(npm bin -g)/mcp-zenskar`) or call the built bundle directly:
 
 ```json
 {
   "command": "node",
-  "args": ["/absolute/path/to/mcp-zenskar/src/server.js"],
+  "args": ["/absolute/path/to/mcp-zenskar/dist/server.mjs"],
   "env": {
     "ZENSKAR_ORGANIZATION": "your-org-id",
     "ZENSKAR_AUTH_TOKEN": "your-token"
@@ -308,6 +312,15 @@ Then either point Claude to the globally-installed binary (usually `$(npm bin -g
 }
 ```
 
+To iterate on `src/server.js` without rebuilding, run it directly — `npm install` already installs the bundler's devDependencies which include the runtime libs:
+
+```json
+{
+  "command": "node",
+  "args": ["/absolute/path/to/mcp-zenskar/src/server.js"]
+}
+```
+
 ## Configuration
 
 The server uses `src/mcp-config.json` to define available tools and API endpoints. This file contains the complete mapping of MCP tools to Zenskar API operations. All tools are declarative — no code changes needed to add new tools.