Code Lens vs Lighthouse MCP

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

Code Lens logoCode LensDeveloper Tools · Local subprocess (stdio)Gemini-powered MCP server for code analysis.47FairAuth: not declaredLighthouse MCP logoLighthouse MCPDeveloper Tools · Local subprocess (stdio)MCP server for Google Lighthouse performance metrics64GoodAuth: not declared

Verdict: choose Code Lens for developer tools work as a local process; 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?

Code Lens logoChoose Code Lens when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: GEMINI_API_KEY, GOOGLE_API_KEY.
  • You want tools like generate_diff, analyze_pr_impact, generate_review_summary.
Explore Code Lens

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.

SpecCode Lens logoCode LensLighthouse MCP logoLighthouse MCP
CategoryDeveloper ToolsDeveloper Tools
Quality signal47/100 · Fair64/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsGEMINI_API_KEYGOOGLE_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars0212
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools132

Tools & capabilities

Code Lens tools 13

  • generate_diffCapture git diff (unstaged/staged) and cache server-side
  • analyze_pr_impactAssess severity, categories, breaking changes, rollback complexity
  • generate_review_summaryPR summary, risk rating, merge recommendation
  • generate_test_planPrioritized test cases and coverage guidance
  • analyze_time_space_complexityBig-O complexity analysis and degradation detection
  • detect_api_breaking_changesDetect breaking API/interface changes
  • load_fileCache a source file for analysis tools
  • refactor_codeComplexity, duplication, naming, grouping suggestions
  • detect_code_smellsStructural code smells (Fowler taxonomy)
  • generate_documentationJSDoc/TSDoc/docstring stubs for public exports
  • ask_about_codeNatural-language Q&A about a cached file
  • verify_logicVerify algorithms via Gemini code execution sandbox
  • +1 more on 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.

Code Lens

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "code-lens": {
      "command": "npx",
      "args": [
        "-y",
        "@j0hanz/code-lens-mcp@latest"
      ],
      "env": {
        "GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE",
        "GOOGLE_API_KEY": "YOUR_GOOGLE_API_KEY_HERE"
      }
    }
  }
}

Lighthouse MCP

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

Frequently asked questions

Code Lens is categorized under Developer Tools and uses a local stdio subprocess. Lighthouse MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Code Lens 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.

Code Lens has no declared pricing — check the project's own site. 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 code-lens and lighthouse-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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