AU

assistant-ui/mcp-app-studio-starter

Developer tools公式

このページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る

10 stars 6 forks 品質 48 トレンド 18

Starter template for MCP App Studio

概要

Starter template for building interactive apps for AI assistants with MCP App Studio. This template is automatically downloaded when you run npx mcp-app-studio. You don't need to clone this repo directly. - — as an MCP Apps host (standard ui/* bridge) - — as an MCP Apps host - — compatible with any MCP-supporting AI assistant Open http://localhost:3002 — you're in the workbench. This project also works with pnpm/yarn/bun (use the equivalent install + run commands). If you switch package managers (e.g. pnpm → npm), delete node_modules/ first to avoid confusing the installer. The MCP server (when server/ exists) runs at http://localhost:3001/mcp by default. If 3001 is already in use, it will select the next available port and write it to server/.mcp-port. The workbench simulates an MCP Apps host in an iframe. It also installs a window.openai shim so you can exercise during development (optional, non-standard).

README

以下は原文 README の抜粋です。原文を見る。

MCP App Studio Starter

Starter template for building interactive apps for AI assistants with MCP App Studio.

Note: This template is automatically downloaded when you run npx mcp-app-studio. You don’t need to clone this repo directly.

Supported Platforms

Build once, deploy anywhere:

  • ChatGPT — as an MCP Apps host (standard ui/* bridge)
  • Claude Desktop — as an MCP Apps host
  • Any MCP Apps host — compatible with any MCP-supporting AI assistant

Quick Start

# npm (default)
npm install
npm run dev

Open http://localhost:3002 — you’re in the workbench.

This project also works with pnpm/yarn/bun (use the equivalent install + run commands).

If you switch package managers (e.g. pnpm → npm), delete node_modules/ first to avoid confusing the installer.

The MCP server (when server/ exists) runs at http://localhost:3001/mcp by default. If 3001 is already in use, it will select the next available port and write it to server/.mcp-port.

The workbench simulates an MCP Apps host in an iframe. It also installs a window.openai shim so you can exercise ChatGPT-only extensions during development (optional, non-standard).

Agent Workflow

Use .agent/skills/mcp-app-development/SKILL.md as the default coding-agent workflow for this repo. It defines the 80/20 capability-slice loop:

  • Build UI and real MCP tool(s) in one chunk
  • Use TDD (red -> green) for parity checks
  • Never treat mock-only behavior as done

Commands

Command Description
npm run dev Start workbench (Next.js + MCP server)
npm run build Production build
npm run export Generate widget bundle for deployment

Project Structure

app/                        Next.js pages
components/
├── examples/               Example widgets (POI Map)
├── workbench/              Workbench UI components
└── ui/                     Shared UI components
lib/
├── sdk/                    SDK exports for production
├── workbench/              React hooks + dev environment
└── export/                 Production bundler
server/                     MCP server (if included)

Building Your Widget

1. Create a component

// components/my-widget/index.tsx
import {
  useToolInput,
  useCallTool,
  useTheme,
  useCapabilities,
  useUpdateModelContext,
  useWidgetState,
} from "@/lib/sdk";

export function MyWidget() {
  const input = useToolInput();
  const callTool = useCallTool();
  const theme = useTheme();
  const capabilities = useCapabilities();
  const updateModelContext = useUpdateModelContext();
  const [widgetState, setWidgetState] = useWidgetState();

  const handleSearch = async () => {
    const result = await callTool("search", { query: input.query });
GitHub で README 全文を見る

インストール

This server does not publish a one-line install command.

Open the repository installation guide MCP 初心者?mcpskill.org のガイドから始めましょう →