281 changed files with 4134 additions and 31291 deletions
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@ -24,8 +24,7 @@ jobs:

      - uses: actions/setup-node@v6
        with:
-          node-version: "22"
-          cache: npm
+          node-version: "20"

      - run: npm ci

@ -72,17 +71,12 @@ jobs:

      - uses: actions/setup-node@v6
        with:
-          node-version: "22"
-          cache: npm
+          node-version: "20"

-      - run: npm ci
+      - run: npm install

      - run: npm run build

-      - name: Validate TypeDoc links
-        if: runner.os == 'Linux' && matrix.name == 'Linux x64'
-        run: npm exec typedoc -- --treatValidationWarningsAsErrors --emit none
-
      - run: npm run examples:build

      - name: Verify generated schemas are up-to-date
@ -103,32 +97,9 @@ jobs:

      - name: Build MCPB bundle (pdf-server)
        if: runner.os == 'Linux' && matrix.name == 'Linux x64'
-        run: node build-mcpb.mjs
+        run: npx -y @anthropic-ai/mcpb pack
        working-directory: examples/pdf-server

-      - name: Smoke-test MCPB bundle starts
-        if: runner.os == 'Linux' && matrix.name == 'Linux x64'
-        run: |
-          unzip -q pdf-server.mcpb -d .mcpb-smoke
-          node .mcpb-smoke/dist/index.js --stdio < /dev/null 2>&1 | tee /tmp/mcpb-smoke.log
-          grep -q "Ready" /tmp/mcpb-smoke.log
-        working-directory: examples/pdf-server
-
-  dependency-isolation:
-    name: Dependency isolation
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v6
-
-      - uses: actions/setup-node@v6
-        with:
-          node-version: "22"
-          cache: npm
-
-      - run: npm ci
-
-      - run: npm run test:dependency-isolation
-
  e2e:
    runs-on: ubuntu-latest
    steps:
@ -140,17 +111,14 @@ jobs:

      - uses: actions/setup-node@v6
        with:
-          node-version: "22"
-          cache: npm
+          node-version: "20"

      - uses: astral-sh/setup-uv@v7

      - run: npm ci

-      # Headless runs without a channel use chromium-headless-shell, so the
-      # full Chromium build (about 165 MB) would only be downloaded, never run.
      - name: Install Playwright browsers
-        run: npx playwright install --with-deps --only-shell chromium
+        run: npx playwright install --with-deps chromium

      - name: Run E2E tests
        run: npx playwright test --reporter=list
@ -179,18 +147,13 @@ jobs:
        shell: wsl-bash {0}
        run: |
          sudo apt-get update
-          curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash -
+          curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
          sudo apt-get install -y nodejs

-      # The checkout lives on the Windows drive, which WSL reaches over 9P;
-      # writing node_modules there is what makes this job slow (npm ci alone
-      # took about 3 minutes). Copy the tree onto the distro's ext4 filesystem
-      # first, as Microsoft's WSL guidance recommends for anything I/O heavy.
      - name: Build and test in WSL
        shell: wsl-bash {0}
        run: |
-          cp -r "$(pwd)" ~/ext-apps && cd ~/ext-apps
-          npm ci
+          npm install
          npm run build
          npm run examples:build
          npm test
@ -219,18 +182,15 @@ jobs:
    steps:
      - uses: actions/setup-node@v6
        with:
-          node-version: "22"
+          node-version: "20"

      - name: Create test project and install from git
        shell: bash
-        env:
-          HEAD_REPO: ${{ github.event.pull_request.head.repo.full_name || github.repository }}
-          HEAD_REF: ${{ github.head_ref || github.ref_name }}
        run: |
          mkdir test-project
          cd test-project
          npm init -y
          # Install from the PR branch (use head repo for fork PRs)
-          npm install "git+https://github.com/${HEAD_REPO}#${HEAD_REF}"
+          npm install "git+https://github.com/${{ github.event.pull_request.head.repo.full_name || github.repository }}#${{ github.head_ref || github.ref_name }}"
          # Verify the package is usable (ESM import)
          node --input-type=module -e "import { App } from '@modelcontextprotocol/ext-apps'; console.log('Import successful:', typeof App)"
--- a/.github/workflows/docs-preview.yml
+++ b/.github/workflows/docs-preview.yml
@ -1,65 +0,0 @@
-name: Docs Preview
-
-on:
-  pull_request:
-    types: [opened, synchronize, reopened, closed]
-    paths:
-      - "docs/**"
-      - "src/**"
-      - "README.md"
-      - "typedoc.config.mjs"
-      - "scripts/typedoc-*.mjs"
-      - ".github/workflows/docs-preview.yml"
-
-permissions:
-  contents: read
-  pull-requests: write
-
-concurrency:
-  group: docs-preview-${{ github.event.pull_request.number }}
-  cancel-in-progress: true
-
-jobs:
-  build-and-deploy:
-    # Refuse to run for fork PRs — forks do not have access to the Cloudflare
-    # secrets, so deploys would fail anyway.
-    if: >-
-      github.event.action != 'closed' &&
-      github.event.pull_request.head.repo.full_name == github.repository
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v6
-
-      - uses: actions/setup-node@v6
-        with:
-          node-version: "22"
-          cache: npm
-
-      - run: npm ci
-
-      - run: npm run build
-
-      - run: npm run docs
-
-      - name: Deploy preview
-        uses: modelcontextprotocol/actions/cloudflare-pages-preview/deploy@main
-        with:
-          directory: docs
-          project-name: mcp-ext-apps-docs-preview
-          api-token: ${{ secrets.CF_PAGES_PREVIEW_API_TOKEN }}
-          account-id: ${{ secrets.CF_PAGES_PREVIEW_ACCOUNT_ID }}
-          comment-title: "📖 Docs Preview Deployed"
-          comment-marker: "<!-- docs-preview-comment -->"
-
-  cleanup:
-    if: >-
-      github.event.action == 'closed' &&
-      github.event.pull_request.head.repo.full_name == github.repository
-    runs-on: ubuntu-latest
-    steps:
-      - uses: modelcontextprotocol/actions/cloudflare-pages-preview/cleanup@main
-        with:
-          project-name: mcp-ext-apps-docs-preview
-          api-token: ${{ secrets.CF_PAGES_PREVIEW_API_TOKEN }}
-          account-id: ${{ secrets.CF_PAGES_PREVIEW_ACCOUNT_ID }}
-          comment-marker: "<!-- docs-preview-comment -->"
--- a/.github/workflows/docs.yml
+++ b/.github/workflows/docs.yml
@ -16,9 +16,8 @@ jobs:
      - uses: oven-sh/setup-bun@v2
      - uses: actions/setup-node@v6
        with:
