context-doctor 0.12.0 → 0.12.1

package/dist/doctor.js

@@ -26,8 +26,10 @@ function checkMcpEntry(appName, configPath) {
         const entry = config.mcpServers?.["context-doctor"];
         if (!entry)
             return { label: appName, status: "fail", detail: `no context-doctor entry in ${configPath} — run: context-doctor install` };
-        // Absolute-path entries must point at a file that still exists.
-        const target = entry.command === "npx" ? null : entry.args?.[0];
+        // Absolute-path entries must point at a file that still exists. Launcher
+        // forms (npx, and Windows' cmd /c npx) resolve at spawn time, not now.
+        const launcher = entry.command === "npx" || entry.command === "cmd";
+        const target = launcher ? null : entry.args?.[0];
         if (target && !existsSync(target)) {
             return { label: appName, status: "fail", detail: `MCP entry points at missing file ${target} — re-run: context-doctor install` };
         }
@@ -41,7 +43,7 @@ function checkMcpEntry(appName, configPath) {
                 detail: `MCP command ${cmd} no longer exists (a Node upgrade moves version-pinned paths) — re-run: context-doctor install`,
             };
         }
-        return { label: appName, status: "ok", detail: `MCP wired (${entry.command === "npx" ? "npx, tracks npm releases" : "local build"})` };
+        return { label: appName, status: "ok", detail: `MCP wired (${launcher ? "npx, tracks npm releases" : "local build"})` };
     }
     catch (e) {
         return { label: appName, status: "fail", detail: `${configPath} is not valid JSON (${e.message})` };

package/dist/install.d.ts

@@ -6,5 +6,19 @@
  * Every config edit is a careful JSON merge with a .backup file written first.
  * `context-doctor uninstall` reverses it.
  */
+/**
+ * How to invoke the published package as an MCP server on a given platform.
+ *
+ * On Windows npx is `npx.cmd` — a batch script, not an executable. MCP clients
+ * spawn their server directly, without a shell, so a bare "npx" fails with
+ * ENOENT and the app simply shows no tools and no error. Hence the cmd /c
+ * wrapper that every working Windows MCP config uses.
+ *
+ * Exported so the platform branch is testable from any host OS.
+ */
+export declare function npxLauncher(platformName: string): {
+    command: string;
+    args: string[];
+};
 export declare function runInstall(): void;
 export declare function runUninstall(): void;

package/dist/install.js

@@ -43,9 +43,25 @@ function serverEntry() {
     const localMcp = join(selfDir, "mcp.js");
     const fromPackage = selfDir.includes(`${sep}node_modules${sep}`) || selfDir.includes("_npx");
     if (!fromPackage && existsSync(localMcp)) {
+        // `node` is node.exe on Windows — directly spawnable, no shell needed.
         return { command: "node", args: [localMcp] };
     }
-    return { command: "npx", args: ["-y", "context-doctor-mcp"] };
+    return npxLauncher(platform());
+}
+/**
+ * How to invoke the published package as an MCP server on a given platform.
+ *
+ * On Windows npx is `npx.cmd` — a batch script, not an executable. MCP clients
+ * spawn their server directly, without a shell, so a bare "npx" fails with
+ * ENOENT and the app simply shows no tools and no error. Hence the cmd /c
+ * wrapper that every working Windows MCP config uses.
+ *
+ * Exported so the platform branch is testable from any host OS.
+ */
+export function npxLauncher(platformName) {
+    return platformName === "win32"
+        ? { command: "cmd", args: ["/c", "npx", "-y", "context-doctor-mcp"] }
+        : { command: "npx", args: ["-y", "context-doctor-mcp"] };
 }
 function readJson(path) {
     if (!existsSync(path))

package/dist/mcp.js

@@ -37,7 +37,7 @@ const STRATEGY_IDS = ["dedupe", "trim-tool-results", "trim-tool-calls", "strip-b
  * recommended pattern.
  */
 function createServer() {
-    const server = new McpServer({ name: "context-doctor", version: "0.12.0" }, { instructions: SERVER_INSTRUCTIONS });
+    const server = new McpServer({ name: "context-doctor", version: "0.12.1" }, { instructions: SERVER_INSTRUCTIONS });
     server.tool("profile_context", "Profile an LLM conversation or prompt: token breakdown by category, largest messages, and actionable findings about wasted context (duplicates, oversized tool results, base64 blobs, cache-unfriendly ordering). Accepts OpenAI/Anthropic conversation JSON or raw text. Call this immediately whenever the user asks about token usage, context size, LLM cost, or latency — and proactively offer it once a conversation grows long or accumulates large pasted content.", {
         conversation: z.string().describe("Conversation JSON (OpenAI or Anthropic format, or bare message array) or raw prompt text"),
         model: z.string().optional().describe("Target model name for context-window math, e.g. claude-sonnet-5 or gpt-4o"),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "context-doctor",
-  "version": "0.12.0",
+  "version": "0.12.1",
   "description": "Profile and optimize LLM context windows. See what's eating your tokens and fix it — works with Claude, GPT, Gemini, and any MCP-capable AI app.",
   "keywords": [
     "llm",