Add Patterns guide doc

AGENTS.md

@@ -82,6 +82,8 @@ Guest UI (App) <--PostMessageTransport--> Host (AppBridge) <--MCP Client--> MCP
 
 JSDoc `@example` tags use `{@includeCode ./file.examples.ts#regionName}` to pull in type-checked code from companion `.examples.ts`/`.examples.tsx` files. Regions are marked with `//#region name` and `//#endregion name`, wrapped in functions (whose parameters provide types for external values). Region names follow `exportedName_variant` or `ClassName_methodName_variant` pattern (e.g., `useApp_basicUsage`, `App_hostCapabilities_checkAfterConnection`).
 
+Standalone docs in `docs/` (listed in `typedoc.config.mjs` `projectDocuments`) can also have type-checked companion `.ts`/`.tsx` files using the same `@includeCode` pattern.
+
 ## Full Examples
 
 Uses npm workspaces. Full examples in `examples/` are separate packages:

docs/migrate_from_openai_apps.md

@@ -1,3 +1,7 @@
+---
+title: Migrate OpenAI App
+---
+
 # Migrating from OpenAI Apps SDK to MCP Apps SDK
 
 This guide helps you migrate from the OpenAI Apps SDK to the MCP Apps SDK (`@modelcontextprotocol/ext-apps`).