-          node-version: "22"
-          cache: npm
-      - run: npm ci
+          node-version: "20"
+      - run: npm install
      - run: npm run build
      - run: npm run docs
      - uses: peaceiris/actions-gh-pages@v4
@ -27,4 +26,3 @@ jobs:
          publish_dir: ./docs
          publish_branch: gh-pages
          keep_files: true
-          cname: apps.extensions.modelcontextprotocol.io
--- a/.github/workflows/npm-publish.yml
+++ b/.github/workflows/npm-publish.yml
@ -42,10 +42,6 @@ jobs:
      - run: npm ci
      - run: npm test

-  # All publish jobs depend directly on [build, test] (not on each other) so
-  # they all enter "waiting for approval" together and can be approved in a
-  # single "Review deployments" click.
-
  publish:
    runs-on: ubuntu-latest
    if: github.event_name == 'release'
@ -92,7 +88,7 @@ jobs:
    runs-on: ubuntu-latest
    if: github.event_name == 'release'
    environment: Release
-    needs: [build, test]
+    needs: [publish]

    permissions:
      contents: read
@ -112,7 +108,6 @@ jobs:
          - cohort-heatmap-server
          - customer-segmentation-server
          - debug-server
-          - lazy-auth-server
          - map-server
          - pdf-server
          - scenario-modeler-server
@ -139,18 +134,8 @@ jobs:
      - name: Build example
        run: npm run build --workspace examples/${{ matrix.example }}

-      - name: Determine npm tag
-        id: npm-tag
-        run: |
-          VERSION=$(node -p "require('./package.json').version")
-          if [[ "$VERSION" == *"-"* ]]; then
-            echo "tag=--tag beta" >> $GITHUB_OUTPUT
-          else
-            echo "tag=" >> $GITHUB_OUTPUT
-          fi
-
      - name: Publish example
-        run: npm publish --workspace examples/${{ matrix.example }} --provenance --access public ${{ steps.npm-tag.outputs.tag }}
+        run: npm publish --workspace examples/${{ matrix.example }} --provenance --access public
        env:
          NODE_AUTH_TOKEN: ${{ secrets.NPM_SECRET }}

@ -158,7 +143,7 @@ jobs:
    runs-on: ubuntu-latest
    if: github.event_name == 'release'
    environment: Release
-    needs: [build, test]
+    needs: [publish-examples]

    permissions:
      contents: write
@ -174,8 +159,12 @@ jobs:
          cache: npm
      - run: npm ci

