kimi-webbridge-mcp
Related Servers
Alternatives to kimi-webbridge-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceBrowser MCP server that connects to your existing browser, preserving sessions, passwords, and extensions, enabling AI agents to interact with web pages without bot detection.315 npm1MIT
- AlicenseNot gradedqualityAmaintenanceConnects MCP-compatible AI agents to an anti-detection browser server so they can navigate sites, interact with pages, run searches, extract content, download files, and reuse sessions across multi-tab workflows. It exposes 47 tools over stdio or HTTP transport, letting agents automate the web without getting blocked.549 npmMIT
- AlicenseAqualityAmaintenanceMCP server that drives your real Chrome/Edge/Opera browser through a Chrome extension and DevTools Protocol, preserving logins and session state, and can also perform OS-level mouse and keyboard input behind approval.5121 PyPI2MIT
- AlicenseNot gradedqualityAmaintenanceConnects MCP-compatible AI agents to an anti-detection browser server, enabling navigation, interaction, search, extraction, downloads, multi-tab workflows, and persistent cookie-based sessions. Agents can automate the web through 47 tools while evading bot detection, with stdio or HTTP transport support.549 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server that lets agents drive your real Chrome browser with existing logins and sessions via an outbound-only WebSocket extension. It exposes Playwright-compatible browser tools for navigation, clicking, typing, and snapshots.1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceConnects MCP-compatible AI agents to a separate anti-detection browser server, providing tools for navigation, interaction, search, extraction, downloads, multi-tab workflows, and session reuse.549 npmMIT
TDQS
Scored across 22 tools
Each tool targets a distinct browser concern: history, tab/session management, page reading, interaction, and capture. Even similar readers like wb_snapshot, wb_get_text, and wb_find are explicitly differentiated by intended use and output type.
All tools share a consistent wb_ prefix and snake_case style, but a few names such as wb_status, wb_network, and wb_console are nouns rather than verb_noun commands. This is a minor deviation from the otherwise predictable pattern.
22 tools is above the typical compact range, but the broad browser-automation domain justifies most entries with little duplication. It feels slightly heavy rather than bloated or sparse.
The tool surface covers the full browser workflow: connection checking, navigation, tab lifecycle, page reading, interaction, waiting, screenshots, network/console capture, and upload. Minor gaps like dedicated cookie or dropdown helpers exist, but agents can work around them with wb_evaluate.