mcp-app-scaffolding
Scaffolds MCP App project structure with correct directory layout, dependencies, entry points, and framework-specific templates. Handles React (useApp hook), Vanilla JS, Vue, Svelte, Preact, and Solid.
Install / Use
npx skills add a5c-ai/babysitter --skill mcp-app-scaffoldingInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of mcp-app-scaffolding
mcp-app-scaffolding scores 92/100 on our quality scale, 882nd of 2,780 Automation skills we index (top 32%).
Its SKILL.md is 8.7 KB long, well organised into 25 sections with 7 code examples: a thorough specification that gives an agent plenty to work with.
With 1,809 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so mcp-app-scaffolding is actively maintained.
- Our last check on 2026-10-27 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
mcp-app-scaffolding compared with similar skills
All 4 of these similar skills score higher than mcp-app-scaffolding; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| mcp-app-scaffolding (this skill)by a5c-ai | 92 | 1.8k | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install mcp-app-scaffolding?
- Run
npx skills add a5c-ai/babysitter --skill mcp-app-scaffolding. The install tabs above show the steps for each supported agent. - Which AI agents does mcp-app-scaffolding work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is mcp-app-scaffolding safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is mcp-app-scaffolding still maintained?
- The repository was last updated about 2 months ago, so mcp-app-scaffolding is actively maintained.
Skill content
View source on GitHubname: mcp-app-scaffolding description: Scaffolds MCP App project structure with correct directory layout, dependencies, entry points, and framework-specific templates. Handles React (useApp hook), Vanilla JS, Vue, Svelte, Preact, and Solid. allowed-tools: Read, Write, Edit, Bash, Glob, Grep graph: domains: [domain:software-engineering] specializations: [specialization:ai-agents-conversational] skillAreas: [skill-area:mcp-server-implementation, skill-area:mcp-tool-design] roles: [role:backend-engineer, role:fullstack-engineer] workflows: [workflow:feature-development] topics: [topic:api-design, topic:design-patterns]
mcp-app-scaffolding
Scaffold MCP App projects from scratch with correct structure, dependencies, and framework-specific templates following the reference-code-first methodology.
Overview
MCP Apps are interactive UIs that render inline in MCP-enabled hosts (Claude Desktop, ChatGPT, VS Code, Goose, Postman). Every MCP App requires:
- A Tool (called by the LLM/host, returns data) registered via
registerAppTool - A Resource (serves bundled HTML UI) registered via
registerAppResource - The tool's
_meta.ui.resourceUrireferences the resource's URI
This skill handles the initial project scaffolding: cloning the SDK reference code, selecting a framework, generating the directory structure, and creating all entry points.
Capabilities
Reference Code Acquisition
- Clone SDK repository at exact published npm version
- Access framework templates from
examples/basic-server-{framework}/ - Access API reference source from
src/ - Access advanced patterns from
docs/patterns.md - Access basic-host reference for testing from
examples/basic-host/
Framework Selection Decision Tree
- React (first-class support): SDK-provided
useApphook,useHostStyles,useHostStyleVariables,useHostFonts - Vanilla JS: Manual App lifecycle, simplest setup, no framework overhead
- Vue / Svelte / Preact / Solid: Manual lifecycle management, follow team preference
Project Structure Generation
- Directory layout with
src/, build configs, entry points - Separate server and client source directories
- Proper
.gitignorefor build artifacts
Dependency Installation
- Runtime:
@modelcontextprotocol/ext-apps,@modelcontextprotocol/sdk,zod - Dev:
typescript,vite,vite-plugin-singlefile,tsx,concurrently - Framework-specific:
react,react-dom,@types/react,@types/react-dom(for React) - Always use
npm install-- never hardcode version numbers
Usage
Step 1: Clone Reference Code
# Clone SDK at the exact version published to npm
git clone --branch "v$(npm view @modelcontextprotocol/ext-apps version)" \
--depth 1 https://github.com/modelcontextprotocol/ext-apps.git /tmp/mcp-ext-apps
Key reference locations:
| Path | Content |
|------|---------|
| /tmp/mcp-ext-apps/examples/basic-server-react/ | React template |
| /tmp/mcp-ext-apps/examples/basic-server-vanillajs/ | Vanilla JS template |
| /tmp/mcp-ext-apps/examples/basic-server-vue/ | Vue template |
| /tmp/mcp-ext-apps/examples/basic-server-svelte/ | Svelte template |
| /tmp/mcp-ext-apps/examples/basic-server-preact/ | Preact template |
| /tmp/mcp-ext-apps/examples/basic-server-solid/ | Solid template |
| /tmp/mcp-ext-apps/src/app.ts | App class API |
| /tmp/mcp-ext-apps/src/server/index.ts | Server registration helpers |
| /tmp/mcp-ext-apps/src/react/useApp.tsx | React useApp hook |
| /tmp/mcp-ext-apps/src/styles.ts | Host styling helpers |
| /tmp/mcp-ext-apps/docs/patterns.md | Advanced patterns |
| /tmp/mcp-ext-apps/examples/basic-host/ | Test host |
Step 2: Framework Decision Tree
Is the team familiar with React?
YES -> Use React with useApp hook (SDK-provided, first-class)
NO -> Is this a simple app with minimal UI?
YES -> Use Vanilla JS with manual lifecycle
NO -> Use team's preferred framework (Vue/Svelte/Preact/Solid)
with manual App lifecycle management
Step 3: Initialize Project
mkdir my-mcp-app && cd my-mcp-app
npm init -y
# Core dependencies
npm install @modelcontextprotocol/ext-apps @modelcontextprotocol/sdk zod
# Dev dependencies
npm install -D typescript vite vite-plugin-singlefile tsx concurrently @types/node
# React-specific (if using React)
npm install react react-dom
npm install -D @types/react @types/react-dom
Step 4: Project Directory Layout
my-mcp-app/
├── src/
│ ├── server.ts # MCP server with registerAppTool + registerAppResource
│ ├── main.ts # Client UI entry (or main.tsx for React)
│ └── global.css # Styles with host CSS variable fallbacks
├── mcp-app.html # HTML entry point for Vite (or mcp-app.tsx for React)
├── vite.config.ts # Vite + vite-plugin-singlefile
├── tsconfig.json # TypeScript configuration
├── package.json # Scripts: build:ui, build:server, build, dev
└── .gitignore # dist/, node_modules/, /tmp/
Step 5: Package.json Scripts
{
"scripts": {
"build:ui": "vite build",
"build:server": "tsc --project tsconfig.server.json",
"build": "npm run build:ui && npm run build:server",
"dev": "concurrently \"vite\" \"tsx watch src/server.ts\"",
"serve": "tsx src/server.ts"
}
}
Step 6: TypeScript Configuration
{
"compilerOptions": {
"target": "ES2022",
"module": "ESNext",
"moduleResolution": "bundler",
"strict": true,
"esModuleInterop": true,
"jsx": "react-jsx",
"outDir": "dist",
"rootDir": "src"
},
"include": ["src/**/*.ts", "src/**/*.tsx"],
"exclude": ["node_modules", "dist"]
}
Verification Checklist
- [ ] SDK reference code cloned at pinned version
- [ ] Framework selected based on team context
- [ ] All dependencies installed via
npm install(no manual versions) - [ ] Server entry point created (
server.ts) - [ ] Client entry point created (
main.ts/main.tsx) - [ ] HTML entry point created (
mcp-app.html/mcp-app.tsx) - [ ] Vite config with
vite-plugin-singlefilepresent - [ ] Build scripts defined (
build:ui,build:server,build) - [ ] TypeScript configured correctly
- [ ]
.gitignoreincludesdist/andnode_modules/
Task Definition
const mcpAppScaffoldingTask = defineTask({
name: 'mcp-app-scaffolding',
description: 'Scaffold MCP App project structure with framework-specific templates',
inputs: {
appName: { type: 'string', required: true },
framework: { type: 'string', default: 'react' },
description: { type: 'string', default: '' },
transport: { type: 'string', default: 'stdio' },
existingServer: { type: 'boolean', default: false }
},
outputs: {
projectDir: { type: 'string' },
framework: { type: 'string' },
files: { type: 'array' },
artifacts: { type: 'array' }
},
async run(inputs, taskCtx) {
return {
kind: 'skill',
title: `Scaffold MCP App: ${inputs.appName} (${inputs.framework})`,
skill: {
name: 'mcp-app-scaffolding',
context: {
appName: inputs.appName,
framework: inputs.framework,
description: inputs.description,
transport: inputs.transport,
existingServer: inputs.existingServer,
instructions: [
'Clone SDK reference code at published npm version',
'Execute framework selection decision tree',
'Generate project directory structure',
'Install all dependencies via npm install',
'Create server and client entry points',
'Configure Vite with vite-plugin-singlefile',
'Set up TypeScript and build scripts'
]
}
},
io: {
inputJsonPath: `tasks/${taskCtx.effectId}/input.json`,
outputJsonPath: `tasks/${taskCtx.effectId}/result.json`
}
};
}
});
Applicable Processes
- create-mcp-app.js
- add-app-to-mcp-server.js
External Dependencies
- Node.js 18+
- npm
- Git (for cloning SDK reference code)
- @modelcontextprotocol/ext-apps npm package
- @modelcontextprotocol/sdk npm package
References
- MCP Apps SDK Repository
- MCP Apps SDK npm
- MCP Apps Quickstart
- MCP Apps Overview
- MCP Specification (2026-01-26)
Related Skills
- mcp-tool-resource-pattern
- mcp-host-styling-integration
- single-file-bundling
- mcp-app-verification
Related Agents
- mcp-app-architect
- mcp-ui-developer
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
