# Adapstory ISA MCP package

Install the package globally from its published npm tarball so the browser runtime path remains stable:

```sh
npm install --global @adapstory/isa
adapstory-isa install
```

The `install` command installs the bundled app in `/Applications/Adapstory ISA.app`. It does not launch the app. Open the app and complete its first-run setup before connecting an MCP client.

With the actual Chrome extension ID, configure the managed browser integration:

```sh
adapstory-isa configure-browser --extension-id ACTUAL_CHROME_EXTENSION_ID
```

This writes the manager's browser configuration and an exact-origin native messaging manifest. It does not install the extension or launch Chrome. Install the extension separately. When supplied to the package builder, its compiled files are under `assets/chrome-extension/`.

Close the previous managed Chrome instance, then open the separate ISA profile with its local automation endpoint:

```sh
open --env ISA_NATIVE_DATA_ROOT= -na 'Google Chrome' --args "--user-data-dir=$HOME/Library/Application Support/Adapstory ISA/Chrome" --remote-debugging-port=9227 --remote-debugging-address=127.0.0.1 --no-first-run --no-default-browser-check 'chrome://extensions/'
```

Keep this visible profile separate from personal Chrome profiles. The manager serializes managed browser tasks and checks the destination against the selected account before filling. Use its explicit browser finish action when a task ends.

Run `adapstory-isa` with no command to start the package-bundled stdio MCP bridge. It passes stdin, stdout, and stderr through to the native bridge and requires the installed app to be running. MCP startup never installs or launches the app.

This package requires macOS 13+ on Apple Silicon, an arm64 Node.js 22+ installation, and Google Chrome for browser operations. It does not include vault data, credentials, browser profiles, or tokens. See `PRIVACY.md` for data handling details.