Lighthouse MCP vs Phonebook

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

Lighthouse MCP logoLighthouse MCPDeveloper Tools · Local subprocess (stdio)MCP server for Google Lighthouse performance metrics64GoodAuth: not declaredPhonebook logoPhonebookDeveloper Tools · Local subprocess (stdio)Self-hosted gallery of your SwiftUI #Preview and Jetpack Compose @Preview screens.47FairAuth: not declared

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

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

Phonebook logoChoose Phonebook when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
Explore Phonebook

Feature & specification comparison

Rows where the two servers differ are marked.

SpecLighthouse MCP logoLighthouse MCPPhonebook logoPhonebook
CategoryDeveloper ToolsDeveloper Tools
Quality signal64/100 · Good47/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars21213
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools2Not listed

Tools & capabilities

Lighthouse MCP tools 2

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

Phonebook 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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "lighthouse-mcp": {
      "command": "npx",
      "args": [
        "lighthouse-mcp"
      ]
    }
  }
}

Phonebook

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "phonebook": {
      "command": "npx",
      "args": [
        "-y",
        "@stag-build/phonebook"
      ]
    }
  }
}

Frequently asked questions

Lighthouse MCP is categorized under Developer Tools and uses a local stdio subprocess. Phonebook belongs to Developer Tools and uses a local stdio subprocess. Pick Lighthouse MCP for developer tools work and Phonebook 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.

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

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