One-page setup

Copy the install path for the MCP host you use.

Every route has the same browser prerequisite: load the Chrome extension from this repo, then point your client at the local stdio server. Use the published package for normal use or the local checkout while developing.

Required once

Build and load the Chrome extension.

The npm package installs the server only. The browser side still comes from this repo checkout. After running the commands, open chrome://extensions, enable Developer mode, click Load unpacked, and select extension-v2/.

git clone https://github.com/JakubJDolezal/browsefleetmcp.git
cd browsefleetmcp/extension-v2
npm install
npm run build

Server choice

Published package.

Use this when you want the npm release and do not need local source edits.

npx -y browsefleetmcp --help

Server choice

Local checkout.

Use this when your MCP client should run the build from this repo.

cd /absolute/path/to/browsefleetmcp
npm install
npm run build
node /absolute/path/to/browsefleetmcp/dist/index.js --help

Copy by target

Pick the block for the thing you are installing into.

Codex

User-level MCP server.

The first block uses the published package. The second points Codex at your local build. If browsefleet already exists, remove or edit that entry before adding it again.

codex mcp add browsefleet -- npx -y browsefleetmcp
codex mcp get browsefleet
codex mcp list
cd /absolute/path/to/browsefleetmcp
npm install
npm run build
codex mcp add browsefleet -- node /absolute/path/to/browsefleetmcp/dist/index.js
codex mcp get browsefleet

Claude Code

User or project-scoped MCP server.

Use user scope for your machine. Use project scope when the config should live with a repo. If the server name already exists, remove or update the old entry before re-adding it.

claude mcp add --transport stdio browsefleet -- npx -y browsefleetmcp
claude mcp list
claude mcp add --transport stdio --scope project browsefleet -- npx -y browsefleetmcp
claude mcp list
cd /absolute/path/to/browsefleetmcp
npm install
npm run build
claude mcp add --transport stdio browsefleet -- node /absolute/path/to/browsefleetmcp/dist/index.js

Claude Desktop

Package an MCPB bundle.

Build the root package, pack the bundle, then install the generated .mcpb file from Claude Desktop Settings.

npm install -g @anthropic-ai/mcpb
cd /absolute/path/to/browsefleetmcp
npm install
npm run build
mcpb pack

Cursor or generic MCP host

Paste the stdio launcher shape.

Cursor uses ~/.cursor/mcp.json. Other stdio MCP hosts need the same command and args shape.

{
  "mcpServers": {
    "browsefleet": {
      "command": "npx",
      "args": ["-y", "browsefleetmcp"]
    }
  }
}
{
  "command": "cmd",
  "args": ["/c", "npx", "-y", "browsefleetmcp"]
}

Optional Codex skill

Teach Codex the BrowseFleet workflow.

This does not install the MCP server. It only gives Codex operating guidance after BrowseFleet is configured.

mkdir -p ~/.codex/skills
cp -R /absolute/path/to/browsefleetmcp/examples/skills/browsefleetmcp ~/.codex/skills/

First run

A configured server still needs a connected browser tab.

Open Chrome, use the BrowseFleetMCP extension popup to connect the current tab, then run a health check or create a session. If tools fail with No connected tab, the client is installed but the browser side is not attached yet.

npx -y browsefleetmcp health
npx -y browsefleetmcp create-session --url https://example.com --label "Smoke test"

# local checkout variant
node /absolute/path/to/browsefleetmcp/dist/index.js health