@primeuicom/mcp 0.1.11 → 0.1.12

package/README.md

@@ -23,7 +23,12 @@ Core goals:
 ## PrimeUI API KEY
 
 - PrimeUI provides this key together with the exported project.
-- In practice, it is preconfigured in the exported project's `.mcp.json` for the `primeui` server entry.
+- In linked/exported projects, the key is stored in `.primeui/project.json` under `apiKey`.
+- PrimeUI MCP loads `PRIMEUI_API_KEY` from env first, then falls back to `.primeui/project.json`.
+- `.primeui/project.json` must include:
+  - `projectId`
+  - `apiKey`
+  - `targetProjectPath` (required, relative path such as `"./"` or `"./apps/web"`)
 
 ## Your first prompts
 
@@ -183,6 +188,11 @@ Use the same JSON server configuration shown in Getting started:
 ## Runtime behavior
 
 - PrimeUI MCP uses bearer authentication with `PRIMEUI_API_KEY`.
+- If `PRIMEUI_API_KEY` env is missing, PrimeUI MCP reads `.primeui/project.json` (`apiKey`).
+- Config lookup:
+  - if `PRIMEUI_PROJECT_ROOT` is set, MCP reads `${PRIMEUI_PROJECT_ROOT}/.primeui/project.json`;
+  - otherwise MCP searches `.primeui/project.json` upward from current working directory.
+- Missing or invalid `targetProjectPath` is treated as a configuration error.
 - Downloaded archives are validated as ZIP payloads before extraction.
 - Temporary export files are written under `.primeui/temp/` in user project folder
 
@@ -191,7 +201,7 @@ Use the same JSON server configuration shown in Getting started:
 Configure these environment variables for local development:
 
 - `PRIMEUI_API_BASE_URL`: PrimeUI API base URL (for example `http://localhost:3020` when testing against local Studio API).
-- `PRIMEUI_PROJECT_ROOT`: local project root where PrimeUI temp files are created (defaults to the current working directory if not set).
+- `PRIMEUI_PROJECT_ROOT`: explicit project root override for `.primeui/project.json` and `.primeui/temp/` location.
 
 Run MCP Inspector: