Runx vs Lighthouse MCP

A side-by-side look at the Runx and Lighthouse MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Runx logoRunxDeveloper ToolsThe governed runtime for agent skills. Search the catalog and inspect a skill before running it.41FairAuth: no auth requiredLighthouse MCP logoLighthouse MCPDeveloper Tools · Local subprocess (stdio)MCP server for Google Lighthouse performance metrics64GoodAuth: not declared

Verdict: choose Runx for developer tools work; choose Lighthouse MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Runx logoChoose Runx when

  • You need dedicated capabilities in the Developer Tools domain.
  • Its auth model fits you: No auth required.
Explore Runx

Lighthouse MCP logoChoose 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.
Explore Lighthouse MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecRunx logoRunxLighthouse MCP logoLighthouse MCP
CategoryDeveloper ToolsDeveloper Tools
Quality signal41/100 · Fair64/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars104212
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listed2

Tools & capabilities

Runx tools

No tool names declared yet. Check the project README from the listing page.

Lighthouse MCP tools 2

  • run_auditRun a Lighthouse audit on a URL
  • get_performance_scoreGet just the performance score for a URL

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.

Runx

No confirmed install command for Runx yet — follow the setup steps linked from its listing page rather than a guessed package name.

Lighthouse MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "lighthouse-mcp": {
      "command": "npx",
      "args": [
        "lighthouse-mcp"
      ]
    }
  }
}

Frequently asked questions

Runx is categorized under Developer Tools and uses an install path we have not confirmed yet. Lighthouse MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Runx for developer tools work and Lighthouse MCP for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Runx has no confirmed install command yet — follow its own setup instructions.

Runx is listed as free. Auth: no auth required. Lighthouse MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add runx and lighthouse-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Runx has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 104 GitHub stars. Lighthouse MCP has 64/100 (Good) with 2 views, 0 installs and 212 GitHub stars.