WebChatMCP.js
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEBCHATMCP_HOST | No | HTTP bind address (default `127.0.0.1`; `0.0.0.0` exposes to LAN — no auth, use with care) | |
| WEBCHATMCP_PORT | No | HTTP port (default `8321`; `0` disables HTTP) | |
| WEBCHATMCP_CHANNEL | No | Browser channel: `chromium` (default) / `chrome` / `msedge` | |
| WEBCHATMCP_HEADLESS | No | `1` runs headless (first login still needs a visible browser) | |
| WEBCHATMCP_PROFILE_DIR | No | Browser profile directory (default `~/.webchatmcp/profile`) | |
| WEBCHATMCP_ANSWER_TIMEOUT_MS | No | Answer wait limit (default `120000`) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| webchat_loginA | Check whether the built-in browser profile is already logged in to the chosen service (headless, no window shown). If so, return immediately. Only when not logged in does it show a browser window so the user can log in manually once; the window is hidden again after login succeeds. The session is persisted in the profile directory and reused by later calls. Logging in is optional for chatgpt and gemini: webchat_ask also works as a guest there. Claude and Grok require it. Waits up to timeout_seconds (default 180) for the manual login; on timeout the window stays open and the user can finish later, then call webchat_status. |
| webchat_logoutA | Log out of the chosen service by clearing its cookies from the built-in browser profile (headless, no window shown), then re-check the login state. Logging out of gemini clears google.com cookies, which signs the profile out of Google. Use webchat_login to log in again. Guest use (where the service allows it) keeps working. |
| webchat_askA | Send a prompt through a fresh private/temporary chat of the chosen service in the built-in browser and return the answer text. Every call opens a brand-new chat: the prompt is not added to the account's chat history. Works without logging in (guest) on chatgpt and gemini; claude and grok require webchat_login (a guest gets a logged_out error). Optionally select a model first via |
| webchat_modelsA | List the models and thinking-depth options available for the chosen service (scraped live from its model menu, so account tier differences are handled automatically). |
| webchat_statusB | Report whether the built-in browser is running, whether the login is active for the given service (defaults to the service of the current page), whether the current page is in private/temporary-chat mode, the profile directory, the HTTP endpoint state, and optional local CDP debugging endpoint (cdp.enabled / cdp.endpoint). Does not navigate: it inspects the page the browser is currently on. |
| webchat_closeA | Close the built-in browser cleanly. The login sessions stay saved in the profile directory and will be reused next time. |
| webchat_warmupA | Preload the private (temporary) chat page of the chosen service in the background browser, so the next webchat_ask skips the page load. With |
| webchat_releaseA | Close the background (headless) browser and its preloaded chat page because the user no longer uses any webchat model. The next webchat_ask or webchat_warmup starts it again. A visible browser window (login in progress) is left alone. Login sessions stay saved. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.