Package BrowseFleetMCP as a Claude Desktop extension.

Claude Desktop prefers a local MCP bundle for local tools. This repo already includes the root manifest.json and .mcpbignore needed to package the current checkout.

npm install -g @anthropic-ai/mcpb
npm run build
mcpb pack

Bundle metadata

manifest.json

Claude Desktop bundle metadata lives at the repo root.

Bundle filter

.mcpbignore

Controls what goes into the packaged desktop extension.

Runtime

dist/index.js

The bundle still launches the same built Node entrypoint.

Install in Claude Desktop

Use the extension flow once the `.mcpb` file exists.

Open Settings → Extensions.
Open Advanced settings.
Click Install Extension....
Select the generated .mcpb file.

What changes

Packaging changes. The browser-session model does not.

The bundle route removes the need to hand-edit config JSON for Claude Desktop users.

It does not remove the Chrome extension requirement or the connected-tab model. The server still needs a live browser tab to control.

This is best when you want a clean artifact to hand to internal users or teammates rather than a repo setup guide.

Keep the model straight

Claude Desktop changes how the server is installed, not how the browser attaches.

Desktop-native install

Users install a packaged extension instead of editing local config files.

Same server core

The package still runs the same built server from dist/index.js.

Extension still required

You still need the Chrome extension and a connected current tab.

Good for distribution

A versioned bundle is easier to hand to teams than ad hoc local config instructions.