mcp-apps-builder
Build, modify, debug, migrate, or review TypeScript MCP servers and interactive MCP Apps using mcp-use v2. Use for tools, resources, prompts, Views, React host interactions, OAuth, middleware, Inspector workflows, package-boundary migrations, and release-ready verification in an mcp-use project.
Profile →npx skills add mcp-use/mcp-use --skill mcp-apps-builder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Build MCP Apps with mcp-use v2 Treat the installed `mcp-use` package, its generated types, and the project's existing exports as the source of truth. Check the installed version before changing code; do not assume APIs from mcp-use v1. ## Workflow 1. Inspect `package.json`, the server entry, exported tool refs, `views/`, and the installed `mcp-use` version. 2. Scaffold a new project with `npx create-mcp-use-app@latest`; do not hand-build framework boilerplate. 3. Read only the references needed for the task: - [Server primitives](references/server.md) for tools, resources, prompts, middleware, and result envelopes. - [Views](references/views.md) for interactive MCP Apps and React hooks. - [Authentication](references/auth.md) for OAuth providers and authenticated tool handlers. - [Migration](references/migration.md) when converting v1 code or reviewing package boundaries. - [Verification](references/verification.md) before reporting completion. 4. Implement against the package types. Export every statically declared tool ref that a View calls. 5. Validate through the real lifecycle: build/typecheck, run the server, connect a client, call the tool, and render the View when one exis
- Workflow
- Native v2 invariants
- Minimal server and View
- Guardrails
What does the mcp-apps-builder skill do?
Build, modify, debug, migrate, or review TypeScript MCP servers and interactive MCP Apps using mcp-use v2. Use for tools, resources, prompts, Views, React host interactions, OAuth, middleware, Inspector workflows, package-boundary migrations, and release-ready verification in an mcp-use project.
How do I install it?
Run `npx skills add mcp-use/mcp-use --skill mcp-apps-builder --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 mcp-use/mcp-use, a repository with 10,446 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.