← ClaudeAtlas

run-production-master-mcplisted

Build, test, and lint the production-master-mcp workspaces, and run the MCP server locally once packages land. Use before opening a PR or when verifying a local checkout is healthy. Triggers on "run the server", "build and test", "run the checks", "verify the repo".
ProductionMasterAI/production-master-mcp · ★ 1 · AI & Automation · score 75
Install: claude install-skill ProductionMasterAI/production-master-mcp
# run-production-master-mcp Local verification and run helper for this npm-workspaces monorepo. Run every gate the way CI does, in order, and stop at the first failure. Prefer the `make` targets (they wrap the npm scripts). ## Verify 1. **Install** — clean, reproducible install from the lockfile: ```bash make install # npm ci ``` 2. **Build all workspaces** — compile every package under `packages/*`: ```bash make build # npm run build ``` 3. **Test** — run the full test suite: ```bash make test # npm test ``` 4. **Lint** — the same lint gate CI enforces (warnings fail the build): ```bash make lint # npm run lint ``` 5. **Typecheck** — a stricter pass than build (also part of CI): ```bash npm run typecheck ``` ## Run the server locally Set `PM_API_URL` to the Production Master REST API base and (for stdio) `PM_SESSION_JWT` to your session token, then: ```bash # stdio transport (default) PM_API_URL=<api-base-url> PM_SESSION_JWT=<your-token> \ npm run dev --workspace=@production-master/mcp # Streamable HTTP transport — POST /mcp on PM_MCP_HTTP_PORT (default 3000); # bearer is per-request, so no PM_SESSION_JWT here PM_API_URL=<api-base-url> \ npm run dev --workspace=@production-master/mcp -- --http ``` `make dev` (`npm run dev --workspaces --if-present`) runs the same script across every workspace that defines one — today that is just `@production-master/mcp`. Connect an MCP clie