aural-ui 4.1.0 → 4.2.0

package/README.md

@@ -114,6 +114,13 @@ aural-ui update
 
 The **aural-ui MCP server** exposes the design system by reading from aural-ui source (components, icons, source and story files). No Storybook process is required.
 
+### Run the MCP server locally
+
+1. Copy [`mcp/.env.example`](mcp/.env.example) to `mcp/.env` and fill in the values (Google OAuth client, redirect URL, issuer base URL, JWT secret). That file is the canonical list of variables; it stays next to the server code so it does not drift.
+2. From the repo root: `npx tsx mcp/src/index.ts` (listens on port `3000` by default).
+
+For OAuth flow details, see [`mcp/docs/auth.md`](mcp/docs/auth.md).
+
 ### Setup in Cursor
 
 Add the server in `.cursor/mcp.json` (or Cursor Settings → MCP). Start the MCP server first (e.g. `npx tsx mcp/src/index.ts` from the aural-ui repo root, or run the Docker image), then point Cursor at the streamable HTTP endpoint:
@@ -131,7 +138,7 @@ Add the server in `.cursor/mcp.json` (or Cursor Settings → MCP). Start the MCP
 
 The server identifies as **aural-ui** so agents match user phrases like "add aural-ui btn". Use the same URL when the server runs in Docker or elsewhere (e.g. `http://your-host:3000/mcp`).
 
-- **Config:** All MCP server settings are in `mcp/src/lib/env.ts` (no .env). You can set `AURAL_UI_SRC` there to the aural-ui repo `src` path if the workspace is not the aural-ui repo.
+- **Config:** Non-secret defaults and limits live in `mcp/src/lib/env.ts`. OAuth and JWT values must come from the environment; for local dev, use `mcp/.env` (start from [`mcp/.env.example`](mcp/.env.example)).
 
 **HTTP / Docker:** When running the MCP server over HTTP (e.g. in Docker):
 - **GET /health** — Returns `200` and `{ "ok": true, "server": "aural-ui" }` for load balancers and orchestrators (no MCP session required).