WebChatMCP.js
Related Servers
Alternatives to WebChatMCP.js
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to automate an authenticated browser session for web chat, model and thinking-depth switching, new-chat resets, and local file upload-and-ask workflows.6116 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server that turns one authenticated ChatGPT browser page into a bounded MCP server, exposing tools for creating, listing, searching, exporting, sending, editing chats and downloading media via a CDP driver.MIT
- AlicenseBqualityCmaintenanceEnables MCP clients like Codex to operate chatgpt.com through a dedicated persistent browser profile, allowing chat creation, project management, prompt submission, file uploads, and response reading without using the ChatGPT API.33MIT
- AlicenseBqualityFmaintenanceMCP server that drives chatgpt.com via web UI automation using a session token, enabling long-running tasks, deep research, and image generation.9126 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables an MCP host agent to delegate bounded reasoning tasks to an ordinary, user-signed-in ChatGPT Chat session and collect concise, size-capped answers back into the original workflow. Runs locally with a managed headless browser profile or an optional unpacked browser extension, requiring no API key, and tracks job state, retries, and recovery IDs.MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to remotely drive a hosted headless browser over HTTP, supporting navigation, clicking, typing, and structured page reading through the Model Context Protocol. It also provides bearer-token authentication for secure remote MCP access.2310,908,336 npmApache 2.0
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes (login, logout, ask, models, status, warmup). However, webchat_release and webchat_close both shut down the browser and differ only subtly (release = stop using webchat models / keep preloaded page semantics vs close = full clean shutdown), which could cause misselection.
All eight tools use a uniform webchat_verb pattern (login, logout, ask, models, status, warmup, release, close) with no stylistic deviations.
Eight tools is well-scoped for a browser-driven webchat server, covering session, query, discovery, and lifecycle concerns without bloat.
The surface covers login lifecycle, querying, model discovery, and browser warmup/teardown, which fully supports the core workflow. Minor gaps exist, such as no explicit tool to pick or switch the target service or to continue a conversation, though the fresh-chat design makes these intentional.