@ikuma.cloud/pix-mcp 0.0.4 → 0.0.5

package/README.md

@@ -9,7 +9,7 @@ required.
 To load this package in an existing Pi installation:
 
 ```sh
-pi -e /absolute/path/to/pix/packages/mcp
+pi -e /absolute/path/to/pix/packages/pix-mcp
 ```
 
 Disable any other MCP adapter that would collide with the `mcp` tool or flags,
@@ -33,6 +33,13 @@ unless explicitly trusted. Either of these authorizes the file for one session:
 Review the file first: trusting it can launch arbitrary local programs and
 contact remote services. Configuration trust is not an OS sandbox.
 
+At session startup, interactive and RPC sessions receive an `MCP config: <path>`
+notice with the resolved absolute path after the file is read and trusted, even
+when a flag skips the trust prompt. The notice identifies the configuration file,
+not whether every server connected; it never includes configuration contents.
+Missing, unreadable, or malformed files and declined trust produce no notice.
+Print and JSON sessions remain silent.
+
 ```json
 {
   "mcpServers": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ikuma.cloud/pix-mcp",
-  "version": "0.0.4",
+  "version": "0.0.5",
   "publishConfig": {
     "access": "public"
   },

package/src/index.ts

@@ -389,6 +389,7 @@ export default function mcp(pi: ExtensionAPI) {
           "MCP configuration not trusted. Review it, then restart with --mcp-trust-config or --mcp-config <path>.";
         return;
       }
+      if (ctx.hasUI) ctx.ui.notify(`MCP config: ${path}`, "info");
       owner.configIssues = config.issues;
       owner.status =
         config.issues.length > 0