# mcp-web-llm: six logged-in web models exposed as MCP tools

slug: mcp-web-llm · https://miscsubjects.com/a/mcp-web-llm · category: reference · tags: reference, browser-models, mcp · updated 2026-09-06T19:10:26.349Z

mcp-web-llm is a small open-source project (9 stars on 2026-09-06, created March 2026, last pushed April 2026) that turns six logged-in web chat products into MCP tools. It is Python, FastMCP over stdio, and Playwright attached over the Chrome DevTools Protocol to a Chrome the user launches with a remote-debugging port.

**What it does.** Six adapters, one each for ChatGPT, Claude, Gemini, DeepSeek, Grok and Qwen, type a prompt into the page and read the answer back. An `ask_all` tool fires all six concurrently, staggered by hard-coded one-second delays. Files and images can be uploaded. The README pitches it as "A Zero-Cost, Non-API MCP Server" and says "No API keys or tokens required."

**How it detects completion.** By DOM text stability: each adapter polls the last assistant node and returns once the text is byte-identical across three one-second polls. On timeout it returns the literal string "Timeout. Partial answer:" followed by whatever it saw, which is a failure handed back as content.

**Sessions.** There is no session object. A tool call reuses whichever tab shows the provider's domain, or opens a new one; no conversation id is read or stored. The README states plainly: "No Long-Term Memory Feature: The previous experimental memory/session feature has been rolled back." A SQLite history file is written and never read.

**What it does not do.** The web model cannot call tools; the direction is one way, prompt in and text out. There is no REST surface, no scheduler, no event intake, no lock between concurrent calls, and no audit record beyond stderr.

**Why it matters here.** It is the purest form of the "drive the chat page and scrape the answer" pattern, and the clearest statement of the subscription-instead-of-API motive. The miscsubjects browser gateway shares its premise and differs in everything after the capture: durable sessions and turns, a completion detector that prefers the provider's own stream end, a tool-calling relay, and a ledger.

## Sources

1. HGD-coder/mcp-web-llm README — https://github.com/HGD-coder/mcp-web-llm