Kitsuvo integrations

Kitsuvo integrations let Claude Code, Codex and other MCP clients drive Kitsuvo, a fast browser built for your LLM. Free for Mac and Windows: open a page, read it, and explain the local evidence behind its AI-built, slop and impersonation verdicts, or check a layout at phone, tablet and desktop sizes.

This repository holds the public installation sources: the plugin and its four agent skills (setup, browse, evidence, responsive), the local HTTP MCP bridge, the cloud relay connector, a Rust MCP client, and browser-extension developer previews. The browser itself is a separate download.

Get Kitsuvo: kitsuvo.com for Windows (64-bit) and macOS (Apple silicon and Intel). Free, no account. First-launch prompts are explained at kitsuvo.com/install. The plugins start the installed browser; they do not install it.

What your agent can do

No Kitsuvo account or API key is needed for local browsing and detection.

Additional clients

Client configs and desktop extension cover Cursor, VS Code, Gemini CLI, Cline, Continue, LM Studio, Devin and remote workflow clients. Registry metadata describes the opt-in authenticated endpoint. Directory approval is separate from these install sources.

Install

Every row except the extension needs Kitsuvo installed with kitsuvo on PATH. If it is not on PATH, use the executable's absolute path as command and keep the argument mcp.

Then ask: Open https://example.com in Kitsuvo and explain its detection evidence.

Claude Code

Install Kitsuvo on Windows or macOS and make kitsuvo available on PATH. Then run:

claude plugin marketplace add leancoderkavy/kitsuvo-integrations
claude plugin install kitsuvo@kitsuvo-browser

The local server runs in Claude Code and Cowork. It does not run on Claude web or mobile.

Codex

codex plugin marketplace add leancoderkavy/kitsuvo-integrations
codex plugin add kitsuvo --marketplace kitsuvo-browser

The plugin includes setup, browsing, detection-evidence, and responsive skills. Do not assume the connection is isolated from your normal sign-ins. On Mac 0.2.14, local MCP reuses the normal profile by default; add --separate-profile to a direct MCP configuration for a separate persistent profile. Check your installed build's browser_status and the connection guide. The plugin requires the installed desktop browser; it does not install it.

Browser inside ChatGPT, Claude, Cursor, or T3 Code

The MCP App bridge provides an interactive browser panel with navigation, tabs, page controls, detection evidence and Windows/macOS previews. Pages still run in Kitsuvo on your computer. For Claude Desktop, launch node integrations/mcp-http/server.mjs --stdio after installing that directory's dependencies. For cloud hosts, use an authenticated tunnel or the cloud connector's --app mode. See panel setup and cloud setup.

Use node integrations/mcp-http/setup.mjs --host cursor --binary /absolute/path/to/kitsuvo to print a local visual-panel configuration. Hosts claude, t3code, and chatgpt have their own setup routes; see host setup. T3 Code's embedded UI depends on the selected provider and build.

Other applications can mount the same panel with the typed @kitsuvo/mcp-http/embed host SDK and an authorized MCP client. Try npm run embed in integrations/mcp-http, then open http://127.0.0.1:8787/embed. See embedding Kitsuvo for lifecycle, isolation and shared-profile details.

HTTP MCP

cd integrations/mcp-http
npm ci --ignore-scripts
npm test
npm start

Node.js 22 or newer is required. The bridge binds only to loopback and is for a secure, authenticated tunnel. Public cloud-directory submission needs a stable HTTPS endpoint with authentication and a connection to each user's own browser. See MCP setup.

Authenticated cloud relay

integrations/mcp-cloud includes the separate OAuth-protected cloud relay and interactive local connector. The endpoint is https://kitsuvo-mcp-relay.fly.dev/mcp. Connecting forwards selected page results to the relay and the client you explicitly approve. Disconnecting revokes access. See cloud setup for prerequisites, consent, ephemeral-state limits and remaining publisher identity requirements.

