Home / Clients

MCP launchers

Same server. Different config files, commands, and scopes.

BrowseFleetMCP is a plain stdio server. Client setup mostly comes down to where the config lives and whether the tool prefers a one-shot CLI command or a checked-in config file.

These snippets only cover the server launcher. Every client still depends on the unpacked Chrome extension from extension-v2/.

{
  "command": "npx",
  "args": ["-y", "browsefleetmcp"]
}

{
  "command": "node",
  "args": ["/absolute/path/to/browsefleetmcp/dist/index.js"]
}

Codex

Add it from the CLI or paste it into `~/.codex/config.toml`.

Codex supports both flows. Use codex mcp add when you want the fastest install. Use config.toml when you want the launcher committed, reviewed, or manually edited.

If you are actively developing this repo, switch the command to node /absolute/path/to/browsefleetmcp/dist/index.js so Codex runs your local build instead of the published package.

codex mcp add browsefleet -- npx -y browsefleetmcp

codex mcp list

# ~/.codex/config.toml
[mcp_servers.browsefleet]
command = "npx"
args = ["-y", "browsefleetmcp"]

# local checkout variant
[mcp_servers.browsefleet]
command = "node"
args = ["/absolute/path/to/browsefleetmcp/dist/index.js"]

Cursor

Put the launcher in `~/.cursor/mcp.json` and restart Cursor.

Cursor wants the config file directly. The JSON shape is standard MCP stdio: command plus args.

Use the published package when you want npm-managed updates. Use the local checkout variant when you want Cursor to launch the build from this repo.

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

{
  "mcpServers": {
    "browsefleet": {
      "command": "node",
      "args": ["/absolute/path/to/browsefleetmcp/dist/index.js"]
    }
  }
}

Claude Code

Use `claude mcp add` or commit a project-scoped `.mcp.json`.

The user-level CLI install is the fastest path. If the config should travel with a repo, use --scope project or drop the same JSON into a checked-in .mcp.json.

Claude Desktop is different. It uses the bundle route covered on the separate Claude Desktop page.

claude mcp add --transport stdio browsefleet -- npx -y browsefleetmcp

claude mcp add --transport stdio --scope project browsefleet -- npx -y browsefleetmcp

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

{
  "mcpServers": {
    "browsefleet": {
      "command": "node",
      "args": ["/absolute/path/to/browsefleetmcp/dist/index.js"]
    }
  }
}

Generic and Windows

Any stdio MCP host works. Windows sometimes needs `cmd /c`.

The launcher contract never changes: a local command plus arguments. The only platform wrinkle is that some Windows-native clients cannot spawn the npx shim directly.

{
  "command": "npx",
  "args": ["-y", "browsefleetmcp"]
}

{
  "command": "node",
  "args": ["/absolute/path/to/browsefleetmcp/dist/index.js"]
}

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

Repo examples

Copy from the repo if you do not want to transcribe snippets by hand.

Codex

examples/codex/

Config examples for direct Codex setup.

Cursor

examples/cursor/

Ready-to-copy MCP JSON for Cursor.

Claude Code

examples/claude-code/

CLI and project-scoped examples for Claude Code.

Generic stdio

examples/generic/

Generic command-plus-args shapes for other MCP hosts.

Codex skill

examples/skills/

Drop-in Codex skill folder that teaches the agent how to use BrowseFleetMCP.

Codex skill

Want the agent to understand BrowseFleet without re-explaining the workflow?

There is now a drop-in skill folder in the repo. It teaches Codex to start with browser_health, treat sessions explicitly, prefer BrowseFleet tools over fallback browser tooling, and use the right recovery commands when the extension or transport looks stale.

Open skill page

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