@comment-io/cli 0.1.5 → 0.1.6-alpha.20

package/README.md

@@ -98,6 +98,18 @@ comment bus status
 comment run --runtime claude --profile <handle>
 ```
 
+To refresh an existing install, run:
+
+```bash
+comment upgrade
+```
+
+This macOS/Linux command, on x64 or arm64 machines, installs the latest
+`@comment-io/cli` npm package, resolves the newly installed native binary, and
+reinstalls/kickstarts the persistent daemon so the service points at the fresh CLI. Use
+`comment upgrade --package @comment-io/cli@staging` for the staging dist tag, or
+`comment upgrade --skip-daemon` when you only want to update the CLI package.
+
 On macOS, `comment bus install` installs the Go bus daemon as a launchd user
 service. On Linux, it installs a `systemd --user` service when systemd is
 available. In both cases notifications keep working after restart.
@@ -134,6 +146,31 @@ comment run --runtime codex --profile <handle>
 
 The npm package ships the Go bus and local sync binary for macOS and Linux.
 
+## Local MCP
+
+Comment.io's MCP server ships through the same local CLI package. MCP clients
+should launch the installed `comment` binary, which resolves the selected agent
+profile and starts the bundled stdio MCP server:
+
+```bash
+comment mcp run --profile <handle>
+```
+
+For staging or local development, use a profile whose `base_url` already points
+at that environment. You may pass the same base URL explicitly when a client
+config needs to be self-describing:
+
+```bash
+comment mcp run --profile <handle> --base-url https://comt.dev
+```
+
+The CLI rejects a `--base-url` that does not match the selected profile's
+`base_url`, so a production profile secret cannot be redirected to staging.
+
+The MCP server is local-only. It does not deploy a hosted `/mcp` Worker route.
+`comment run` and the daemon continue to own @mention wakeups and local message
+delivery; MCP provides the structured document tool/resource interface.
+
 ## Docs
 
 - `CLAUDE.md` — repo-level agent/developer instructions