Rust connector client

Build the standalone client with cargo build --locked --manifest-path crates/kitsuvo-connectors/Cargo.toml. It discovers and calls tools from explicitly approved stdio and Streamable HTTP MCP servers. OAuth credentials are stored in the macOS or Windows credential store. See connector setup for approval syntax and current provider qualification limits.

Browser extensions

Public store installs: Get for Chrome or Get for Edge. These listings were verified October 14, 2026. The extension works without installing the desktop browser.

extensions/chromium targets Chrome, Edge, Opera, Brave and Vivaldi. extensions/firefox is for temporary Firefox installation; Mozilla signing is required for public installs. extensions/safari needs Apple packaging and signing. See browser setup and kitsuvo.com/extensions.

The extension checks local builder fingerprints and optionally filters search results. It has no cloud AI, telemetry, or desktop companion requirement. It does not include the desktop browser's full slop or impersonation checks. Manual packages remain developer previews. Firefox and Safari do not have verified public listings here. Browser-store availability does not establish approval in any AI-client directory.

Security and privacy

• Choose the profile. These local plugin configurations pass mcp and inherit the installed browser's default. On Mac 0.2.14 this reuses the normal signed-in profile, including website cookies. Add --separate-profile in a direct MCP configuration when you want a separate persistent profile. Check browser_status for your installed build. The packages do not enable --allow-sensitive.
• Sensitive pages are refused. Sign-in pages and password fields are not driven.
• Local by default. The plugin adds no analytics and no Kitsuvo-hosted upload service. Kitsuvo itself sends no telemetry.
• What the AI client sees. Tool arguments (URLs and any text you ask it to type) go to the browser. Page text, snapshots, reports and supported screenshots go back to the connected client, which handles them under its own data policy. Pages can contain personal data.
• Cloud paths are opt-in. The loopback bridge is not exposed unless you put a tunnel in front of it. The cloud relay reaches your browser only while you run its connector and after you approve a client in your terminal.
• Evidence, not proof. AI-built is provenance, not proof of harm. A low score is not proof of human authorship or safety.

Full policy: kitsuvo.com/privacy. To report a vulnerability, see SECURITY.md.

FAQ

What is Kitsuvo? A free browser for Mac and Windows that checks visited sites for AI-builder traces, filters likely AI-built results from Google, Bing and DuckDuckGo, and shows the evidence behind each score. These integrations let an AI agent use it.

Do I need an account, API key or paid plan? No. Local browsing and detection need none. Optional cloud AI checks in the desktop app are separate.

Does installing the plugin install Kitsuvo? No. Install the desktop browser first. The plugin runs kitsuvo mcp.

Which systems are supported? The desktop browser is for Windows (64-bit) and macOS (Apple silicon and Intel). Screenshots are Windows-only; on macOS use snapshots and resizing. On Linux or ChromeOS, try the extension preview.

Can the agent use my signed-in browser? Yes, when it uses your normal profile: that is the local MCP default on Mac 0.2.14. A separate profile must be selected explicitly with --separate-profile. Sensitive sign-in pages and password fields are protected by default. Page text from other signed-in pages can still reach the connected AI client.

Does it work with ChatGPT? Through the Codex local marketplace, or a cloud client via the HTTP bridge with a secure tunnel or the cloud relay.

Is it listed in the Claude, ChatGPT or browser-extension stores? Chrome and Edge have the public extension listings linked above. That is separate from AI-client directory approval; no such approval is established here. The local Claude Code and Codex plugin install routes use this repository.

Can it prove a site was written by AI? No. It reports builder evidence and separates AI-built, low-value content and impersonation. Detection depends on recognizable traces.

Can I fork or redistribute this? The Kitsuvo Integration License allows personal use and local configuration changes. Other modification or redistribution needs written permission from hello@kitsuvo.com.

Something broke. Open an install help or bug report issue. See CONTRIBUTING.md.

Repository map