actvt-setuplisted

# Connecting Actvt Actvt's MCP server runs inside the Actvt macOS app. It is not a standalone process, so it only answers while the app is running with the server switched on. Work through these checks in order and stop at the first one that fails. ## 1. Is Actvt installed? ```sh ls -d /Applications/Actvt.app ``` If it is missing, the user needs to install Actvt from https://actvt.io. It is macOS only and requires macOS 15.5 or later. Nothing else here will work until then. ## 2. Is the server switched on? The endpoint descriptor only exists while the server is running. ```sh ls -l ~/Library/Application\ Support/ACTVT/mcp/endpoint.json ``` If the file is missing, tell the user to open Actvt and turn on **Settings > MCP > Enable MCP server**. This is a GUI toggle, so they have to do it. Once it is on, the file appears within a second or two. ## 3. Which port did it bind? ```sh plutil -extract url raw -o - ~/Library/Application\ Support/ACTVT/mcp/endpoint.json ``` Expect `http://127.0.0.1:4096/mcp`, which is what this plugin points at. Actvt prefers 4096 but falls back to another port when something else already holds it. If the URL shows a different port, the user should either free 4096 and restart Actvt, or export the real endpoint before starting Claude Code: ```sh export ACTVT_MCP_URL="$(plutil -extract url raw -o - ~/Library/Application\ Support/ACTVT/mcp/endpoint.json)" ``` ## 4. Does the auth helper work? ```sh "${CLAUDE_PLUGIN_ROOT}/scripts/actvt-auth.sh