lighthouse-mcp 0.1.9 → 0.1.12

package/README.md

@@ -2,8 +2,6 @@
 
 An MCP server that wraps around Google's Lighthouse tool to help measure various performance metrics for web pages.
 
-![Lighthouse MCP Server Screenshot](screenshot.png)
-
 ## Features
 
 - Run comprehensive Lighthouse audits on any URL
@@ -150,43 +148,7 @@ Claude will use the `get_performance_score` tool to analyze the website and retu
 - Node.js 16+
 - Chrome/Chromium browser (for Lighthouse)
 
-## Development & Release
-
-### Prerequisites
-
-Before releasing, ensure you're authenticated with both registries:
-
-**NPM Authentication:**
-```bash
-npm login
-```
-
-**MCP Registry Authentication:**
-```bash
-mcp-publisher login github
-```
-
-If your authentication tokens expire, you'll need to re-login to the respective services.
-
-### Making Releases
-
-Use the interactive release script to publish to both NPM and the MCP Registry:
-
-```bash
-./release.sh
-```
-
-The script will:
-1. Check NPM login status
-2. Check for uncommitted changes
-3. Run tests (if they exist)
-4. Build the project
-5. Prompt for version bump type (patch/minor/major/custom)
-6. Update both package.json and server.json versions
-7. Create a preview of the package contents
-8. Publish to NPM
-9. Publish to MCP Registry (if mcp-publisher is available)
-10. Create git commit and tag
-11. Optionally push to remote repository
-
-This ensures consistent releases to both registries with proper version synchronization.
+## Endorsements
+<a href="https://glama.ai/mcp/servers/@priyankark/lighthouse-mcp">
+  <img width="380" height="200" src="https://glama.ai/mcp/servers/@priyankark/lighthouse-mcp/badge" />
+</a>

package/build/index.js

@@ -4,6 +4,40 @@ import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js'
 import { CallToolRequestSchema, ErrorCode, ListToolsRequestSchema, McpError, } from '@modelcontextprotocol/sdk/types.js';
 import lighthouse from 'lighthouse';
 import * as chromeLauncher from 'chrome-launcher';
+import os from 'os';
+import fs from 'fs';
+import path from 'path';
+// Workaround for modelcontextprotocol/typescript-sdk#1380
+// In some Zod runtimes, the method literal is stored under `_def.values[0]`
+// instead of `_def.value` / `.value`, causing "Schema method literal must be a string"
+// during Server initialization. This patches setRequestHandler to handle both cases.
+const originalSetRequestHandler = Server.prototype.setRequestHandler;
+Server.prototype.setRequestHandler = function patchedSetRequestHandler(requestSchema, handler) {
+    try {
+        return originalSetRequestHandler.call(this, requestSchema, handler);
+    }
+    catch (err) {
+        if (err?.message !== 'Schema method literal must be a string')
+            throw err;
+        // Attempt to fix the schema by copying values[0] to value
+        try {
+            const shape = requestSchema?.shape ?? requestSchema?._def?.shape?.();
+            const methodSchema = shape?.method;
+            const def = methodSchema?._def;
+            const maybeValue = Array.isArray(def?.values) ? def.values[0] : undefined;
+            if (typeof maybeValue === 'string') {
+                if (def && def.value === undefined)
+                    def.value = maybeValue;
+                if (methodSchema && methodSchema.value === undefined)
+                    methodSchema.value = maybeValue;
+            }
+        }
+        catch {
+            // If patching fails, rethrow the original error
+        }
+        return originalSetRequestHandler.call(this, requestSchema, handler);
+    }
+};
 const isValidAuditArgs = (args) => {
     return (typeof args === 'object' &&
         args !== null &&
@@ -111,7 +145,29 @@ class LighthouseServer {
             throw new McpError(ErrorCode.InvalidParams, 'Invalid audit arguments');
         }
         try {
-            const chrome = await chromeLauncher.launch({ chromeFlags: ['--headless'] });
+            // Ensure temp directory exists and is writable (fixes #19 - Windows EPERM)
+            // On Windows, os.tmpdir() reads TEMP -> TMP -> USERPROFILE, so we verify
+            // the resolved path is usable before launching Chrome.
+            const tmpDir = os.tmpdir();
+            try {
+                fs.accessSync(tmpDir, fs.constants.W_OK);
+            }
+            catch {
+                // If the default temp dir isn't writable, create a fallback in the user's home
+                const fallbackTmp = path.join(os.homedir(), '.lighthouse-tmp');
+                if (!fs.existsSync(fallbackTmp)) {
+                    fs.mkdirSync(fallbackTmp, { recursive: true });
+                }
+                process.env.TEMP = fallbackTmp;
+                process.env.TMP = fallbackTmp;
+                process.env.TMPDIR = fallbackTmp;
+            }
+            // Explicitly pass process.env so MCP-configured env vars (TEMP, TMP, TMPDIR)
+            // propagate to the Chrome child process on all platforms.
+            const chrome = await chromeLauncher.launch({
+                chromeFlags: ['--headless', '--no-sandbox'],
+                envVars: process.env,
+            });
             const options = {
                 logLevel: 'info',
                 output: 'json',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lighthouse-mcp",
-  "version": "0.1.9",
+  "version": "0.1.12",
   "description": "MCP server for Google Lighthouse performance metrics",
   "type": "module",
   "main": "build/index.js",
@@ -35,10 +35,14 @@
     "url": ""
   },
   "dependencies": {
-    "@modelcontextprotocol/sdk": "latest",
+    "@modelcontextprotocol/sdk": "^1.27.1",
     "chrome-launcher": "^0.15.2",
     "lighthouse": "^12.5.1"
   },
+  "overrides": {
+    "basic-ftp": ">=5.2.0",
+    "lodash-es": ">=4.17.23"
+  },
   "devDependencies": {
     "@types/node": "^20.4.5",
     "typescript": "^5.1.6"