Kapture

by williamkapke

Not rated
GitHub

About

A Chrome DevTools Extension that enables browser automation through the Model Context Protocol (MCP) for AI applications.

Details

Author
williamkapke
Categories
Developer Tools, Automation, Other

Option A: Install from Chrome Web Store (Recommended)

- Visit the[Kapture Chrome Web Store page - Click "Add to Chrome" - Confirm the installation

Kapture - Browser Automation via Chrome DevTools

Kapture is a Chrome DevTools Extension that enables browser automation through the Model Context Protocol (MCP). It allows AI applications like Claude to control web browsers via a three-layer architecture.

✨ Key Feature: Multiple AI clients can connect to the same server! Claude Desktop, Cline, and other MCP clients can all control browser tabs through a single server instance.

Kapture bridges AI assistants with web browsers through:

- MCP Server: Handles MCP protocol communication
- Chrome Extension: Background service worker executes browser automation commands (DevTools does not need to be open)
- WebSocket Bridge: Real-time communication between server and extensions
- Multi-Client Support: Multiple AI clients can connect simultaneously via WebSocket

# Server cd server npm install npm run build # Test App (optional) cd test-app npm install

Option A: Install from Chrome Web Store (Recommended)

- Visit theKapture Chrome Web Store page - Click "Add to Chrome" - Confirm the installation

Option B: Load Unpacked (Developer Mode)

- Open Chrome and navigate tochrome://extensions/ - Enable "Developer mode" - Click "Load unpacked" - Select theextensionfolder

Configure your AI clientand open it. It will start the MCP server automatically.

# Server cd server npm start # Test App cd test-app npm start

- Open any website in Chrome
- Click the Kapture toolbar icon and flip the connection toggle
- The extension connects to the server on port 61822 (the badge shows ✓ when connected)

Alternatively, connect from the "Kapture" panel in DevTools, or load a page with?kapture-connect=truein the URL to auto-connect.

Option 1: Using the bridge command (Recommended)

This single command starts the server and handles stdio-to-WebSocket translation:

{ "mcpServers": { "kapture": { "command": "npx", "args": ["-y", "kapture-mcp@latest", "bridge"] } } }

Option 2: Direct WebSocket connection (Advanced)

For advanced use cases where you need manual server control:
- Configure Claude Desktop to connect via WebSocket:

{ "mcpServers": { "kapture": { "transport": "websocket", "url": "ws://localhost:61822/mcp" } } }

Note: This approach requires manually managing the server lifecycle. Use Option 1 (bridge command) for most use cases.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.