| Filename | Latest commit message | Latest commit date |
|---|---|---|
ae9b96e1fd* fix(examples): use npm reference for ext-apps dependency Replace local path '../..' with '^1.0.0' npm reference in all example packages. The local path was accidentally published to npm, causing npm install to hang when installing server-* packages. Bump versions to 1.0.1 for all public packages to fix the published versions. Fixes npm install hanging issue in dependent projects like example-remote-server. Note: npm workspaces automatically resolves the dependency to the local package during development, so no overrides are needed. * fix: update zod to 4.x in transcript-server and fix update-lock:docker script - Update transcript-server to use zod ^4.1.13 for compatibility - Fix update-lock:docker script to properly clean workspace node_modules - Regenerate package-lock.json with clean npmjs.org URLs |
||
| .. | ||
| src | ||
| .gitignore | ||
| main.ts | ||
| mcp-app.html | ||
| package.json | ||
| README.md | ||
| server.ts | ||
| tsconfig.json | ||
| tsconfig.server.json | ||
| vite.config.ts | ||
Example: Integration Test Server
An MCP App example used for E2E integration testing.
Overview
This example demonstrates all App SDK communication APIs and is used by the E2E test suite to verify host-app interactions:
- Tool registration with a linked UI resource
- React UI using the
useApp()hook - App communication APIs:
callServerTool,sendMessage,sendLog,openLink
Key Files
server.ts- MCP server with tool and resource registrationmcp-app.html/src/mcp-app.tsx- React UI usinguseApp()hook
Getting Started
npm install
npm run dev
How It Works
- The server registers a
get-timetool with metadata linking it to a UI HTML resource (ui://get-time/mcp-app.html). - When the tool is invoked, the Host renders the UI from the resource.
- The UI uses the MCP App SDK API to communicate with the host and call server tools.