mason-context 0.3.5 → 0.3.7

package/README.md

@@ -120,7 +120,7 @@ Most providers work without an API key — `claude`, `gemini`, and `ollama` all
 
 **What it doesn't touch:** Mason respects `.gitignore` (via `git ls-files`) and has a deny-list that blocks `.env`, `.pem`, `.key`, credentials, and other sensitive files from being sampled. Path traversal protection ensures all file access stays within the project root.
 
-**LLM data flow:** When generating a snapshot via CLI (`mason generate`, `mason snapshot`), Mason sends sampled file contents to your configured LLM provider. If you're using `claude`, `openai`, or `gemini`, this means source code is sent to an external API. Use `ollama` for fully local generation. The MCP server tools (`get_snapshot`, `get_impact`, etc.) do not send data to any LLM — they only read local files.
+**LLM data flow:** Generating a snapshot via CLI sends sampled file contents to your configured LLM provider — the same way any AI coding assistant reads your code. Use `ollama` for fully local generation. The MCP server tools (`get_snapshot`, `get_impact`, etc.) only read local files.
 
 ## Language support
 

package/dist/bin/mason-mcp.js

@@ -1296,7 +1296,7 @@ function createMcpServer() {
   const server = new McpServer(
     {
       name: "mason",
-      version: "0.3.5"
+      version: "0.3.7"
     },
     {
       instructions: "Mason is a context engineering tool. Always call get_snapshot before using Explore agents, Glob, or Grep to understand the codebase. The snapshot is a concept map that maps features and flows to their implementing files \u2014 it eliminates the need to search. This applies to ANY question about architecture, features, flows, how things work, cross-feature interactions, or bug investigation. Workflow: 1) Call get_snapshot first. 2) If no snapshot, call full_analysis and then save_snapshot to create one. 3) If the snapshot is stale, tell the user and offer to update it. 4) Use your native file reading tool to read files the snapshot points to. 5) Before modifying a file, call get_impact to check what else might be affected. 6) After making significant changes (new features, refactors, architecture changes), call save_snapshot to update the concept map."

package/dist/bin/mason.js

@@ -1879,7 +1879,7 @@ function createMcpServer() {
   const server = new McpServer(
     {
       name: "mason",
-      version: "0.3.5"
+      version: "0.3.7"
     },
     {
       instructions: "Mason is a context engineering tool. Always call get_snapshot before using Explore agents, Glob, or Grep to understand the codebase. The snapshot is a concept map that maps features and flows to their implementing files \u2014 it eliminates the need to search. This applies to ANY question about architecture, features, flows, how things work, cross-feature interactions, or bug investigation. Workflow: 1) Call get_snapshot first. 2) If no snapshot, call full_analysis and then save_snapshot to create one. 3) If the snapshot is stale, tell the user and offer to update it. 4) Use your native file reading tool to read files the snapshot points to. 5) Before modifying a file, call get_impact to check what else might be affected. 6) After making significant changes (new features, refactors, architecture changes), call save_snapshot to update the concept map."
@@ -2064,7 +2064,7 @@ function createCLI() {
   const program2 = new Command();
   program2.name("mason").description(
     "Context engineering CLI & MCP server \u2014 generates intelligent CLAUDE.md files"
-  ).version("0.3.5");
+  ).version("0.3.7");
   program2.command("setup").description("Register Mason as an MCP server with Claude Code").option("--scope <scope>", "Config scope: user or project", "user").action(async (opts) => {
     const { execFile: execFile9 } = await import("child_process");
     const { promisify: promisify9 } = await import("util");

package/dist/src/cli.js

@@ -1879,7 +1879,7 @@ function createMcpServer() {
   const server = new McpServer(
     {
       name: "mason",
-      version: "0.3.5"
+      version: "0.3.7"
     },
     {
       instructions: "Mason is a context engineering tool. Always call get_snapshot before using Explore agents, Glob, or Grep to understand the codebase. The snapshot is a concept map that maps features and flows to their implementing files \u2014 it eliminates the need to search. This applies to ANY question about architecture, features, flows, how things work, cross-feature interactions, or bug investigation. Workflow: 1) Call get_snapshot first. 2) If no snapshot, call full_analysis and then save_snapshot to create one. 3) If the snapshot is stale, tell the user and offer to update it. 4) Use your native file reading tool to read files the snapshot points to. 5) Before modifying a file, call get_impact to check what else might be affected. 6) After making significant changes (new features, refactors, architecture changes), call save_snapshot to update the concept map."
@@ -2064,7 +2064,7 @@ function createCLI() {
   const program = new Command();
   program.name("mason").description(
     "Context engineering CLI & MCP server \u2014 generates intelligent CLAUDE.md files"
-  ).version("0.3.5");
+  ).version("0.3.7");
   program.command("setup").description("Register Mason as an MCP server with Claude Code").option("--scope <scope>", "Config scope: user or project", "user").action(async (opts) => {
     const { execFile: execFile9 } = await import("child_process");
     const { promisify: promisify9 } = await import("util");

package/package.json

@@ -1,8 +1,9 @@
 {
   "name": "mason-context",
-  "version": "0.3.5",
+  "version": "0.3.7",
   "description": "Context engineering CLI & MCP server — generates intelligent CLAUDE.md files through structured codebase analysis",
   "type": "module",
+  "mcpName": "com.adrianczuczka/mason",
   "bin": {
     "mason": "dist/bin/mason.js",
     "mason-mcp": "dist/bin/mason-mcp.js",
@@ -12,11 +13,19 @@
     "build": "tsup",
     "dev": "tsup --watch",
     "test": "vitest run",
-    "test:watch": "vitest"
+    "test:watch": "vitest",
+    "pack:mcpb": "node scripts/pack-mcpb.mjs"
   },
   "keywords": [
-    "context-engineering",
+    "mcp",
+    "model-context-protocol",
     "claude",
+    "claude-code",
+    "claude-md",
+    "context-engineering",
+    "code-analysis",
+    "concept-map",
+    "snapshot",
     "ai",
     "cli"
   ],
@@ -36,7 +45,7 @@
     "LICENSE"
   ],
   "dependencies": {
-    "@anthropic-ai/sdk": "^0.82.0",
+    "@anthropic-ai/sdk": "^0.95.1",
     "@modelcontextprotocol/sdk": "^1.29.0",
     "chalk": "^5.6.2",
     "commander": "^14.0.3",