chrome-lite-mcp

Local Chrome browser automation via MCP (Model Context Protocol). No remote bridges, no account matching — purely localhost.

Works with any MCP-compatible client.

MCP Client <-stdio-> MCP Server <-WebSocket-> Chrome Extension <-Chrome API-> Web Pages

The Chrome extension connects to a local WebSocket server. The MCP client talks to the MCP server via stdio. Everything stays on localhost.

1. Open Chrome -> chrome://extensions -> Enable Developer Mode -> Load unpacked -> select extension/
2. cd server && npm install
3. Connect your MCP client to server/index.js via stdio

Download the latest release tarball:

REPO="vutran1710/chrome-lite-mcp"
DOWNLOAD_URL=$(curl -sfL "https://api.github.com/repos/${REPO}/releases/latest" \
  | grep -o 'https://[^"]*chrome-lite-mcp-.*\.tar\.gz[^"]*' | head -1)
mkdir -p /opt/chrome-lite-mcp
curl -sfL "$DOWNLOAD_URL" | tar -xz -C /opt/chrome-lite-mcp

The tarball includes server/ (with node_modules), extension/, and docs/.

Launch Chrome with the extension and start the MCP server:

# Start MCP server (WebSocket on port 7331)
node /opt/chrome-lite-mcp/server/index.js &

# Launch Chrome with extension auto-loaded
chromium --load-extension=/opt/chrome-lite-mcp/extension &

{
  "mcpServers": {
    "chrome": {
      "command": "node",
      "args": ["/path/to/chrome-lite-mcp/server/index.js"]
    }
  }
}

Tagged releases are built automatically via GitHub Actions. To create a release:

git tag v0.2.0
git push origin v0.2.0

The workflow builds a tarball (chrome-lite-mcp-v0.2.0.tar.gz) containing:

• server/ — MCP server with bundled node_modules
• extension/ — Chrome Manifest V3 extension
• docs/ — Design docs and app-specific skills reference

| Tool | Description | |------|-------------| | tabs_list | List all open tabs | | `tab_