@theme-registry/refract-mcp 0.1.1 → 0.1.2

package/README.md

@@ -22,6 +22,7 @@ against it, so the agent asks about *your* theme without ever resending it. It r
 | `checkContrast` | Do the theme's colour pairings pass WCAG-2 (+ advisory APCA)? |
 | `validateTheme` | Is a candidate theme valid on every configured target? — returns **every** problem at once (collect-all), per target. |
 | `diffTheme` | What's the blast radius of a candidate edit — which tokens moved, classes changed, pairings crossed a threshold, targets stopped building? |
+| `reload` | Reload the project's theme config from disk (also happens automatically on change). |
 
 `diffTheme` is the plan-then-apply guardrail: pass a **candidate edit** and it builds it against the
 project's real adapters and reports the blast radius *before* the agent writes — the claim a token file
@@ -31,6 +32,10 @@ a generic check would miss. `getClass` / `resolveToken` read the real emitted na
 what ships. The query tools take no
 `theme` argument — they read the loaded project theme.
 
+Note: over MCP, `getClass` takes **named** arguments — `{ subsystem, group, variant }` (a JSON object,
+as the tool schema requires) — whereas the runtime `theme.getClass(subsystem, group, variant)` takes the
+same three **positionally**. Same identifiers, different call shape for the two surfaces.
+
 ## Architecture
 
 Pure tools (`src/tools.ts`, unit-tested) operate on a built `Theme` the server holds; `callTool`

package/dist/server.js

@@ -1,9 +1,9 @@
 #!/usr/bin/env node
-import { readFileSync, watch } from 'node:fs';
-import { dirname } from 'node:path';
+import { readFileSync, watch, realpathSync } from 'node:fs';
+import { basename, dirname } from 'node:path';
 import { parseArgs } from 'node:util';
 import { argv } from 'node:process';
-import { pathToFileURL } from 'node:url';
+import { fileURLToPath } from 'node:url';
 import { Server } from '@modelcontextprotocol/sdk/server/index.js';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
 import { ListToolsRequestSchema, CallToolRequestSchema, ListResourcesRequestSchema, ReadResourceRequestSchema } from '@modelcontextprotocol/sdk/types.js';
@@ -443,9 +443,40 @@ async function start(args) {
     transport.onclose = () => process.exit(0);
     await createServer().connect(transport);
 }
-// Run when invoked as the bin entry (ESM: compare our URL to the launched script), not when imported by tests.
-if (argv[1] && import.meta.url === pathToFileURL(argv[1]).href) {
-    void start(argv.slice(2));
+const realpathOr = (p) => {
+    try {
+        return realpathSync(p);
+    }
+    catch {
+        return p;
+    }
+};
+/**
+ * Is the launched script (`argv[1]`) this very module, resolving symlinks on BOTH sides? The published
+ * bin runs through a `node_modules/.bin/refract-mcp` symlink, so a raw path/URL compare misses (the
+ * symlink path ≠ the real dist path) and the server silently exits 0 — a hostile failure mode for
+ * something agents auto-spawn. Resolving through realpath fixes it. Pure + injectable `real` so the
+ * decision is unit-testable without spawning a process.
+ */
+function isBinEntry(invokedAs, selfPath, real = realpathOr) {
+    return invokedAs !== undefined && real(invokedAs) === real(selfPath);
+}
+// Auto-start only when invoked as the bin entry. If the launched file IS this file by name but its path
+// won't resolve to this module, say so loudly instead of no-op. A genuine module import (argv[1] is the
+// test runner, a different basename) stays silent.
+{
+    const invokedAs = argv[1];
+    const selfPath = fileURLToPath(import.meta.url);
+    if (isBinEntry(invokedAs, selfPath)) {
+        start(argv.slice(2)).catch((e) => {
+            process.stderr.write(`refract-mcp: failed to start — ${e.message}\n`);
+            process.exit(1);
+        });
+    }
+    else if (invokedAs && basename(invokedAs) === basename(selfPath)) {
+        process.stderr.write(`refract-mcp: launched as "${invokedAs}" but that path doesn't resolve to this module (${selfPath}); ` +
+            `not auto-starting. Use the \`refract-mcp\` bin or \`node ${selfPath}\`.\n`);
+    }
 }
 
-export { callTool, createServer, guideFiles, loadTheme, serverVersion, start };
+export { callTool, createServer, guideFiles, isBinEntry, loadTheme, serverVersion, start };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theme-registry/refract-mcp",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Model Context Protocol server for refract — query + validate a project's theme from an AI agent.",
   "author": {
     "name": "Petyo Stoyanov",
@@ -25,7 +25,7 @@
   ],
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
-    "@theme-registry/refract": "^0.1.1"
+    "@theme-registry/refract": "^0.1.2"
   },
   "peerDependencies": {
     "typescript": "*"
@@ -42,7 +42,7 @@
     "rollup": "^3.29.4",
     "typescript": "^5.4.2",
     "vitest": "^4.1.10",
-    "@theme-registry/refract-css": "^0.1.1"
+    "@theme-registry/refract-css": "^0.1.2"
   },
   "scripts": {
     "build": "rollup -c",