modelcontextprotocol / modelcontextprotocol/ext-apps

Add official CLI scaffolding tool for MCP Apps

Open
#354 1 comment 0 reactions 1 assignee View on GitHub

@liady is already working on this.

Since Jan 25, 2026.

enhancement
Dominant language
TypeScript
Stars
2.9k
Forks
387
Avg merge
3h 21m
Merged PRs (30d)
6

Description

Problem

Currently, developers who want to create a new MCP App project need to manually:

  1. Copy files from an existing example
  2. Modify package.json with their project name
  3. Update dependencies
  4. Configure build scripts

This friction slows down adoption and increases the chance of misconfiguration.

Additionally, the package name create-mcp-app is already taken on npm by an unrelated package. Using @modelcontextprotocol/create-mcp-app clearly identifies this as the official scaffolding tool from the MCP team.

Proposal

Add an official @modelcontextprotocol/create-mcp-app package that enables one-command project scaffolding:

npm create @modelcontextprotocol/mcp-app my-app
Features
  • Interactive CLI - Prompts for project name and template selection
  • Multiple templates - Start with React or Vanilla JS
  • Zero configuration - Generated projects work out of the box
  • Official branding - Scoped under @modelcontextprotocol to indicate official support
Benefits
  • Lower barrier to entry - New developers can start building immediately
  • Consistent project structure - All generated projects follow best practices
  • Version-locked templates - Templates are bundled with the CLI, ensuring compatibility
  • Offline support - No network requests needed after installation

Usage

# Interactive mode
npm create @modelcontextprotocol/mcp-app

# With project name
npm create @modelcontextprotocol/mcp-app my-app

# With template selection
npm create @modelcontextprotocol/mcp-app my-app --template react

# Skip npm install
npm create @modelcontextprotocol/mcp-app my-app --no-install

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.