Overview

Create a minimal MCP server scaffold and contract summary from a structured tool list. It defines the server name and tool descriptions, then generates a scaffold file map and tool contract summary. Optional starter files can be materialized when not in dry-run mode, and contract checks should be reviewed before adding business logic.

How This Skill Works

It reads a defined server name and tool list with descriptions, then outputs a scaffold file map and a tool contract summary. If not in dry-run mode, it can materialize starter files and produce deterministic, contract-focused outputs for review before coding.

When to Use It

• Starting a new MCP server project with a predefined tool set.
• Defining tool schemas and ensuring deterministic input/output contracts.
• Generating a starter server layout to bootstrap development.
• Validating MCP-ready structure before implementing business logic.
• Materializing starter files after a dry-run to finalize repo setup.

Quick Start

1. Step 1: Define server name and tool list with descriptions.
2. Step 2: Run scripts/scaffold_mcp_server.py to generate starter artifacts.
3. Step 3: Review contract checks and, if desired, materialize starter files in non-dry-run mode.

Best Practices

• Keep tool boundaries explicit and minimal to avoid scope creep.
• Define deterministic outputs and clear input/output schemas.
• Review generated contract checks before adding business logic.
• Follow the bundled scaffold guide for file layout and references.
• Use a dry-run to verify scaffold results before materializing files.

Example Use Cases

• Bootstrap an MCP server named AdventureHub with tools Teleport and InventorySync.
• Add a new tool contract for HealthMonitor and generate its schema contract.
• Run scaffold in dry-run to inspect outputs without creating files.
• Materialize starter files for an existing MCP service to bootstrap development.
• Review contract checks after scaffolding to ensure compatibility with business logic.

Frequently Asked Questions