Browser MCP Server
Related Servers
Alternatives to Browser MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides browser automation capabilities using Puppeteer, enabling LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.723,092 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables LLMs to automate web browsers using Puppeteer, allowing navigation, screenshots, form filling, and JavaScript execution in a real browser environment.2MIT
- FlicenseBqualityDmaintenanceA Model Context Protocol server that provides browser automation capabilities using Puppeteer with configurable options through environment variables, enabling LLMs to interact with web pages, take screenshots, and execute JavaScript in a browser environment.74-
- AlicenseBqualityCmaintenanceA Model Context Protocol server for web automation that enables browser control, element interaction, content extraction, and monitoring using Playwright.73 npmISC
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.18Apache 2.0
- AlicenseBqualityDmaintenanceA Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages, take screenshots, generate test code, scrape web content, and execute JavaScript in real browser environments.3111,800 npmMIT
TDQS
Scored across 2 tools
The two tools have overlapping purposes—both capture console output from a browser—but their descriptions clarify distinct contexts: one navigates to a URL, while the other serves local content. Some ambiguity remains as both involve browser console operations, but the descriptions help differentiate them.
Both tool names follow a consistent 'browser-[context]-console' pattern, using hyphens to separate words. This predictable naming scheme makes it easy to understand their roles and relationship within the server.
With only two tools, the server feels under-scoped for a 'Browser MCP Server' that implies broader browser automation capabilities. A typical browser server might include tools for navigation, DOM interaction, or screenshots, making this set appear incomplete.
Inferred domain is browser automation, but the toolset is severely incomplete. It lacks basic operations like page navigation, element interaction, or screenshot capture, focusing narrowly on console output. This will likely cause agent failures for common browser tasks.