MCP Apps Builder

Editorial guide for building, modifying, debugging, migrating, and reviewing TypeScript MCP servers and interactive MCP Apps using mcp-use v2.

Migrate an existing mcp-use v1 server to v2 by reviewing package boundaries and updating server, provider, and React imports.
Build a new catalog MCP server with a tool that returns structured data and renders an interactive View.
Debug an existing MCP App by running the server, connecting a client, calling the tool, and rendering the View to verify the real lifecycle.
Review a project for release readiness by checking exports against installed declarations and running the verification checks.

TypeScript MCP server code
React View components
MCP result envelopes with content, structuredContent, and optionally _meta or isError
Scaffolding output from create-mcp-use-app

Do not assume APIs from mcp-use v1; check the installed version before changing code
Do not copy examples from v1 docs or historical changelogs
Do not invent exports or configuration fields; confirm them in installed declarations or source
Do not deploy or mutate external systems unless explicitly requested
Do not rely on module globals for cross-request identity or elicitation continuity
Confirm every statically declared tool ref that a View calls is exported
Verify each View is located at views/<name>/view.tsx and bound with view: { name: "<name>" } and has a matching outputSchema and structuredContent
Ensure server APIs are imported from mcp-use, provider adapters from mcp-use/oauth/*, and React APIs from mcp-use/react

AI Search

Find projects, verify facts, compare options, or turn a complex need into an actionable plan

Try a searchA click only fills the search box; you stay in control

Collection Scenario Project type License Deployment Resource form