Browser vs Kloakt
A side-by-side look at the Browser and Kloakt MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Browser for browser automation work; choose Kloakt for browser automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Browser when
- You need dedicated capabilities in the Browser Automation domain.
- Its auth model fits you: No auth required.
Choose Kloakt when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
kloakt_extract, kloakt_fetch.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 43/100 · Fair | 53/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 36,641 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Browser | View Kloakt |
Tools & capabilities
Browser tools
No tool names declared yet. Check the project README from the listing page.
Kloakt tools 2
kloakt_extractExtract clean markdown content from a web page using a headless browser with full JavaScript rendering. Strips nav/header/footer by default. Returns structured data: title, URL, markdown content, meta tags, timing. Use this instead of WebFetch when you need JS-rendered content or clean markdown.kloakt_fetchLow-level page fetch with JS rendering. Returns raw output as string. Supports HTML dump, text dump, link extraction, or arbitrary JS evaluation.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Browser
No confirmed install command for Browser yet — follow the setup steps linked from its listing page rather than a guessed package name.
Kloakt
{
"mcpServers": {
"kloakt": {
"command": "uvx",
"args": [
"--from",
"kloakt",
"kloakt-mcp"
]
}
}
}
Frequently asked questions
Browser is categorized under Browser Automation and uses an install path we have not confirmed yet. Kloakt belongs to Browser Automation and uses a local stdio subprocess. Pick Browser for browser automation work and Kloakt for browser automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Browser has no confirmed install command yet — follow its own setup instructions.
Browser is listed as free. Auth: no auth required. Kloakt has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add lightpanda-io-browser and kloakt as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Browser has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 36,641 GitHub stars. Kloakt has 53/100 (Good) with 1 views, 0 installs and 1 GitHub stars.
