Agent skill · Frontend

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.

a5c-aigithub.com/a5c-aiGitHub ↗
claude-codecodexcan modify filesMIT
Install
npx skills add a5c-ai/babysitter --skill mcp-app-scaffolding --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Allowed tools: ReadWriteEditBashGlobGrep
Path: library/specializations/ai-agents-conversational/skills/mcp-app-scaffolding/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,642
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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.resourceUri` references 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 `useApp` hook, `useHostStyles`, `useHo

What's inside
Steps it walks through
  1. Overview
  2. Capabilities
  3. Reference Code Acquisition
  4. Framework Selection Decision Tree
  5. Project Structure Generation
  6. Dependency Installation
  7. Usage
  8. Step 1: Clone Reference Code
  9. Step 2: Framework Decision Tree
  10. Step 3: Initialize Project
  11. Step 4: Project Directory Layout
  12. Step 5: Package.json Scripts
  13. Step 6: TypeScript Configuration
  14. Verification Checklist
Ships with 1 file
  • README.md
Commands it runs
Clone SDK at the exact version published to npm
git clone --branch "v$(npm view @modelcontextprotocol/ext-apps version)" \
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
More from babysitter
All skills →
About this skill
What does the mcp-app-scaffolding skill do?

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.

How do I install it?

Run `npx skills add a5c-ai/babysitter --skill mcp-app-scaffolding --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going