-      - name: Build pdf-server + MCPB bundle
-        run: npm run build:mcpb --workspace examples/pdf-server
+      - name: Build pdf-server
+        run: npm run build --workspace examples/pdf-server
+
+      - name: Pack MCPB bundle
+        run: npx -y @anthropic-ai/mcpb pack
+        working-directory: examples/pdf-server

      - name: Upload MCPB to release
        run: gh release upload "${{ github.event.release.tag_name }}" examples/pdf-server/*.mcpb --clobber
--- a/.github/workflows/publish.yml
+++ b/.github/workflows/publish.yml
@ -34,7 +34,6 @@ jobs:
            ./examples/cohort-heatmap-server \
            ./examples/customer-segmentation-server \
            ./examples/debug-server \
-            ./examples/lazy-auth-server \
            ./examples/map-server \
            ./examples/pdf-server \
            ./examples/scenario-modeler-server \
--- a/.github/workflows/update-snapshots.yml
+++ b/.github/workflows/update-snapshots.yml
@ -16,14 +16,10 @@ permissions:

 jobs:
  update-snapshots:
-    # Run on workflow_dispatch OR when a maintainer comments "/update-snapshots" on a PR.
-    # author_association check prevents arbitrary commenters from triggering a job with
-    # contents:write that pushes a [skip ci] commit to the PR branch.
+    # Run on workflow_dispatch OR when someone comments "/update-snapshots" on a PR
    if: >
      github.event_name == 'workflow_dispatch' ||
-      (github.event.issue.pull_request &&
-      contains(github.event.comment.body, '/update-snapshots') &&
-      contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.comment.author_association))
+      (github.event.issue.pull_request && contains(github.event.comment.body, '/update-snapshots'))
    runs-on: ubuntu-latest
    steps:
      - name: Get PR branch
@ -63,8 +59,7 @@ jobs:

      - uses: actions/setup-node@v6
        with:
-          node-version: "22"
-          cache: npm
+          node-version: "20"

      - uses: astral-sh/setup-uv@v7

--- a/.gitignore
+++ b/.gitignore
@ -15,6 +15,4 @@ __pycache__/
 *.pyc

 # MCPB bundles (built artifacts)
-*.mcpb
-.mcpb-stage/
-.mcpb-smoke/
+*.mcpb
--- a/.husky/pre-commit
+++ b/.husky/pre-commit
@ -14,16 +14,8 @@ if grep -E '"resolved": "https?://' package-lock.json | grep -v registry.npmjs.o
  exit 1
 fi

-# Capture staged files so we only re-stage what the user intended to commit
-# (avoids sweeping unrelated WIP into the commit). --diff-filter=d skips
-# deletions so the xargs git add below doesn't fail on removed paths.
-STAGED=$(git diff --name-only --cached --diff-filter=d)
-
 npm run build:all
 npm run prettier:fix

-# Re-stage originally-staged files (prettier may have reformatted them)
-echo "$STAGED" | xargs -r git add
-
-# Also stage generated files (regenerated by build:all from spec.types.ts)
-git add src/generated/
+# Stage any files reformatted by prettier (generated files, source, docs, etc.)
+git diff --name-only --diff-filter=M | xargs -r git add
--- a/.npmrc
+++ b/.npmrc
@ -1 +0,0 @@
-registry=https://registry.npmjs.org/
--- a/.prettierignore
+++ b/.prettierignore
@ -5,5 +5,4 @@ examples/basic-server-*/**/*.tsx
 examples/quickstart/**/*.ts
 **/vendor/**
 **/.build/**
-**/.claude/**
 SKILL.md
--- a/AGENTS.md
+++ b/AGENTS.md
@ -39,10 +39,7 @@ npm test
 # Check JSDoc comment syntax and `{@link}` references
 npm exec typedoc -- --treatValidationWarningsAsErrors --emit none

-# Regenerate package-lock.json
-# Note: repo .npmrc pins registry to npmjs.org, so a plain `npm i` is safe even
-# if your global npm config points elsewhere. The Docker step below is optional
-# — it locks linux-amd64 optionalDependencies (sharp, rollup, bun) for CI.
+# Regenerate package-lock.json (especially on setups w/ custom npm registry)
 rm -fR  package-lock.json node_modules && \
  docker run  --rm -it --platform linux/amd64 -v $PWD:/src:rw -w /src node:latest npm i && \
  rm -fR node_modules && \
@ -60,8 +57,8 @@ rm -fR  package-lock.json node_modules && \

 ### Key Source Files

- `src/app.ts` - `App` subclasses `Protocol` from `@modelcontextprotocol/client`, handles View initialization, tool calls, and messaging
- `src/app-bridge.ts` - `AppBridge` subclasses `Protocol` from `@modelcontextprotocol/client` for the iframe channel and proxies through a separate outer `Client`
+- `src/app.ts` - `App` class extends MCP Protocol, handles guest initialization, tool calls, messaging
+- `src/app-bridge.ts` - `AppBridge` class for hosts, proxies MCP requests, sends tool input/results to guests
 - `src/server/index.ts` - Helpers for MCP servers to register tools/resources with UI metadata
 - `src/types.ts` - Protocol types re-exported from `spec.types.ts` and Zod schemas from `generated/schema.ts` (auto-generated during build)
 - `src/message-transport.ts` - `PostMessageTransport` for iframe communication
@ -70,12 +67,12 @@ rm -fR  package-lock.json node_modules && \
 ### Protocol Flow

 ```
-View (App/Protocol) <--PostMessageTransport--> Host (AppBridge/Protocol) <--separate MCP Client--> MCP Server
+View (App) <--PostMessageTransport--> Host (AppBridge) <--MCP Client--> MCP Server
 ```

 1. Host creates iframe with view HTML
 2. View creates `App` instance and calls `connect()` with `PostMessageTransport`
-3. View sends `ui/initialize` (the only handshake on the iframe channel) and receives authoritative Apps capabilities and context
+3. View sends `ui/initialize` request, receives host capabilities and context
 4. Host sends `sendToolInput()` with tool arguments after initialization
 5. View can call server tools via `app.callServerTool()` or send messages via `app.sendMessage()`
 6. Host sends `sendToolResult()` when tool execution completes
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@ -25,15 +25,6 @@ We welcome contributions to the MCP Apps SDK! This document outlines the process
 - Update documentation as needed
 - Keep changes focused and atomic
 - Provide a clear description of changes
- **Keep "Allow edits by maintainers" checked** when opening your PR — this lets maintainers rebase your branch and lets the [`/update-snapshots` workflow](#updating-snapshots-in-ci) push updated screenshots to it
-
-## Examples Policy
-
-The examples in `examples/` are maintained by the core team. **We do not accept pull requests that add new example servers from outside contributors.** Each example carries an ongoing maintenance cost — keeping it building, tested, and up to date with SDK changes — so we are deliberate about what we add.
-
-If you have an idea for an example that would provide significant educational value, please [open an issue](https://github.com/modelcontextprotocol/ext-apps/issues) describing what the example would demonstrate and why it would be useful, and maintainers will evaluate the request.
-
-PRs that add new examples without a prior approved issue may be closed.

 ## Running Examples

@ -49,408 +40,6 @@ Or build and run examples:
 npm run examples:start
 ```

-### With MCP Clients
-
-To use these examples with MCP clients that support the stdio transport (such as Claude Desktop or VS Code), add this MCP server configuration to your client's settings:
-
-<details>
-<summary>MCP client configuration for all examples (using stdio)</summary>
-
-```json
-{
-  "mcpServers": {
-    "basic-react": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-basic-react",
-        "--stdio"
-      ]
-    },
-    "basic-vanillajs": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-basic-vanillajs",
-        "--stdio"
-      ]
-    },
-    "basic-vue": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-basic-vue",
-        "--stdio"
-      ]
-    },
-    "basic-svelte": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-basic-svelte",
-        "--stdio"
-      ]
-    },
-    "basic-preact": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-basic-preact",
-        "--stdio"
-      ]
-    },
-    "basic-solid": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-basic-solid",
-        "--stdio"
-      ]
-    },
-    "budget-allocator": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-budget-allocator",
-        "--stdio"
-      ]
-    },
-    "cohort-heatmap": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-cohort-heatmap",
-        "--stdio"
-      ]
-    },
-    "customer-segmentation": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-customer-segmentation",
-        "--stdio"
-      ]
-    },
-    "map": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-map",
-        "--stdio"
-      ]
-    },
-    "pdf": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-pdf",
-        "--stdio"
-      ]
-    },
-    "scenario-modeler": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-scenario-modeler",
-        "--stdio"
-      ]
-    },
-    "shadertoy": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-shadertoy",
-        "--stdio"
-      ]
-    },
-    "sheet-music": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-sheet-music",
-        "--stdio"
-      ]
-    },
-    "system-monitor": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-system-monitor",
-        "--stdio"
-      ]
-    },
-    "threejs": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-threejs",
-        "--stdio"
-      ]
-    },
-    "transcript": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-transcript",
-        "--stdio"
-      ]
-    },
-    "video-resource": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-video-resource",
-        "--stdio"
-      ]
-    },
-    "wiki-explorer": {
-      "command": "npx",
-      "args": [
-        "-y",
-        "--silent",
-        "--registry=https://registry.npmjs.org/",
-        "@modelcontextprotocol/server-wiki-explorer",
-        "--stdio"
-      ]
-    },
-    "qr": {
-      "command": "uv",
-      "args": [
-        "run",
-        "/path/to/ext-apps/examples/qr-server/server.py",
-        "--stdio"
-      ]
-    },
-    "say": {
-      "command": "uv",
-      "args": [
-        "run",
-        "--default-index",
-        "https://pypi.org/simple",
-        "https://raw.githubusercontent.com/modelcontextprotocol/ext-apps/refs/heads/main/examples/say-server/server.py",
-        "--stdio"
-      ]
-    }
-  }
-}
-```
-
-</details>
-
-> [!NOTE]
-> The `qr` server requires cloning the repository first. See [qr-server README](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/qr-server) for details.
-
-### Local Development
-
-To test local modifications with MCP clients, first clone and install the repository:
-
-```bash
-git clone https://github.com/modelcontextprotocol/ext-apps.git
-cd ext-apps
-npm install
-```
-
-Then configure your MCP client to build and run the local server. Replace `~/src/ext-apps` with your actual clone path.
-
-Most example servers have a `start:stdio` script that builds and launches in stdio mode:
-
-<details>
-<summary>MCP client configuration for local development (all examples)</summary>
-
-```json
-{
-  "mcpServers": {
-    "basic-react": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/basic-server-react && npm --silent run start:stdio"
-      ]
-    },
-    "basic-vanillajs": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/basic-server-vanillajs && npm --silent run start:stdio"
-      ]
-    },
-    "basic-vue": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/basic-server-vue && npm --silent run start:stdio"
-      ]
-    },
-    "basic-svelte": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/basic-server-svelte && npm --silent run start:stdio"
-      ]
-    },
-    "basic-preact": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/basic-server-preact && npm --silent run start:stdio"
-      ]
-    },
-    "basic-solid": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/basic-server-solid && npm --silent run start:stdio"
-      ]
-    },
-    "budget-allocator": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/budget-allocator-server && npm --silent run start:stdio"
-      ]
-    },
-    "cohort-heatmap": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/cohort-heatmap-server && npm --silent run start:stdio"
-      ]
-    },
-    "customer-segmentation": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/customer-segmentation-server && npm --silent run start:stdio"
-      ]
-    },
-    "map": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/map-server && npm --silent run start:stdio"
-      ]
-    },
-    "pdf": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/pdf-server && npm --silent run start:stdio"
-      ]
-    },
-    "scenario-modeler": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/scenario-modeler-server && npm --silent run start:stdio"
-      ]
-    },
-    "shadertoy": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/shadertoy-server && npm --silent run start:stdio"
-      ]
-    },
-    "sheet-music": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/sheet-music-server && npm --silent run start:stdio"
-      ]
-    },
-    "system-monitor": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/system-monitor-server && npm --silent run start:stdio"
-      ]
-    },
-    "threejs": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/threejs-server && npm --silent run start:stdio"
-      ]
-    },
-    "transcript": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/transcript-server && npm --silent run start:stdio"
-      ]
-    },
-    "video-resource": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/video-resource-server && npm --silent run start:stdio"
-      ]
-    },
-    "wiki-explorer": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "cd ~/src/ext-apps/examples/wiki-explorer-server && npm --silent run start:stdio"
-      ]
-    },
-    "qr": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "uv run ~/src/ext-apps/examples/qr-server/server.py --stdio"
-      ]
-    },
-    "say": {
-      "command": "bash",
-      "args": [
-        "-c",
-        "uv run --index https://pypi.org/simple ~/src/ext-apps/examples/say-server/server.py --stdio"
-      ]
-    }
-  }
-}
-```
-
-</details>
-
-This configuration rebuilds each server on launch, ensuring your local changes are picked up.
-
 ## Testing

 ### Unit Tests
@ -502,7 +91,7 @@ Alternatively, use the [workflow dispatch](https://github.com/modelcontextprotoc

 ## Code of Conduct

-This project follows our [Code of Conduct](https://github.com/modelcontextprotocol/.github/blob/main/CODE_OF_CONDUCT.md). Please review it before contributing.
+This project follows our [Code of Conduct](CODE_OF_CONDUCT.md). Please review it before contributing.

 ## Reporting Issues

@ -539,17 +128,40 @@ Before publishing releases, ensure the following are configured:

 ### Publishing a Release

-1. **Bump the version** across the root and all workspace packages:
+Releases are published automatically via GitHub Actions when a GitHub Release is created.
+
+#### Steps to publish:
+
+1. **Update the version** in `package.json`:

   ```bash
-   npm run bump -- minor   # or: patch | major | prerelease --preid=beta | 1.7.0
+   # For a regular release
+   npm version patch  # or minor, or major
+
+   # For a beta release
+   npm version prerelease --preid=beta
   ```

-   Commit and open a PR with a grouped changelog in the body (see prior `chore: bump …` PRs for the format).
+2. **Commit the version bump** (if not done by `npm version`):

-2. **Merge the PR**, then [draft a GitHub Release](https://github.com/modelcontextprotocol/ext-apps/releases/new) — create a `vX.Y.Z` tag on `main`, paste the changelog, publish.
+   ```bash
+   git add package.json
+   git commit -m "Bump version to X.Y.Z"
+   git push origin main
+   ```

-3. **Approve the deployment** — publishing the Release triggers the [npm-publish workflow](https://github.com/modelcontextprotocol/ext-apps/actions/workflows/npm-publish.yml); all publish jobs wait together for a single "Review deployments" approval.
+3. **Create a GitHub Release**:
+   - Go to [Releases](https://github.com/modelcontextprotocol/ext-apps/releases)
+   - Click "Draft a new release"
+   - Create a new tag matching the version (e.g., `v0.1.0`)
+   - Set the target branch (usually `main`)
+   - Write release notes describing the changes
+   - Click "Publish release"
+
+4. **Monitor the workflow**:
+   - The [npm-publish workflow](https://github.com/modelcontextprotocol/ext-apps/actions/workflows/npm-publish.yml) will trigger automatically
+   - It runs build and test jobs before publishing
+   - On success, the package is published to npm with provenance

 #### npm Tags

@ -573,7 +185,7 @@ To release a patch for an older version:

 ### Testing Pre-releases

-Every commit and PR automatically publishes a preview package via [pkg-pr-new](https://github.com/stackblitz-labs/pkg.pr.new). Check the PR comments or workflow logs for the install command.
+Every commit and PR automatically publishes a preview package via [pkg-pr-new](https://github.com/pkg-pr-new/pkg-pr-new). Check the PR comments or workflow logs for the install command.

 ---

--- a/README.md
+++ b/README.md
@ -1,19 +1,16 @@
 <!-- LOGO -->
 <div align="center">
-  <picture>
-    <source media="(prefers-color-scheme: dark)" srcset="media/mcp-white.svg">
-    <source media="(prefers-color-scheme: light)" srcset="media/mcp.svg">
-    <img src="media/mcp.svg" alt="MCP Apps" width="128">
-  </picture>
+  <img src="media/mcp.svg#gh-light-mode-only" alt="MCP Apps" width="128">
+  <img src="media/mcp-white.svg#gh-dark-mode-only" alt="MCP Apps" width="128">
  <h1>MCP Apps</h1>
  <p>
    Build interactive UIs for MCP tools — charts, forms, dashboards — that render inline in Claude, ChatGPT and any other compliant chat client.
    <br /><br />
    <a href="#why-mcp-apps">Why</a>
    ·
-    <a href="https://apps.extensions.modelcontextprotocol.io/api/documents/quickstart.html">Quickstart</a>
+    <a href="https://modelcontextprotocol.github.io/ext-apps/api/documents/Quickstart.html">Quickstart</a>
    ·
-    <a href="https://apps.extensions.modelcontextprotocol.io/api/">API Docs</a>
+    <a href="https://modelcontextprotocol.github.io/ext-apps/api/">API Docs</a>
    ·
    <a href="https://github.com/modelcontextprotocol/ext-apps/blob/main/specification/2026-01-26/apps.mdx">Spec</a>
    ·
@ -27,7 +24,7 @@
  <a href="https://www.npmjs.com/package/@modelcontextprotocol/ext-apps"><img src="https://img.shields.io/npm/v/@modelcontextprotocol/ext-apps.svg" alt="npm version"></a>
  <a href="https://www.npmjs.com/package/@modelcontextprotocol/ext-apps"><img src="https://img.shields.io/npm/dm/@modelcontextprotocol/ext-apps.svg" alt="npm downloads"></a>
  <a href="https://github.com/modelcontextprotocol/ext-apps"><img src="https://img.shields.io/github/stars/modelcontextprotocol/ext-apps" alt="GitHub stars"></a>
-  <a href="https://apps.extensions.modelcontextprotocol.io/api/"><img src="https://img.shields.io/badge/docs-API%20Reference-blue" alt="API Documentation"></a>
+  <a href="https://modelcontextprotocol.github.io/ext-apps/api/"><img src="https://img.shields.io/badge/docs-API%20Reference-blue" alt="API Documentation"></a>
 </p>

 <p align="center">
@ -89,8 +86,6 @@ it will guide you through the rest.
  <a href="https://block.github.io/goose/docs/tutorials/building-mcp-apps/"><img src="https://img.shields.io/badge/Goose-docs-000000?logo=goose&logoColor=white" alt="Goose"></a>
  <a href="https://learning.postman.com/docs/postman-ai/mcp-requests/interact"><img src="https://img.shields.io/badge/Postman-docs-FF6C37?logo=postman&logoColor=white" alt="Postman"></a>
  <a href="https://www.mcpjam.com/blog/mcp-apps-example"><img src="https://img.shields.io/badge/MCPJam-docs-8B5CF6" alt="MCPJam"></a>
-  <a href="https://manufact.com/inspector"><img src="https://img.shields.io/badge/mcp--use-inspector-E5F3FD" alt="mcp-use"></a>
-  <a href="https://docs.alpic.ai/distribution/playground"><img src="https://img.shields.io/badge/Alpic-playground-E90060?logo=data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAGQAAABkCAMAAABHPGVmAAAAKlBMVEUKDhz%2F%2F%2F%2BjpaogJDFBRE%2Fw8PHHyMvh4eNmaHF1d4CUlpuFho2ztLhWWWP5YkbJAAAACXBIWXMAAAsTAAALEwEAmpwYAAAB1klEQVR42u2Y0ZKDIAxFBQQF8f9%2FdyW7dhAu7U7Iy87mzvShGfXU3CTGLotKpVKpVCqV6h%2FI2VuxfF3tUwcdVEccA2LNS%2BWCq2mUykG%2BCtg5iNmv76mllOApCPHrFQgNxJf8HHIQs10XdFtDKcEKPQ0x4brg6htKWGr0PIR8jq0tj4oQgJiIzD8rtATErMAWMj%2FxIYcBPjuPgoENcW3Jks%2BdLeXS32jLmise%2BZxQ8GRD%2BkkCbSlByi0Pgm3p0P6nJ1meXJ%2F8K1tKo7qUOFM4wdxEMMS4iSp9sqFJQrZ4hOZBTEa5gbaQ%2BTwI%2FcCu8TOq482xIWZkSx8MfAi0xcOEJTZkULKohXjm29epGU2SIGK%2BfT9J%2Bjre%2BRBYsiUYBSHkaEI2B0EInRx%2BkbApiB89EaMgBNdx7u5vDoJH79ne3yQElqxvEzYLKY%2Bl81PCZiFUsvlDwqYhw80uSkJg4z8Ttsss3OltwgQgMGGPlpSAwITVM0wCgius6iARCGzJcn%2BHJCSMXraCIATPsPW2SggCh364a1sIgveUew%2BTgtBGsuE9zDspyLBZ3M5aVCOCUDFlqXUbrm8j7%2FnvJ2B9G3kf%2BZBlt0iu%2Fr%2BNxHqRU6lUKpVKpVL9UX0BOrAPfcbTY8UAAAAASUVORK5CYII%3D" alt="Alpic Playground"></a>
 </p>

 > [!NOTE]
@ -122,36 +117,12 @@ resources:

 ## Getting Started

-Requires Node.js 20+. The base MCP SDK packages are `^2.0.0` peers of
-`ext-apps` (`@modelcontextprotocol/core` is a required peer that `client` already depends on, so npm installs it for you).
-
-For a View or host:
-
 ```bash
-npm install -S @modelcontextprotocol/ext-apps \
-  @modelcontextprotocol/client@^2.0.0 \
-  zod@^4.2.0
+npm install -S @modelcontextprotocol/ext-apps
 ```

-For an MCP server, add the server package (and, for HTTP transports, the Node
-and Express adapters):
-
-```bash
-npm install -S @modelcontextprotocol/ext-apps \
-  @modelcontextprotocol/client@^2.0.0 \
-  @modelcontextprotocol/server@^2.0.0 \
-  @modelcontextprotocol/node@^2.0.0 \
-  @modelcontextprotocol/express@^2.0.0 \
-  zod@^4.2.0
-```
-
-The wire protocol is unchanged between `ext-apps` 1.x and 2.x: a 2.x View works
-in a 1.x host and a 2.x host renders 1.x Views. See the
-[migration guide](https://apps.extensions.modelcontextprotocol.io/api/documents/migrate-to-v2.html)
-when upgrading from 1.x.
-
 **New here?** Start with the
-[Quickstart Guide](https://apps.extensions.modelcontextprotocol.io/api/documents/quickstart.html)
+[Quickstart Guide](https://modelcontextprotocol.github.io/ext-apps/api/documents/Quickstart.html)
 to build your first MCP App.

 ## Using the SDK
@ -162,10 +133,10 @@ UI metadata.

 | Package                                     | Purpose                                                   | Docs                                                                                                                |
 | ------------------------------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
-| `@modelcontextprotocol/ext-apps`            | Build interactive Views (App class, PostMessageTransport) | [API Docs →](https://apps.extensions.modelcontextprotocol.io/api/modules/app.html)                                  |
-| `@modelcontextprotocol/ext-apps/react`      | React hooks for Views (useApp, useHostStyles, etc.)       | [API Docs →](https://apps.extensions.modelcontextprotocol.io/api/modules/_modelcontextprotocol_ext-apps_react.html) |
-| `@modelcontextprotocol/ext-apps/app-bridge` | Embed and communicate with Views in your chat client      | [API Docs →](https://apps.extensions.modelcontextprotocol.io/api/modules/app-bridge.html)                           |
-| `@modelcontextprotocol/ext-apps/server`     | Register tools and resources on your MCP server           | [API Docs →](https://apps.extensions.modelcontextprotocol.io/api/modules/server-helpers.html)                       |
+| `@modelcontextprotocol/ext-apps`            | Build interactive Views (App class, PostMessageTransport) | [API Docs →](https://modelcontextprotocol.github.io/ext-apps/api/modules/app.html)                                  |
+| `@modelcontextprotocol/ext-apps/react`      | React hooks for Views (useApp, useHostStyles, etc.)       | [API Docs →](https://modelcontextprotocol.github.io/ext-apps/api/modules/_modelcontextprotocol_ext-apps_react.html) |
+| `@modelcontextprotocol/ext-apps/app-bridge` | Embed and communicate with Views in your chat client      | [API Docs →](https://modelcontextprotocol.github.io/ext-apps/api/modules/app-bridge.html)                           |
+| `@modelcontextprotocol/ext-apps/server`     | Register tools and resources on your MCP server           | [API Docs →](https://modelcontextprotocol.github.io/ext-apps/api/modules/server.html)                               |

 There's no _supported_ host implementation in this repo (beyond the
 [examples/basic-host](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/basic-host)
@ -272,8 +243,8 @@ point your client at a local build:

 ## Resources

- [Quickstart Guide](https://apps.extensions.modelcontextprotocol.io/api/documents/quickstart.html)
- [API Documentation](https://apps.extensions.modelcontextprotocol.io/api/)
+- [Quickstart Guide](https://modelcontextprotocol.github.io/ext-apps/api/documents/Quickstart.html)
+- [API Documentation](https://modelcontextprotocol.github.io/ext-apps/api/)
 - [Specification (2026-01-26)](https://github.com/modelcontextprotocol/ext-apps/blob/main/specification/2026-01-26/apps.mdx)
  ([Draft](https://github.com/modelcontextprotocol/ext-apps/blob/main/specification/draft/apps.mdx))
 - [SEP-1865 Discussion](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1865)
--- a/SECURITY.md
+++ b/SECURITY.md
@ -1,21 +0,0 @@
-# Security Policy
-
-Thank you for helping keep the Model Context Protocol and its ecosystem secure.
-
-## Reporting Security Issues
-
-If you discover a security vulnerability in this repository, please report it through
-the [GitHub Security Advisory process](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability)
-for this repository.
-
-Please **do not** report security vulnerabilities through public GitHub issues, discussions,
-or pull requests.
-
-## What to Include
-
-To help us triage and respond quickly, please include:
-
- A description of the vulnerability
- Steps to reproduce the issue
- The potential impact
- Any suggested fixes (optional)
--- a/build.bun.ts
+++ b/build.bun.ts
@ -1,18 +1,9 @@
 #!/usr/bin/env bun
 import { $ } from "bun";
-import { cpSync, mkdirSync, rmSync } from "node:fs";
-
-// Avoid publishing artifacts left behind by an earlier build or branch.
-rmSync("dist", { recursive: true, force: true });

 // Run TypeScript compiler for type declarations
 await $`tsc`;

-// Copy schema.json (tsc is emitDeclarationOnly, Bun.build doesn't emit JSON assets).
-// Needed for the "./schema.json" package export.
-mkdirSync("dist/src/generated", { recursive: true });
-cpSync("src/generated/schema.json", "dist/src/generated/schema.json");
-
 const isDevelopment = Bun.env.NODE_ENV === "development";

 // Build all JavaScript/TypeScript files
@ -34,20 +25,10 @@ function buildJs(
  });
 }

-// Peer dependencies stay external in the standard entry points so consumers
-// share one base MCP SDK and Zod instance. The *-with-deps entry points keep
-// bundling these dependencies for standalone browser use.
-const PEER_EXTERNALS = [
-  "@modelcontextprotocol/client",
-  "@modelcontextprotocol/core",
-  "@modelcontextprotocol/server",
-  "zod",
-];
-
 await Promise.all([
  buildJs("src/app.ts", {
    outdir: "dist/src",
-    external: PEER_EXTERNALS,
+    external: ["@modelcontextprotocol/sdk"],
  }),
  buildJs("src/app.ts", {
    outdir: "dist/src",
@ -55,19 +36,19 @@ await Promise.all([
  }),
  buildJs("src/app-bridge.ts", {
    outdir: "dist/src",
-    external: PEER_EXTERNALS,
+    external: ["@modelcontextprotocol/sdk"],
  }),
  buildJs("src/react/index.tsx", {
    outdir: "dist/src/react",
-    external: ["react", "react-dom", ...PEER_EXTERNALS],
+    external: ["react", "react-dom", "@modelcontextprotocol/sdk"],
  }),
  buildJs("src/react/index.tsx", {
    outdir: "dist/src/react",
-    external: ["react", "react-dom"],
+    external: ["react", "react-dom", "@modelcontextprotocol/sdk"],
    naming: { entry: "react-with-deps.js" },
  }),
  buildJs("src/server/index.ts", {
    outdir: "dist/src/server",
-    external: PEER_EXTERNALS,
+    external: ["@modelcontextprotocol/sdk"],
  }),
 ]);
--- a/docs/agent-skills.md
+++ b/docs/agent-skills.md
@ -1,7 +1,5 @@
 ---
 title: Agent Skills
-group: Getting Started
-description: Use Agent Skills to build, migrate, and extend MCP Apps with AI coding agents. Install skills that scaffold new apps, convert OpenAI Apps, and add UI to existing servers.
 ---

 # Agent Skills
--- a/docs/authorization.md
+++ b/docs/authorization.md
@ -1,211 +0,0 @@
---
-title: Authorization
-group: Security
-description: Learn how to protect MCP App tools with OAuth authorization, including per-server and per-tool auth patterns, token verification, and UI-initiated auth escalation.
---
-
-# Authorization
-
-MCP Apps can protect tools behind OAuth-based authorization, as defined in the [MCP specification](https://modelcontextprotocol.io/specification/latest/basic/authorization). There are two approaches:
-
- **Per-server authorization** — The entire MCP server requires authorization at connection time. Every request must include a valid token, regardless of which tool is being called. This is the simpler model when all tools are sensitive.
- **Per-tool authorization** — Only specific tools require authorization. Public tools work without a token, and the OAuth flow is triggered only when the user calls a protected tool. This lets you mix public and protected tools in the same server.
-
-## Shared setup
-
-Regardless of which approach you choose, you need OAuth discovery metadata and token verification. These are the same for both.
-
-### OAuth discovery metadata
-
-The MCP specification requires servers to implement [authorization server discovery](https://modelcontextprotocol.io/specification/latest/basic/authorization#authorization-server-discovery) so clients know how to obtain authorization. Two well-known endpoints are needed:
-
-**[Protected Resource Metadata](https://datatracker.ietf.org/doc/html/rfc9728)** (`/.well-known/oauth-protected-resource`) — describes the resource server and identifies which authorization server(s) can issue tokens for it. The MCP SDK's `mcpAuthRouter` handles this automatically.
-
-**Authorization Server Metadata** (`/.well-known/oauth-authorization-server`) — advertises the authorization and token endpoints, supported scopes, and whether [Client ID Metadata Documents](https://modelcontextprotocol.io/specification/latest/basic/authorization#client-id-metadata-documents) (CIMD) is supported:
-
-```ts
-app.get("/.well-known/oauth-authorization-server", (_req, res) => {
-  res.json({
-    ...oauthMetadata,
-    client_id_metadata_document_supported: true,
-  });
-});
-```
-
-Setting `client_id_metadata_document_supported: true` tells MCP clients to use CIMD instead of [Dynamic Client Registration](https://modelcontextprotocol.io/specification/latest/basic/authorization#dynamic-client-registration) (DCR). With CIMD, the `client_id` is a URL that serves the client's metadata document, removing the need for a registration endpoint. See [Client Registration Approaches](https://modelcontextprotocol.io/specification/latest/basic/authorization#client-registration-approaches) in the spec for the full list of options and priority order.
-
-### Token verification
-
-Verify access tokens as JWTs against the identity provider's JWKS endpoint. The `jose` library handles key fetching and caching:
-
-```ts
-import { createRemoteJWKSet, jwtVerify } from "jose";
-
-const JWKS = createRemoteJWKSet(new URL(`${IDP_DOMAIN}/.well-known/jwks.json`));
-
-const { payload } = await jwtVerify(token, JWKS, {
-  issuer: IDP_DOMAIN,
-});
-```
-
-MCP servers must validate that tokens were issued specifically for them — see [Token Handling](https://modelcontextprotocol.io/specification/latest/basic/authorization#token-handling) and [Access Token Privilege Restriction](https://modelcontextprotocol.io/specification/latest/basic/authorization#access-token-privilege-restriction) in the spec for the full requirements.
-
-## Per-server authorization
-
-With per-server authorization, every request to the `/mcp` endpoint must include a valid Bearer token. Any unauthorized request receives HTTP `401`, and the host must complete the OAuth flow before the client can use any tools. This is the right choice when all tools are sensitive and there's no value in allowing unauthorized access.
-
-The TypeScript MCP SDK supports this out of the box via `mcpAuthRouter` and `ProxyOAuthServerProvider` — no custom HTTP handler logic is needed. See the [MCP SDK documentation](https://github.com/modelcontextprotocol/typescript-sdk) for setup details.
-
-## Per-tool authorization
-
-With per-tool authorization, the `/mcp` endpoint handler inspects the raw JSON-RPC request body, checks whether any message targets a protected tool, and only enforces authorization for those calls. Public tools pass through without a token.
-
-### How it works
-
-1. The server maintains a set of tool names that require authorization
-2. When a JSON-RPC request arrives at the `/mcp` endpoint, the server inspects the request body to determine if any message is a `tools/call` targeting a protected tool
-3. If a protected tool is being called and no valid Bearer token is present, the server returns HTTP `401` with a [`WWW-Authenticate` header](https://modelcontextprotocol.io/specification/latest/basic/authorization#protected-resource-metadata-discovery-requirements) pointing to its [Protected Resource Metadata](https://datatracker.ietf.org/doc/html/rfc9728)
-4. The MCP host (e.g., Claude Desktop) sees the `401`, discovers the authorization server via the metadata URL, runs the [OAuth flow](https://modelcontextprotocol.io/specification/latest/basic/authorization#authorization-flow-steps) with the user, and retries the request with the acquired token
-5. On retry, the server verifies the token, extracts the user identity, and creates a per-request MCP server instance with that auth context
-6. Unprotected tools pass through without any token check — they work for everyone
-
-This design means authorization is enforced at the HTTP boundary (as [required by the spec](https://modelcontextprotocol.io/specification/latest/basic/authorization#access-token-usage)), not as a tool-level error. The MCP server itself never sees unauthorized requests for protected tools.
-
-### Enforcing HTTP 401
-
-The [MCP auth specification](https://modelcontextprotocol.io/specification/latest/basic/authorization#access-token-usage) requires protected resources to return HTTP `401` responses — not tool-level errors.
-
-Start by defining which tools require authorization. Then, in the `/mcp` endpoint handler, inspect the raw JSON-RPC request body, check whether any message targets a protected tool, and either verify the Bearer token or return `401` before the request ever reaches the MCP server:
-
-```ts
-/** Tools that require a valid Bearer token — checked at the HTTP level for proper 401. */
-const PROTECTED_TOOLS = new Set(["get_account_balance", "manage_branch_admin"]);
-
-app.all("/mcp", async (req, res) => {
-  // Parse the JSON-RPC body — it may be a single message or a batch
-  const messages = Array.isArray(req.body) ? req.body : [req.body];
-
-  // Check if any message is a tools/call for a protected tool
-  const needsAuth = messages.some(
-    (msg: any) =>
-      msg?.method === "tools/call" && PROTECTED_TOOLS.has(msg.params?.name),
-  );
-
-  // Extract and verify the Bearer token
-  let authInfo: AuthInfo | undefined;
-  const authHeader = req.headers.authorization;
-
-  if (authHeader?.startsWith("Bearer ")) {
-    try {
-      const token = authHeader.slice(7);
-      const { payload } = await jwtVerify(token, JWKS, {
-        issuer: IDP_DOMAIN,
-      });
-      authInfo = { token, sub: payload.sub as string };
-    } catch {
-      if (needsAuth) {
-        return res
-          .status(401)
-          .set(
-            "WWW-Authenticate",
-            `Bearer resource_metadata="${resourceMetadataUrl}"`,
-          )
-          .json({
-            error: "invalid_token",
-            error_description: "The access token is invalid",
-          });
-      }
-    }
-  } else if (needsAuth) {
-    return res
-      .status(401)
-      .set(
-        "WWW-Authenticate",
-        `Bearer resource_metadata="${resourceMetadataUrl}"`,
-      )
-      .json({
-        error: "invalid_token",
-        error_description: "Authorization required",
-      });
-  }
-
-  // Create a per-request MCP server with the auth context.
-  // authInfo is undefined for public tool calls, populated for
-  // authenticated requests — tool handlers use it to scope data
-  // to the authenticated user.
-  const server = createServer(authInfo);
-  // ... handle the request with transport
-});
-```
-
-The `WWW-Authenticate` header includes the [Protected Resource Metadata](https://modelcontextprotocol.io/specification/latest/basic/authorization#authorization-server-location) URL, which tells the client where to discover the authorization server.
-
-### Defence-in-depth in tool handlers
-
-Even though the HTTP layer enforces authorization, protected tool handlers should also verify `authInfo` as a defence-in-depth measure. If the HTTP layer is misconfigured or bypassed, the tool handler catches unauthorized access:
-
-```ts
-registerAppTool(
-  server,
-  "get_account_balance",
-  {
-    description: "Get account balance",
-    inputSchema: z.object({ accountId: z.string() }),
-  },
-  async ({ accountId }) => {
-    if (!authInfo) {
-      return {
-        isError: true,
-        content: [
-          {
-            type: "text",
-            text: "Authorization required to access account data.",
-          },
-        ],
-      };
-    }
-
-    const balance = await getBalance(authInfo.sub, accountId);
-    return {
-      content: [{ type: "text", text: `Balance: ${balance}` }],
-    };
-  },
-);
-```
-
-### UI-initiated auth escalation
-
-A powerful pattern is mixing public and protected tools in the same app. The app loads with public data (no authorization required), and the OAuth flow is triggered only when the user performs a protected action. This is a practical application of the [step-up authorization flow](https://modelcontextprotocol.io/specification/latest/basic/authorization#step-up-authorization-flow) described in the spec:
-
-1. A public tool (e.g., `manage_branch`) loads the UI without requiring authorization
-2. The user clicks a button that calls a protected tool via `app.callServerTool()`
-3. The MCP host receives HTTP `401` and automatically runs the OAuth flow
-4. After the user completes the OAuth flow, the host retries the tool call with the acquired token
-5. The protected data appears in the UI
-
-```tsx
-function BranchItem({ branch }: { branch: Branch }) {
-  const [adminData, setAdminData] = useState(null);
-
-  async function handleManage() {
-    // This call may trigger the OAuth flow if the user
-    // hasn't been authorized yet — the host handles it
-    // transparently.
-    const result = await app.callServerTool({
-      name: "manage_branch_admin",
-      arguments: { branch_id: branch.id },
-    });
-    setAdminData(result.structuredContent);
-  }
-
-  return (
-    <div>
-      <span>{branch.name}</span>
-      <button onClick={handleManage}>Manage</button>
-      {adminData && <AdminPanel data={adminData} />}
-    </div>
-  );
-}
-```
-
-This pattern keeps the initial experience fast (no login wall) while securing sensitive operations behind authorization. The host manages the entire OAuth flow — the app code simply calls the tool and handles the result.
--- a/docs/csp-cors.md
+++ b/docs/csp-cors.md
@ -1,64 +0,0 @@
---
-title: CSP and CORS
-group: Security
-description: Configure Content Security Policy and CORS for MCP Apps that make network requests from sandboxed iframes, including connectDomains, resourceDomains, and stable origin setup.
---
-
-# CSP & CORS
-
-Unlike regular web apps, MCP Apps HTML is served as an MCP resource and runs in a sandboxed iframe with no same-origin server. Any app that makes network requests must configure Content Security Policy (CSP) and possibly CORS.
-
-**CSP** controls what the _browser_ allows. You must declare _all_ origins in {@link types!McpUiResourceMeta.csp `_meta.ui.csp`} ({@link types!McpUiResourceCsp `McpUiResourceCsp`}) — including `localhost` during development. Declare `connectDomains` for fetch/XHR/WebSocket requests and `resourceDomains` for scripts, stylesheets, images, and fonts.
-
-**CORS** controls what the _API server_ allows. Public APIs that respond with `Access-Control-Allow-Origin: *` or use API key authentication work without CORS configuration. For APIs that allowlist specific origins, use {@link types!McpUiResourceMeta.domain `_meta.ui.domain`} to give the app a stable origin that the API server can allowlist. The format is host-specific, so check each host's documentation for its supported format.
-
-<!-- prettier-ignore -->
-```ts source="../src/server/index.examples.ts#registerAppResource_withDomain"
-// Computes a stable origin from an MCP server URL for hosting in Claude.
-function computeAppDomainForClaude(mcpServerUrl: string): string {
-  const hash = crypto
-    .createHash("sha256")
-    .update(mcpServerUrl)
-    .digest("hex")
-    .slice(0, 32);
-  return `${hash}.claudemcpcontent.com`;
-}
-
-const APP_DOMAIN = computeAppDomainForClaude("https://example.com/mcp");
-
-registerAppResource(
-  server,
-  "Company Dashboard",
-  "ui://dashboard/view.html",
-  {
-    description: "Internal dashboard with company data",
-  },
-  async () => ({
-    contents: [
-      {
-        uri: "ui://dashboard/view.html",
-        mimeType: RESOURCE_MIME_TYPE,
-        text: dashboardHtml,
-        _meta: {
-          ui: {
-            // CSP: tell browser the app is allowed to make requests
-            csp: {
-              connectDomains: ["https://api.example.com"],
-            },
-            // CORS: give app a stable origin for the API server to allowlist
-            //
-            // (Public APIs that use `Access-Control-Allow-Origin: *` or API
-            // key auth don't need this.)
-            domain: APP_DOMAIN,
-          },
-        },
-      },
-    ],
-  }),
-);
-```
-
-Note that `_meta.ui.csp` and `_meta.ui.domain` are set in the `contents[]` objects returned by the resource read callback, not in `registerAppResource()`'s config object.
-
-> [!NOTE]
-> For full examples that configures CSP, see: [`examples/sheet-music-server/`](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/sheet-music-server) (`connectDomains`) and [`examples/map-server/`](https://github.com/modelcontextprotocol/ext-apps/tree/main/examples/map-server) (`connectDomains` and `resourceDomains`).
--- a/docs/favicons/apple-touch-icon.png
+++ b/docs/favicons/apple-touch-icon.png
--- a/docs/favicons/favicon-16x16.png
+++ b/docs/favicons/favicon-16x16.png
--- a/Show more
+++ b/Show more