Example: Basic Server (Svelte)

An MCP App example with a Svelte 5 UI using runes for reactivity.

> [!TIP]
> Looking for a vanilla JavaScript example? See basic-server-vanillajs!

MCP Client Configuration

Add to your MCP client configuration (stdio transport):

``json
{
"mcpServers": {
"basic-svelte": {
"command": "npx",
"args": [
"-y",
"--silent",
"--registry=https://registry.npmjs.org/",
"@modelcontextprotocol/server-basic-svelte",
"--stdio"
]
}
}
}
`

$3

To test local modifications, use this configuration (replace ~/code/ext-apps with your clone path):

`json
{
"mcpServers": {
"basic-svelte": {
"command": "bash",
"args": [
"-c",
"cd ~/code/ext-apps/examples/basic-server-svelte && npm run build >&2 && node dist/index.js --stdio"
]
}
}
}
`

Overview

- Tool registration with a linked UI resource
- Svelte 5 UI using the App class
- App communication APIs: callServerTool, sendMessage, sendLog, openLink

Key Files

- server.ts - MCP server with tool and resource registration
- mcp-app.html / src/App.svelte - Svelte 5 UI using App class

Getting Started

`bash
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.

Build System

This example bundles into a single HTML file using Vite with vite-plugin-singlefile — see vite.config.ts. This allows all UI content to be served as a single MCP resource. Alternatively, MCP apps can load external resources by defining _meta.ui.csp.resourceDomains` in the UI resource metadata.