ext-apps/examples/integration-server
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Olivier Chafik ca1d29894f
chore: bump ext-apps to 1.7.4 (#685)
* chore: bump ext-apps to 1.7.4

* fix: resolve all npm audit vulnerabilities

- Remove unused vitest devDependency from basic-host (critical advisory,
  package was never referenced by any test or config)
- systeminformation ^5.31.5 -> ^5.31.6 (command injection, GHSA-hvx9-hwr7-wjj9)
- Lockfile-only bumps: devalue 5.8.1, fast-uri 3.1.2, hono 4.12.23,
  ip-address 10.2.0, express-rate-limit 8.5.2, postcss 8.5.15, qs 6.15.2,
  svelte 5.56.1

npm audit now reports 0 vulnerabilities.
2026-06-04 22:10:06 +01:00
..
src refactor: use MCP resource types for ui/download-file params 2026-02-20 12:00:35 +00:00
.gitignore Improve consistency and organization of examples for AI learning 2026-01-13 20:48:02 -06:00
main.ts Refactor server startup functions 2026-01-24 09:27:54 -06:00
mcp-app.html Clean up examples (#182) 2025-12-19 11:44:27 +00:00
package.json chore: bump ext-apps to 1.7.4 (#685) 2026-06-04 22:10:06 +01:00
README.md Use apps.extensions.modelcontextprotocol.io domain for docs URLs 2026-02-24 11:38:54 -06:00
server.ts refactor: use MCP resource types for ui/download-file params 2026-02-20 12:00:35 +00:00
tsconfig.json Clean up examples (#182) 2025-12-19 11:44:27 +00:00
tsconfig.server.json feat: compile example servers to JavaScript for npm consumption (#259) 2026-01-14 23:46:17 +00:00
vite.config.ts Clean up examples (#182) 2025-12-19 11:44:27 +00:00

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:

Key Files

Getting Started

npm install
npm run dev

How It Works

  1. The server registers a get-time tool with metadata linking it to a UI HTML resource (ui://get-time/mcp-app.html).
  2. When the tool is invoked, the Host renders the UI from the resource.
  3. The UI uses the MCP App SDK API to communicate with the host and call server tools.