Files
claude-plugins-official/plugins/mcp-server-dev
Bryan Thompson 7c86e21044 Add multi-view app architecture reference for build-mcp-app (#973)
Adds a reference doc covering production patterns for multi-view MCP apps
that go beyond single-purpose widgets. Patterns distilled from building
nashville-charts-app, generalized with placeholder examples.

Covers: single-resource action dispatch, model context updates, teardown
guards, bidirectional tool calls, Vite+esbuild build pipeline, dual
transport (HTTP+stdio), debugging tips, prompt orchestration.

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-10 22:51:38 +01:00
..

mcp-server-dev

Skills for designing and building MCP servers that work seamlessly with Claude.

What's inside

Three skills that compose into a full build path:

Skill Purpose
build-mcp-server Entry point. Interrogates the use case, picks deployment model (remote HTTP / MCPB / local stdio), picks tool-design pattern, routes to a specialized skill.
build-mcp-app Adds interactive UI widgets (forms, pickers, confirm dialogs) rendered inline in chat. Works on remote servers and MCPB bundles.
build-mcpb Packages a local stdio server with its runtime so users can install it without Node/Python. For servers that must touch the local machine.

How it works

build-mcp-server is the front door. It asks what you're connecting to, who'll use it, how big the action surface is, and whether you need in-chat UI. From those answers it recommends one of four paths:

  • Remote streamable-HTTP (the default recommendation for anything wrapping a cloud API) — scaffolded inline
  • MCP app — hands off to build-mcp-app
  • MCPB — hands off to build-mcpb
  • Local stdio prototype — scaffolded inline with an MCPB upgrade note

Each skill ships reference files for the parts that don't fit in the main instructions: auth flows (DCR/CIMD), tool-description writing, widget templates, manifest schemas, security hardening.

Usage

Ask Claude to "help me build an MCP server" and the entry skill will trigger. Or invoke directly:

/mcp-server-dev:build-mcp-server