sunpeak 0.16.1 → 0.16.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sunpeak",
-  "version": "0.16.1",
+  "version": "0.16.2",
   "description": "Local-first MCP Apps framework. Quickstart, build, test, and ship your Claude or ChatGPT App!",
   "type": "module",
   "main": "./dist/index.cjs",

package/template/README.md

@@ -18,7 +18,8 @@ That's it! Edit the resource files in [./src/resources/](./src/resources/) to bu
 pnpm test              # Run tests with Vitest.
 pnpm test:e2e          # Run end-to-end tests with Playwright.
 sunpeak dev            # Start dev server + MCP endpoint.
-sunpeak build          # Build all resources for production.
+sunpeak build          # Build resources and compile tools for production.
+sunpeak start          # Start the production MCP server.
 sunpeak upgrade        # Upgrade sunpeak to latest version.
 ```
 
@@ -62,31 +63,31 @@ Once your app is connected, send the name of the app and a tool, like `/sunpeak
 
 ## Build & Deploy
 
-Build your app for production:
+Build and start your app for production:
 
 ```bash
-sunpeak build
+sunpeak build && sunpeak start
 ```
 
-This creates optimized builds in `dist/`, organized by resource:
+`sunpeak build` creates optimized builds in `dist/`:
 
 ```bash
 dist/
 ├── albums/
 │   ├── albums.html           # Built resource bundle.
 │   └── albums.json           # ResourceConfig (extracted from .tsx).
-├── review/
-│   ├── review.html
-│   └── review.json
+├── tools/
+│   ├── show-albums.js        # Compiled tool handler + schema.
+│   └── ...
+├── server.js                 # Compiled server entry (if src/server.ts exists).
 └── ...
 ```
 
-Each resource folder contains:
+`sunpeak start` loads the compiled tools and resources, then starts a production MCP server with real handlers, Zod input validation, and optional auth.
 
-- **`.html` file**: Self-contained bundle with JS and CSS inlined
-- **`.json` file**: Resource metadata (extracted from the `resource` export in your `.tsx` file) with a generated `uri` for cache-busting
-
-Host these files and reference them as resources in your production MCP server.
+```bash
+sunpeak start --port 3000     # Custom port (default: 8000)
+```
 
 ## Add a new UI (Resource)
 

package/template/package.json

@@ -6,6 +6,7 @@
   "scripts": {
     "dev": "sunpeak dev",
     "build": "sunpeak build",
+    "start": "sunpeak start",
     "test": "vitest run",
     "test:e2e": "playwright test"
   },

package/template/src/server.ts

@@ -4,12 +4,14 @@ import type { AuthInfo } from 'sunpeak/mcp';
 /**
  * Optional server entry point.
  *
- * The `auth` function extracts authentication info from incoming HTTP requests.
- * The returned `AuthInfo` is available as `extra.authInfo` in tool handlers.
+ * Called on every MCP request. Return AuthInfo to authenticate, null to reject (401).
+ * The returned AuthInfo is available as `extra.authInfo` in tool handlers.
  */
-export function auth(req: IncomingMessage): AuthInfo {
-  const token = req.headers.authorization?.replace('Bearer ', '') ?? '';
-  return { token, clientId: 'my-app', scopes: [] };
+export async function auth(req: IncomingMessage): Promise<AuthInfo | null> {
+  const token = req.headers.authorization?.replace('Bearer ', '');
+  // Allow unauthenticated requests (no token = anonymous access).
+  // To require auth, return null here instead.
+  return { token: token ?? '', clientId: 'anonymous', scopes: [] };
 }
 
 export const server = { name: 'Sunpeak', version: '1.0.0' };

package/dist/index-BjnAsaqp.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"index-BjnAsaqp.js","sources":[],"sourcesContent":[],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;"}

package/dist/index-C9CVbGFt.cjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"index-C9CVbGFt.cjs","sources":[],"sourcesContent":[],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;"}