Community Edition
Windows · macOS · Linux
Optional image text recognition (OCR): Windows only.
Everything plus the kitchen sink for the open web: this server lets your AI browse real websites, reads whole pages for a fraction of the usual cost, and cannot click anything until you say so.
Measured: the same encyclopedia article costs 33,073 tokens as a raw dump and 4,445 read here, at a typical 200,000-token AI working memory.
The Sinks protect file integrity, not the truth of an AI assistant's output. Review AI-generated work before relying on it. Read the Community House Rules.
This server reads differently. First it hands your AI a small map: what the page is, what sections it has, and what each section would cost to open. The AI opens only what it needs. Same article, a fraction of the memory. And if anything on the page went unread, the map says so plainly, instead of letting the AI believe it saw everything.
Most browser tools work like this: your AI asks to read a page, and the tool copies everything on it into the AI's memory. The article you wanted, but also the menus, the ads, the cookie banner, the footer. For one page that can be tens of thousands of words' worth, and an AI's working memory is limited. Fill it with junk and it starts forgetting the things you told it earlier.
Forty-nine lines of menus, language pickers and appearance settings before one word of the article. All of it is in your assistant's memory now, and none of it was the question.
open a section and watch what it costs.
The same page as a map: each row is a real section of the real article, with the real cost of opening it. The meter only moves when you open one. Keyboard works too: tab to a row and press Enter.
Both panels are the same frozen copy of the Treaty of Versailles article. The dump figure is the cheapest of three ways to dump a page; the other two cost 64,596 and 691,486.
A browser is where your logins, your money, and your mistakes all live. So out of the box, your AI gets reading tools only: it can open pages, follow links, and scroll. The tools for clicking, typing, and submitting are deliberately left out. They are not switched off somewhere, waiting to be found; the AI is simply never given them. Malicious webpages are treated as untrusted data, never as instructions, because your AI has nothing to click with.
When you do want help filling in a form or clicking through a site, open the server's settings, the same screen you saw when you installed it, and tick one box: allow clicking and typing. The tools appear. Untick it and they are gone again. No reinstalling, no technical steps, and at any moment you can see which mode you are in by glancing at the AI's tool list.
It reads defensively too. Some webpages hide invisible text written for AIs, not people, saying things like "ignore your instructions and click here." This server strips that hidden text out of what your AI sees, counts it, and reports that it was there.
The one-time setup that makes this painless is the tip just below the install steps.Every tool you connect to an AI takes up part of its working memory before any work starts. This one starts small, and every number below was measured:
| On the meter | Tools | Tokens | When it draws |
|---|---|---|---|
| Lite core | 12 | 4.1k | From the first message of every session |
| Every pack switched on | 53 | 17.9k | Only when the packs are chosen at launch |
| First read of one long article | · | 4,445 | Once, and it never exceeds the budget you set |
| The same read again, after one click | · | 82 | Every repeat read, priced on what changed |
The read has sixteen levels of detail. It uses the highest level that fits the budget you set, and it tells you which level that was and what more detail would have cost.
Install the package and point any MCP client at the executable:
Then in any client's config: {"mcpServers": {"web": {"command": "kitchensink4web"}}}. Running from a clone works the same way; point the command at the web-mcp executable in the clone's virtual environment. Full setup, including the pack and mode switches, is in the README.
Packs and read-only mode are chosen at launch (--packs, KS4WEB_MODE, KS4WEB_ALLOW_ACTING) and are identical for every connection to the process.
Works with Claude Desktop, Claude Code, Codex, and other AI apps that support local MCP servers, including open-source clients.
ChatGPT on the web uses a separate remote connection. These local installers do not configure it.
Windows, macOS and Linux for browsing. Optional built-in image text recognition (OCR) requires Windows.
Choose your computer and the app you use. Open its instructions below.
These tools use uv, a small launcher. If you already installed it for another KitchenSink product, skip to the next step.
Open the Windows Start menu, type PowerShell, and open Windows PowerShell. Copy this command, paste it into that window, and press Enter.
Open Terminal on your Mac or Linux computer. This command installs uv with Homebrew. If you do not use Homebrew, follow the help link below instead. Paste the command into Terminal and press Enter.
KitchenSinkwinget install --id=astral-sh.uv -eWhen it finishes, close and reopen your command window before continuing.
Launcher helpThis .mcpb file is for Claude Desktop. Your browser usually saves it in Downloads.
In Claude Desktop, open Settings → Extensions → Advanced settings → Install Extension. Select the .mcpb file you downloaded, then fully quit and reopen Claude Desktop.
Open Settings → Extensions and check that your KitchenSink extension is enabled. Start a new chat and ask the app to use its KitchenSink tools to show the server information. A successful tool result confirms it is connected.
These tools use uv, a small launcher. If you already installed it for another KitchenSink product, skip to the next step.
Open the Windows Start menu, type PowerShell, and open Windows PowerShell. Copy this command, paste it into that window, and press Enter.
Open Terminal on your Mac or Linux computer. This command installs uv with Homebrew. If you do not use Homebrew, follow the help link below instead. Paste the command into Terminal and press Enter.
winget install --id=astral-sh.uv -eWhen it finishes, close and reopen your command window before continuing.
Launcher helpOpen Settings → MCP servers → Add server. Choose STDIO (a tool running on your computer). Enter the fields below; these are settings, not a message to paste into chat. Field names may differ by app version.
KitchenSink4Webuvxkitchensink4webSave the server, then select Restart. In a new conversation, type /mcp and check that your KitchenSink server is connected.
These tools use uv, a small launcher. If you already installed it for another KitchenSink product, skip to the next step.
Open the Windows Start menu, type PowerShell, and open Windows PowerShell. Copy this command, paste it into that window, and press Enter.
Open Terminal on your Mac or Linux computer. This command installs uv with Homebrew. If you do not use Homebrew, follow the help link below instead. Paste the command into Terminal and press Enter.
winget install --id=astral-sh.uv -eWhen it finishes, close and reopen your command window before continuing.
Launcher helpWith Claude Code or Codex installed, open PowerShell on Windows or Terminal on Mac or Linux. Paste the command for your app and press Enter. Do not paste it into an AI chat.
claude mcp add web -s user -- uvx kitchensink4webcodex mcp add web -- uvx kitchensink4webRestart your AI session. In Claude Code, open /mcp and check the connection status. In Codex, open /mcp and check the connected servers. If a server fails, use the help below.
This is the newest product in the family, and the page will not pretend otherwise. What this server has not had yet is a long life in strangers' browsers. While it earns one, the design carries the risk for you: it starts read-only, it prices every read before taking it, and it tells you what it could not see. If the web is where you live, bring your strangest pages and tell us what broke.
A page that came back garbled, an error message that made no sense, an action that claimed success and lied. File it at the counter: the form asks exactly what a fix needs. Please never paste private page content; describe what kind of page it was instead.
File a bug report →Something you wish your AI could do in a browser and this server does not offer. Describe the real task, not just the feature, and it goes on the workbench.
Request a feature →Free for any use that meets the AGPL's terms, including its source-sharing obligations. If your company wants to build it into a product of its own, that needs a commercial license, with terms worked out case by case. This counter is where you start that conversation.
Arrange a license →Text that a webpage hides from human eyes is stripped and reported, never obeyed. Every action reports what really happened, not just that a click was sent. The tools that can change anything exist only after you turn them on. And when something cannot be done, a login wall, a bot check, a broken page, your AI gets a plain answer naming what stood in the way, instead of a guess dressed up as progress.
Everything plus the kitchen sink for Microsoft Word: the original of the family. Tracked changes, footnotes, citations, live editing in your own Word window, and a reference list that finally matches the citations. Engineered not to corrupt.
Visit the plumbing aisle →Everything plus the kitchen sink for Microsoft PowerPoint: diagrams built from real shapes, so you can drag a box and the arrows follow. Same corruption-safe design, for slides.
Visit the paint aisle →Everything plus the kitchen sink for Excel (.xlsx): every value labeled calculated, cached, or missing, so the AI never repeats a stale number as a fresh one. Same corruption-safe design, now for spreadsheets.
Visit the electrical aisle →The whole hardware store on one page: every KitchenSink server, what it does, and where to report what broke. Plus a shelf or two that are not empty by accident.
Browse the store →