Agentic Mcp Server Builder

Scaffold MCP server projects and baseline tool contract checks. Use for defining tool schemas, generating starter server layouts, and validating MCP-ready st...

Security Scan

The skill's code and instructions match its stated purpose (scaffolding MCP servers); it has no network behavior or credential requests, but it does write files to disk and can be allowed to write outside the workspace, so test with dry-run and review targets first.

Purpose & Capability

Name/description (scaffold MCP servers and contract checks) align with the included script and docs. The script reads a JSON payload describing tools and generates a file map and starter files — this is exactly what a scaffolder would need to do.

Instruction Scope

SKILL.md confines the agent to run the provided script and read the included guide. The script only reads a local JSON input and writes local scaffold files. Note: SKILL.md suggests materializing files when not in dry-run mode, so follow guardrails to use --dry-run first.

Install Mechanism

No install spec is provided and the skill only includes a small Python script and markdown references. There is no download-from-URL or package installation step.

Credentials

The skill requests no environment variables, no credentials, and the script does not read environment variables or external config paths. There are no secrets or external API keys involved.

Persistence & Privilege

always is false and the skill is user-invocable. The script writes scaffold files into a scaffold_root under the current workspace by default; it can be allowed to write outside the workspace only if the --allow-outside-workspace flag is passed. The script will overwrite existing files without prompting.

Assessment

This skill appears coherent for scaffolding MCP servers. Before running: 1) run with --dry-run to verify the generated file map and output (no writes); 2) confirm the scaffold_root and output paths are correct and back up any important files (the script will overwrite existing files); 3) avoid passing --allow-outside-workspace unless you explicitly trust the input and destination, since that allows writing outside the current directory; 4) inspect any input JSON you provide and the generated artifacts locally — the tool does not perform network calls or access credentials, so risks are limited to local file writes and accidental overwrites.

Overview

Create a minimal MCP server scaffold and contract summary from a structured tool list.

Workflow

1. Define server name and tool list with descriptions.
2. Generate scaffold file map and tool contract summary.
3. Optionally materialize starter files when not in dry-run mode.
4. Review generated contract checks before adding business logic.

Use Bundled Resources

• Run scripts/scaffold_mcp_server.py to generate starter artifacts.
• Read references/mcp-scaffold-guide.md for file layout and contract checks.

Guardrails

• Keep tool boundaries explicit and minimal.
• Include deterministic outputs and clear input/output schemas.