A side-by-side look at the Ghostlight and MCP Server Browser MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ghostlight for browser automation work as a local process; choose MCP Server Browser for browser automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Ghostlight when
You need dedicated capabilities in the Browser Automation domain.
No tool names declared yet. Check the project README from the listing page.
MCP Server Browser 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.
Ghostlight is categorized under Browser Automation and uses a local stdio subprocess. MCP Server Browser belongs to Browser Automation and uses a local stdio subprocess. Pick Ghostlight for browser automation work and MCP Server Browser for browser automation.
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.
Ghostlight has no declared pricing — check the project's own site. MCP Server Browser 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 ghostlight and mcp-server-browser as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ghostlight has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. MCP Server Browser has 52/100 (Good) with 1 views, 0 installs and 39,308 GitHub stars.