webcontrol-mcp
Related Servers
Alternatives to webcontrol-mcp
No user-submitted related servers found.
Related Servers
FlicenseAqualityCmaintenanceEnables coding agents to drive a real Playwright-backed browser session, navigating, observing, interacting, and capturing proof on web pages via MCP tools across stdio and Streamable HTTP transports.152-- AlicenseAqualityAmaintenanceEnables assistants such as Claude Code, Codex, and Gemini CLI to drive a real browser over MCP — navigating, clicking, typing, and reading live pages from plain-English instructions. Supports optional proxy routing, persistent profiles for surviving logins, and reproducible browser identities via seeds.1631,816MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Desktop, Claude Code and IDE agents to call a tool that drives a real Playwright browser to complete web tasks, with sensitive actions automatically refused when no human is available to approve them.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to drive a live Chrome or Brave browser over stdio, with tools for navigation, clicking, typing, screenshots, and executing automation goals.3MIT
- AlicenseAqualityBmaintenanceEnables AI agents to drive a real Playwright browser over MCP to navigate pages, read accessibility-tree snapshots, click, type, screenshot, and evaluate JavaScript, either in a managed browser or attached to a running Chromium-based browser via CDP.201MIT
- FlicenseNot gradedqualityDmaintenanceProvides browser automation capabilities through Claude Desktop and other MCP clients, enabling navigation, screenshot capture, content extraction, and interactive control.-
TDQS
Scored across 5 tools
Each tool maps to a single, clearly distinct browser action (navigate, click, type, capture, read), with no semantic overlap between them. An agent can unambiguously pick the right tool for any given step.
Most tools follow a verb_noun/verb-object pattern (open_page, get_text) or a standard single-action verb (click, fill), which is readable and predictable. The lone noun-form 'screenshot' is a minor deviation from the dominant verb style but still self-explanatory.
Five tools is a reasonable, well-scoped surface for a minimal browser controller and each tool earns its place. It leans slightly thin, since common interactions like navigation or key presses have no dedicated tool.
The core read/interact loop (open, click, fill, screenshot, read text) is covered, but notable gaps exist: no back/forward/reload navigation, no key press (e.g. Enter/Submit), no select/dropdown handling, scroll, or hover. These omissions will force agents to work around common form and multi-page flows.