lighthouse-mcp 0.1.6 → 0.1.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +32 -4
- package/package.json +3 -2
package/README.md
CHANGED
|
@@ -14,7 +14,11 @@ An MCP server that wraps around Google's Lighthouse tool to help measure various
|
|
|
14
14
|
|
|
15
15
|
## Installation
|
|
16
16
|
|
|
17
|
-
### Option 1:
|
|
17
|
+
### Option 1: From MCP Registry (Recommended)
|
|
18
|
+
|
|
19
|
+
This server is available in the [Model Context Protocol Registry](https://registry.modelcontextprotocol.io/servers/io.github.priyankark/lighthouse-mcp). Install it using your MCP client or Claude Desktop.
|
|
20
|
+
|
|
21
|
+
### Option 2: Using npx
|
|
18
22
|
|
|
19
23
|
You can run the tool directly using npx without installation:
|
|
20
24
|
|
|
@@ -22,9 +26,9 @@ You can run the tool directly using npx without installation:
|
|
|
22
26
|
npx lighthouse-mcp
|
|
23
27
|
```
|
|
24
28
|
|
|
25
|
-
### Option
|
|
29
|
+
### Option 3: Global Installation
|
|
26
30
|
|
|
27
|
-
Install the package globally:
|
|
31
|
+
Install the package globally from npm:
|
|
28
32
|
|
|
29
33
|
```bash
|
|
30
34
|
npm install -g lighthouse-mcp
|
|
@@ -36,7 +40,7 @@ Then run it:
|
|
|
36
40
|
lighthouse-mcp
|
|
37
41
|
```
|
|
38
42
|
|
|
39
|
-
### Option
|
|
43
|
+
### Option 4: Local Development
|
|
40
44
|
|
|
41
45
|
1. Clone this repository
|
|
42
46
|
2. Install dependencies:
|
|
@@ -145,3 +149,27 @@ Claude will use the `get_performance_score` tool to analyze the website and retu
|
|
|
145
149
|
|
|
146
150
|
- Node.js 16+
|
|
147
151
|
- Chrome/Chromium browser (for Lighthouse)
|
|
152
|
+
|
|
153
|
+
## Development & Release
|
|
154
|
+
|
|
155
|
+
### Making Releases
|
|
156
|
+
|
|
157
|
+
Use the interactive release script to publish to both NPM and the MCP Registry:
|
|
158
|
+
|
|
159
|
+
```bash
|
|
160
|
+
./release.sh
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
The script will:
|
|
164
|
+
1. Check for uncommitted changes
|
|
165
|
+
2. Run tests (if they exist)
|
|
166
|
+
3. Build the project
|
|
167
|
+
4. Prompt for version bump type (patch/minor/major/custom)
|
|
168
|
+
5. Update both package.json and server.json versions
|
|
169
|
+
6. Create a preview of the package contents
|
|
170
|
+
7. Publish to NPM
|
|
171
|
+
8. Publish to MCP Registry
|
|
172
|
+
9. Create git commit and tag
|
|
173
|
+
10. Optionally push to remote repository
|
|
174
|
+
|
|
175
|
+
This ensures consistent releases to both registries with proper version synchronization.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "lighthouse-mcp",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.8",
|
|
4
4
|
"description": "MCP server for Google Lighthouse performance metrics",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "build/index.js",
|
|
@@ -15,7 +15,8 @@
|
|
|
15
15
|
"build": "tsc && chmod +x build/index.js",
|
|
16
16
|
"start": "node build/index.js",
|
|
17
17
|
"dev": "tsc -w",
|
|
18
|
-
"prepublishOnly": "npm run build"
|
|
18
|
+
"prepublishOnly": "npm run build",
|
|
19
|
+
"update-server-json": "node -e \"const fs=require('fs');const pkg=JSON.parse(fs.readFileSync('package.json'));const server=JSON.parse(fs.readFileSync('server.json'));server.version=pkg.version;server.packages[0].version=pkg.version;fs.writeFileSync('server.json',JSON.stringify(server,null,2));\""
|
|
19
20
|
},
|
|
20
21
|
"keywords": [
|
|
21
22
|
"lighthouse",
|