Lighthouse MCP vs Runx
A side-by-side look at the Lighthouse MCP and Runx MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Lighthouse MCP for developer tools work as a local process; choose Runx for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Lighthouse MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
run_audit, get_performance_score.
Choose Runx when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 64/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 212 | 104 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View Lighthouse MCP | View Runx |
Tools & capabilities
Lighthouse MCP tools 2
run_auditRun a Lighthouse audit on a URLget_performance_scoreGet just the performance score for a URL
Runx tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Lighthouse MCP
{
"mcpServers": {
"lighthouse-mcp": {
"command": "npx",
"args": [
"lighthouse-mcp"
]
}
}
}
Runx
No confirmed install command for Runx yet — follow the setup steps linked from its listing page rather than a guessed package name.