@@ -50,7 +54,7 @@ This guide helps you migrate from the OpenAI Apps SDK to the MCP Apps SDK (`@mod
 
 ### Server-Side Migration Example
 
-### Before (OpenAI)
+#### Before (OpenAI)
 
 ```typescript
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
@@ -110,7 +114,7 @@ function createServer() {
 }
 ```
 
-### After (MCP Apps)
+#### After (MCP Apps)
 
 ```typescript
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
@@ -184,7 +188,7 @@ function createServer() {
 6. **Helper Functions**: MCP provides `registerAppTool()` and `registerAppResource()` helpers
 7. **Not Yet Implemented**: `_meta["openai/toolInvocation/invoking"]`, `_meta["openai/toolInvocation/invoked"]`, and `_meta["openai/widgetDescription"]` don't have MCP equivalents yet
 
-## Client-side
+## Client-Side
 
 ### Quick Start Comparison
 
@@ -302,7 +306,7 @@ function createServer() {
 | —      | `app.getHostVersion()`      | Returns `{ name, version }` of host               |
 | —      | `app.getHostCapabilities()` | Check `serverTools`, `openLinks`, `logging`, etc. |
 
-### Full Migration Example
+### Client-Side Migration Example
 
 #### Before (OpenAI)
 

docs/patterns.md

@@ -0,0 +1,116 @@
+---
+title: Patterns
+---
+
+# MCP Apps Patterns
+
+This document covers common patterns and recipes for building MCP Apps.
+
+## Tools that are private to Apps
+
+Set {@link types!McpUiToolMeta.visibility Tool.\_meta.ui.visibility} to `["app"]` to make tools only callable by Apps (hidden from the model). This is useful for UI-driven actions like updating quantities, toggling settings, or other interactions that shouldn't appear in the model's tool list.
+
+{@includeCode ../src/server/index.examples.ts#registerAppTool_appOnlyVisibility}
+
+_See [`examples/system-monitor-server/`](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/system-monitor-server) for a full implementation of this pattern._
+
+## Reading large amounts of data via chunked tool calls
+
+Some host platforms have size limits on tool call responses, so large files (PDFs, images, etc.) cannot be sent in a single response. Use an app-only tool with chunked responses to bypass these limits while keeping the data out of model context.
+
+**Server-side**: Register an app-only tool that returns data in chunks with pagination metadata:
+
+{@includeCode ./patterns.tsx#chunkedDataServer}
+
+**Client-side**: Loop calling the tool until all chunks are received:
+
+{@includeCode ./patterns.tsx#chunkedDataClient}
+
+_See [`examples/pdf-server/`](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/pdf-server) for a full implementation of this pattern._
+
+## Giving errors back to model
+
+**Server-side**: Tool handler validates inputs and returns `{ isError: true, content: [...] }`. The model receives this error through the normal tool call response.
+
+**Client-side**: If a runtime error occurs (e.g., API failure, permission denied, resource unavailable), use {@link app!App.updateModelContext updateModelContext} to inform the model:
+
+{@includeCode ../src/app.examples.ts#App_updateModelContext_reportError}
+
+## Matching host styling (CSS variables, theme, and fonts)
+
+Use the SDK's style helpers to apply host styling, then reference them in your CSS:
+
+- **CSS variables** — Use `var(--color-background-primary)`, etc. in your CSS
+- **Theme** — Use `[data-theme="dark"]` selectors or `light-dark()` function for theme-aware styles
+- **Fonts** — Use `var(--font-sans)` or `var(--font-mono)` with fallbacks (e.g., `font-family: var(--font-sans, system-ui, sans-serif)`)
+
+**Vanilla JS:**
+
+{@includeCode ./patterns.tsx#hostStylingVanillaJs}
+
+**React:**
+
+{@includeCode ./patterns.tsx#hostStylingReact}
+
+_See [`examples/basic-server-vanillajs/`](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/basic-server-vanillajs) and [`examples/basic-server-react/`](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/basic-server-react) for full implementations of this pattern._
+
+## Entering / Exiting fullscreen
+
+Toggle fullscreen mode by calling {@link app!App.requestDisplayMode requestDisplayMode}:
+
+{@includeCode ../src/app.examples.ts#App_requestDisplayMode_toggle}
+
+Listen for display mode changes via {@link app!App.onhostcontextchanged onhostcontextchanged} to update your UI:
+
+{@includeCode ../src/app.examples.ts#App_onhostcontextchanged_respondToDisplayMode}
+
+_See [`examples/shadertoy-server/`](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/shadertoy-server) for a full implementation of this pattern._
+
+## Passing contextual information from the App to the Model
+
+Use {@link app!App.updateModelContext updateModelContext} to keep the model informed about what the user is viewing or interacting with. Structure the content with YAML frontmatter for easy parsing:
+
+{@includeCode ../src/app.examples.ts#App_updateModelContext_appState}
+
+_See [`examples/map-server/`](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/map-server) for a full implementation of this pattern._
+
+## Sending large follow-up messages
+
+When you need to send more data than fits in a message, use {@link app!App.updateModelContext updateModelContext} to set the context first, then {@link app!App.sendMessage sendMessage} with a brief prompt to trigger a response:
+
+{@includeCode ../src/app.examples.ts#App_sendMessage_withLargeContext}
+
+_See [`examples/transcript-server/`](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/transcript-server) for a full implementation of this pattern._
+
+## Persisting widget state
+
+To persist widget state across conversation reloads (e.g., current page in a PDF viewer, camera position in a map), use [`localStorage`](https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage) with a stable identifier provided by the server.
+
+**Server-side**: Tool handler generates a unique `widgetUUID` and returns it in `CallToolResult._meta.widgetUUID`:
+
+{@includeCode ./patterns.tsx#persistDataServer}
+
+**Client-side**: Receive the UUID in {@link app!App.ontoolresult ontoolresult} and use it as the storage key:
+
+{@includeCode ./patterns.tsx#persistData}
+
+_See [`examples/map-server/`](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/map-server) for a full implementation of this pattern._
+
+## Pausing computation-heavy widgets when out of view
+
+Widgets with animations, WebGL rendering, or polling can consume significant CPU/GPU even when scrolled out of view. Use [`IntersectionObserver`](https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API) to pause expensive operations when the widget isn't visible:
+
+{@includeCode ./patterns.tsx#visibilityBasedPause}
+
+_See [`examples/shadertoy-server/`](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/shadertoy-server) for a full implementation of this pattern._
+
+## Lowering perceived latency
+
+Use {@link app!App.ontoolinputpartial ontoolinputpartial} to receive streaming tool arguments as they arrive, allowing you to show a loading preview before the complete input is available.
+
+{@includeCode ../src/app.examples.ts#App_ontoolinputpartial_progressiveRendering}
+
+> [!IMPORTANT]
+> Partial arguments are "healed" JSON — the host closes unclosed brackets/braces to produce valid JSON. This means objects may be incomplete (e.g., the last item in an array may be truncated). Don't rely on partial data for critical operations; use it only for preview UI.
+
+_See [`examples/threejs-server/`](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/threejs-server) for a full implementation of this pattern._