mcpdemos
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcpdemos run the polite CLI demo"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Demos
8 runnable demos showcasing Model Context Protocol capabilities - from text-only tools to interactive MCP Apps with bidirectional communication.
Quick Start
node --version # Requires Node 20+
npm install
npm run dev # Start MCP server (stdio transport)For production:
npm run build
npm startRelated MCP server: mcp-demo
VS Code Configuration
Add to .vscode/settings.json to auto-discover the server:
{
"mcp": {
"servers": {
"mcpdemos": {
"command": "node",
"args": ["dist/index.js"],
"cwd": "${workspaceFolder}"
}
}
}
}For development with tsx:
{
"mcp": {
"servers": {
"mcpdemos": {
"command": "npx",
"args": ["tsx", "src/index.ts"],
"cwd": "${workspaceFolder}"
}
}
}
}Demos
# | Demo | Category | Tools | Resources |
1 | Hook |
| - | |
2 | Negotiation |
| - | |
3 | Security |
| - | |
4 | Coordination |
| - | |
5 | Coordination |
| - | |
6 | Shared Artifacts |
|
| |
7 | Shared Artifacts |
|
| |
8 | Platform |
| - |
Runbooks
ShowRun All Demos - All Demos Walkthrough Script
5-Minute Runbook - Quick highlights (Demos 1, 2, 3, 4, 6, 8)
15-Minute Runbook - Full walkthrough with stage timing for all 8 demos
Architecture
src/
index.ts ← Server entry point (stdio transport)
demos/
demo1-polite-cli.ts ← Tool: verbose CLI responses
demo2-elicitation.ts ← Tools: scaffold start + confirm
demo3-oauth.ts ← Tools: consent → approve → action
demo4-async-progress.ts ← Tools: pipeline + progress polling
demo5-cancel-retry.ts ← Tools: cancel, retry, list tasks
demo6-color-picker.ts ← Tool + Resource: colour picker UI
demo7-component-gallery.ts ← Tool + Resource: gallery UI
demo8-export-artifacts.ts ← Tool: report generation
examples/
demo{1-8}/README.md ← Per-demo docs with stage scripts
docs/
5-minute-runbook.md
15-minute-runbook.md
outputs/ ← Generated reports (Demo 8)Graceful Degradation
If a host doesn't support MCP Apps (ui:// resources), all demos fall back to text-only tool interactions. The UI resources are optional enhancements.
Dependencies
@modelcontextprotocol/sdk- MCP server frameworkzod- Schema validationtsx(dev) - TypeScript executionNo external APIs, databases, or cloud services required
Licence
MIT
Available Tools
16 toolsdemo1_polite_cliC
Verbose CLI-style helper – returns long text/JSON requiring multiple round-trips. Demonstrates the 'before' experience of chatting with a polite but wordy tool.
Inputs: command (required), verbose.
demo2_scaffold_confirmB
Complete project scaffolding after user has made their choices. Resumes the flow started by demo2_scaffold_start.
Inputs: projectName (required), template (required), includeDocker, includeCI, +1 more.
demo2_scaffold_startC
Begin project scaffolding – presents configuration choices via structured elicitation. Returns a structured prompt for the user to choose template, name, and options.
Inputs: projectName (required).
demo3_approve_consentA
Approve a pending consent request and receive a scoped mock token. The token is ephemeral and never leaves the server process.
Inputs: consentId (required).
demo3_protected_actionA
Execute a protected action using the mock token from demo3_approve_consent. Validates the token is present, unexpired, and properly scoped.
Inputs: token (required), action (required).
demo3_request_consentA
Initiate a secure OAuth-style handoff. Returns a mock authorization prompt that the user must approve before the protected action can proceed. No real secrets are involved – this is a simulation.
Inputs: action (required), userId.
demo4_check_progressA
Check progress of a running pipeline task. Returns current step, percentage, and log entries.
Inputs: taskId (required).
demo4_start_pipelineA
Start a long-running build pipeline with 12 steps. Returns progress updates as the task runs. Use demo4_check_progress to poll status.
Inputs: project, stepDelayMs, failAtStep.
demo5_cancel_taskB
Cancel a running pipeline task. The task will stop at its current step.
Inputs: taskId (required), reason.
demo5_list_tasksC
List all tasks (running, completed, failed, cancelled) for visibility.
Inputs: no named parameters.
demo5_retry_taskA
Retry a failed or cancelled task. Can resume from where it stopped or restart entirely with modified parameters.
Inputs: taskId (required), mode, fixFailingStep, stepDelayMs.
demo6_get_paletteA
Get all saved colors from the palette.
Inputs: no named parameters.
demo6_save_colorC
Save a color to the server palette. Can be called by the Color Picker UI or directly by an agent.
Inputs: color (required), name (required).
demo7_gallery_stateA
Get or set the component gallery state. When setting, the server updates its state which the UI can read on next render.
Inputs: action (required), component, variant, theme.
demo8_export_reportA
Generate a markdown report of all demos and write it to /outputs. Includes sharing guidance, VS Code config, and dev mode checklist.
Inputs: title, includeDevMode, format.
demo8_list_exportsA
List all exported reports in the /outputs directory.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 16 tools
Each tool targets a distinct demo scenario and action, with no overlapping purposes. The demoX prefix clearly groups related tools, and individual tool descriptions specify unique roles (e.g., start vs. confirm vs. check progress).
All tools follow a consistent snake_case verb_noun pattern (e.g., demo1_polite_cli, demo2_scaffold_start, demo3_request_consent). The naming is uniform across all 16 tools with no deviations.
With 16 tools, the count is slightly above the ideal 3-15 range, but given the multi-demo scope, it remains well-scoped. Each tool serves a distinct purpose, and none feel redundant.
The tool surface covers the core workflows for each demo scenario (e.g., scaffolding, consent flow, pipeline management, palette operations). Minor gaps exist (e.g., no tool to reset a demo), but overall it supports the intended demonstrations adequately.
Maintenance
Related MCP Connectors
Capability-routed CLI/MCP: signed provenance exports, WCAG-validated themes, sovereign deploy modes.
One OAuth connector for your team's remote MCP servers, with Tool Packs, guardrails and logs.
327 dev tools via REST API and MCP. Generate Dockerfiles, schemas, K8s, APIs, and more.
Discover, plan and run tools across your connected business systems through one OAuth MCP endpoint
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceProvides runnable samples demonstrating how MCP tools can return deterministic, interactive UIs using HTML, UI5 Web Components, UI Integration Cards, and host-orchestrated SAP transport data.10-
- AlicenseNot gradedqualityDmaintenanceA demo MCP server showcasing every MCP capability with fake logic, including tools, resources, prompts, progress, cancellation, elicitation, sampling, roots, and subscriptions, over Streamable HTTP, HTTP+SSE, and stdio transports.19 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI clients to connect to example tools, resources, and prompts over MCP, demonstrating integration with IDEs, chatbots, and agent frameworks.-
- FlicenseNot gradedqualityAmaintenanceEnables developers to build, run locally with debugging, and deploy to the cloud custom remote MCP endpoints hosted on Azure Functions, with built-in Microsoft Entra authentication. Sample projects demonstrate snippet CRUD and QR code tools, resource templates, prompt workflows, and an interactive weather demo UI.-