webchat
Related Servers
Alternatives to webchat
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables coding agents to drive a real Chrome browser to complete natural-language web tasks and return evidence for verification.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to open URLs in a persistent headless browser and interact with pages by clicking, typing, selecting, reading content, evaluating JavaScript, waiting for elements, and capturing screenshots.49 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to drive a locally installed Google Chrome window with human-like navigation, page inspection, clicking, typing, dragging, scrolling, tab management, and screenshots, while sharing one persistent browser session across sessions.13MIT
- AlicenseBqualityCmaintenanceEnables AI agents to perform low-latency web automation with a persistent headed Chrome/Chromium instance, including navigation, DOM interaction, content extraction, screenshots, tab management, and batch/code execution via 18 MCP tools.20MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to perform typed, site-specific actions across a signed-in Chrome browser, interacting with services like Gmail, Reddit, Drive, and Amazon through natural language requests.1MIT
- AlicenseAqualityDmaintenanceEnables AI agents to control a persistent Chromium browser or attach to an existing Chrome with sandboxed JavaScript and structured tools for web interaction and automation.16MIT
TDQS
Scored across 7 tools
The three groups are clear: querying (ask, council), conversation management (list_threads, thread_history), and introspection (usage, site_status, list_sites). The only real pair that could be confused is ask vs council, but the descriptions explicitly distinguish single-site/race vs parallel multi-site semantics, and site_status vs usage are cleanly separated as live check vs historical stats.
Readable but mixed: list_sites and list_threads use verb_noun, while ask, council, usage and site_status are bare verbs or nouns, and thread_history is noun_noun where list_threads would be the parallel form. No chaos, but no single predictable pattern an agent can pattern-match on.
Seven tools is well-scoped for a webchat orchestration server: two execution tools, three observability tools, and two conversation tools. Each earns its place and nothing is obviously padding.
Core lifecycle is covered: send prompts (ask, council), continue/list/inspect threads, check quota and site health, discover sites. Minor gaps: no tool to delete or rename a saved thread, and no way to enumerate the per-site model menus that ask and council reference, forcing the agent to guess model names.