KitchenSink4Web

<!-- mcp-name: io.github.KitchenSink4AI/kitchensink4web -->

# 🚰 KitchenSink4Web Community Edition

[![Tests](https://github.com/KitchenSink4AI/KitchenSink4Web/actions/workflows/tests.yml/badge.svg)](https://github.com/KitchenSink4AI/KitchenSink4Web/actions/workflows/tests.yml)
[![PyPI](https://img.shields.io/pypi/v/kitchensink4web)](https://pypi.org/project/kitchensink4web/)
[![License: AGPL-3.0](https://img.shields.io/badge/license-AGPL--3.0-blue)](LICENSE)

[Landing page](https://kitchensink4.ai/KitchenSink4Web/) · [llms.txt](https://kitchensink4.ai/KitchenSink4Web/llms.txt) (machine-readable capability manifest for agents and LLM crawlers)

**Read websites and extract data with your AI assistant, read-only by default, with clicking and typing when you allow it.**

Read websites and pull out the data you need from Claude Code, Codex CLI, Copilot CLI or any other MCP client that runs local tools. KitchenSink4Web drives a browser on your computer, returns a page within a size budget and says what it left unread, and exports tables to CSV or JSON. It starts read-only; clicking, typing and form filling are switched on only when you choose. Websites receive ordinary browsing requests; what reaches your AI provider is decided by your AI app. The Community edition is free under the AGPL. The Business edition adds a Windows installer, a signed update channel, a license your company can approve and support.

**Works on:** Windows, macOS and Linux for the browser tools. Image-text recognition uses Windows OCR. A browser download and some optional dependencies may be needed.

## Install

Pick the route for your AI app. The commands go in PowerShell on Windows or a terminal on macOS and Linux, not into an AI chat. The package routes need Python 3.12 or newer.

**Claude Desktop**

Install [uv](https://docs.astral.sh/uv/getting-started/installation/), then quit and reopen Claude Desktop. Download the `.mcpb` file from [KitchenSink4Web releases](https://github.com/KitchenSink4AI/KitchenSink4Web/releases/latest). In Claude Desktop open Settings, then Extensions, then Advanced settings, then Install extension, and choose the file. The bundle fetches the Python package the first time it starts, so the first launch needs a network connection. Restart your session and check that the tools show as connected.

**Claude Code or Codex CLI**

Install uv, then run the line for your app and restart your session:

```sh
claude mcp add web -s user -- uvx kitchensink4web
```

```sh
codex mcp add web -- uvx kitchensink4web
```

**Any other local MCP client**

Use `uvx` as the command and `kitchensink4web` as its argument, or install the package and use `kitchensink4web` as the server command:

```sh
pip install kitchensink4web
```

Then follow your client's guide for adding a local MCP server. Installing the package on its own does not connect it to an AI app.

**Business edition**

Compare the editions on the [pricing page](https://kitchensink4.ai/pricing/). Already purchased? Your Windows installer and download link are in your [license portal](https://get.kitchensink4.ai/my-license/).

## What it can do

53 tools with every pack and browser actions enabled. The default read-only lite launch exposes 12; lite with actions has 20.

- Read a page within a chosen size budget and see what was left unread.
- Find one section or element without fetching the whole page again.
- Extract tables, lists and article text, then export CSV or JSON.
- Take screenshots or save a page as PDF.
- Read only what changed on a page you already read.
- Watch a page for changes while the server runs.
- Turn on clicking, typing and form filling when a task needs them.
- Record a browser task and replay it with checks, with the workflow pack.
- Run automated accessibility checks with the optional dependency.

What is available depends on the packs you enable and the applications installed. The full tool reference is below.

## Business edition

Need a license your company can approve and a setup someone supports? The Business edition pairs these tools with a Windows installer, a signed update channel and support under the Business terms. Update checks tell you when a covered release is available; nothing installs on its own. Compare the options on the [pricing page](https://kitchensink4.ai/pricing/). The Community edition stays free under the AGPL, including business use that meets its terms.

## Privacy Policy

The tools run on your computer, and KitchenSink4AI receives no documents and no usage data from them. Your AI app may send prompts, file contents and tool results to its own provider under that app's settings and terms. Installing downloads packages, and the Community version check contacts PyPI unless you disable it; those requests carry connection details such as your network address and never your documents. The browser connects to the websites you ask it to use, and those sites see ordinary browsing requests. A missing tokenizer table may be downloaded once; the text being measured is never sent. Cloud folders and backups follow their own settings. The [Privacy Policy](https://kitchensink4.ai/privacy/) covers the product, purchases and support records.

*Not affiliated with or endorsed by Google, Mozilla, Microsoft, or any website this server
visits. Chrome, Chromium, Firefox, and Edge are trademarks of their respective owners, used
nominatively to name the browsers this server can drive.*

## The cheap first read

`get_page_view` returns the page's shape: what it is, what is on it section by section, what each
section costs to open, and what the sensible next call would be. You set the budget and the read
never exceeds it, so the question is never whether a page fits, only how much detail you bought.
Every read ends with a completeness block naming what was left out and what it would cost to get
it back. Nothing is swept under the rug.

From there the pattern is cheap and gets cheaper. Expand one region instead of raising the
budget. Chain delta reads: pass the token a read returns and the next read prices only what
changed. Elements come back as short-lived refs your assistant can act on directly, and searches
by text and role survive re-renders that break refs.

Open shadow roots are read and their contents are actable like anything else, which is what makes
component-built sites (Reddit, MDN, most of the modern web) readable at all. Closed roots cannot
be reached by any tool; they are counted and reported rather than silently skipped. Same-origin
iframes are read and searched like the page they sit in, each labeled with its own origin; a
cross-origin frame is counted and named, never entered.

## The packs

The server starts lite: reading, navigation, and session management, 20 tools. Capability packs
are chosen at launch and are fixed for the whole session, which means an absent pack is provably
absent, not merely switched off:

| Pack | What you get |
|---|---|
| extract | Tables, lists, links, and article text, with CSV and JSON export. |
| capture | Screenshots (passwords blurred), PDF export, and saving pages as files. |
| network | See the requests a page makes behind the scenes. Useful for debugging websites; most people leave it off. |
| storage | Use with care. Saves a signed-in session so Claude does not have to log in every time. It saves the session, never your password; treat the saved file like one anyway. |
| files | Download files from pages into one folder, and upload files into page forms. Every one asks you first. |
| diagnostics | Lets Claude run JavaScript on a page, one script at a time, each one shown to you for approval first. This is the most powerful and most dangerous setting on this page. Leave it off unless you know you need it. |
| workflows | Record a multi-step task once and replay it later. Every replay checks that the page still matches before anything runs. |
| accessibility | Checks a page against the WCAG accessibility rules using axe-core, groups what it finds by rule, and says plainly what automated testing cannot check. Needs an optional extra installed; the tool tells you how if it is missing. |

## Browsers and lanes

The default lane drives the server's own bundled Chromium. It never touches your browser or your
profile; sessions open in a fresh profile that is deleted on close unless you explicitly save
signed-in state to a file.

Lane B drives a browser you already have installed (Chrome, Edge, or Firefox), still with its own
separate profile, never yours. Installed Firefox is the lane to reach for on research-heavy work:
sites that turn away automated Chromium routinely serve Firefox normally, and both Firefox lanes
pass bot checks that block headless Chromium. That is lane steering, not evasion; the server does
not disguise what it is, it just lets you use a browser the site treats better.

Signed-in sessions are saved and reloaded with `save_auth_state` and `auth_state=` on open. The
state file records when its session cookies expire, and loading a stale file says so plainly
instead of letting the login fail mysteriously.

`manage_session(action='status')` reports which browsers are installed and which lane it would
recommend for the page you are on. It never switches lanes for you.

## The safety model

A browser is where your logins, your money, and your mistakes all live, so the safety layer is
the product, not a feature of it.

**Read-only unless you say otherwise.** Out of the box the tools that click, type, and submit do
not exist. They are not disabled, they are absent from the tool list, and no instruction on any
webpage can talk your assistant into using a tool that is not there. One switch at install
(`allow acting` in the bundle, `KS4WEB_ALLOW_ACTING=true` elsewhere) brings them in.

**Credential blindness.** The server never reads what you type into password fields, and secrets
observed in cookies and site storage are vaulted: they cannot leak into your assistant's
conversation, becaus