spec-driven-mcp-converterlisted

Convert any MCP (Model Context Protocol) server into a standalone CLI utility and auto-generate companion skill documentation through an 8-phase workflow with structural anti-skip enforcement. Prevents token optimization bias through per-phase reference loading, checkpoint persistence, Execute-Verify-Record enforcement, and artifact verification. Use when you have an MCP server (Puppeteer, filesystem, weather, database, etc.) and need to: (1) Create a standalone CLI wrapper that Claude Code can execute, (2) Auto-generate a skill so Claude understands how to use the CLI, (3) Bridge MCP async patterns into sync CLI patterns, or (4) Rapidly prototype tool integration without MCP server overhead. Always use this skill when the user runs /convert-mcp. Make sure to use this skill whenever the user mentions converting MCP servers, bridging MCP to CLI, wrapping MCP tools as commands, or generating CLI utilities from MCP definitions — even if they don't explicitly say "convert-mcp".
bankielewicz/DevForgeAI · ★ 4 · AI & Automation · score 66

Install: claude install-skill bankielewicz/DevForgeAI

# Spec-Driven MCP Converter Convert any MCP server into a locally-executable CLI utility with auto-generated skill documentation. This hybrid framework handles 80% of MCP patterns automatically while allowing custom extensions for outliers. **Context files are THE LAW:** tech-stack.md, source-tree/, dependencies.md, coding-standards.md, architecture-constraints.md, anti-patterns.md **If ambiguous or conflicts detected: HALT and use AskUserQuestion** --- ## Execution Model See **`.claude/rules/core/anti-skip-behavior.md`** for the canonical execution contract (expand inline; do not wait passively or offer execution options; honor every step of every phase; Self-Check violation taxonomy; Token-Optimization-Bias prohibition; governed by ADR-076). After invocation, execute Phase 00 Initialization immediately. --- ## Anti-Skip Enforcement Contract Enforced structurally outside LLM control, not by this prose — by the framework's deterministic gates wired for this workflow: the `devforgeai-validate` phase gates, the `settings.json`-registered `.claude/hooks/` scripts, and `.claude/hooks/phase-steps-registry.json` (ADR-076). Behavioral residue: `.claude/rules/core/anti-skip-behavior.md`. Layer 4 (CLI phase-gate) is not wired for this workflow (no `CONVERT-` workflow schema registered). --- ## Three Conversion Patterns The skill handles 3 MCP conversion patterns, detected automatically or specified via `--pattern`: | Pattern | Use Case | Detection | Frequency | |--------