mcp-apps-builder

# 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 exists. ## Native v2 invariants - Import server APIs from `mcp-use`; provider adapters come from `mcp-use/oauth/*`; React APIs come from `mcp-use/react`. - Define tools with `inputSchema`; add `outputSchema` when returning structured data or binding a View. - Return MCP result envelo...