Chrome Extension

Chrome extensions are a strong fit for MDP when the useful capability lives in the browser rather than on a remote server.

Good capability shapes

Typical examples include:

The simplest setup is:

run the MDP client inside an extension page, service worker, or controlled browser context
expose endpoint, prompt, or skill paths with the JavaScript SDK
connect to the MDP server over ws / wss or HTTP loop

If websocket auth is required in the browser, the SDK can bootstrap /mdp/auth automatically during connect().

This repository now includes a dedicated Chrome extension app under apps/chrome-extension.

The app is built as an MDP client:

the background service worker connects to the MDP server
matched pages receive a content script for DOM operations
the extension can inject a main-world bridge so page-local code can register paths
the local development workflow is powered by WXT

The current extension app can expose capabilities such as:

Chrome-side endpoint paths for tab management, notifications, and config status
DOM-oriented endpoint paths through the content script
injected main-world endpoint paths through window.__MDP_EXTENSION_BRIDGE__
bridge-facing endpoint paths such as GET /page/injected-paths, POST /page/call-injected-path, and POST /page/snapshot

Build the unpacked extension with:

bash

pnpm --filter @modeldriveprotocol/chrome-extension build

Then load apps/chrome-extension/dist/chrome-mv3 from chrome://extensions with Developer mode enabled.

For local iteration, use:

bash

pnpm --filter @modeldriveprotocol/chrome-extension dev

That uses WXT dev mode to start Chrome with the extension loaded, so you can inspect changes locally without a manual rebuild/load cycle.

Use the extension options page to set: