Turn a product spec into a working
CLI + MCP product
Shipwright gives clients one simple path: describe the product, generate the repo, download the starter files, and hand off something they can actually run.
What Shipwright does
Expected output
shipwright generate --spec ./product.yaml ✅ CLI scaffold created ✅ MCP server scaffold created ✅ Starter files downloaded ✅ Client can run and extend it locally
One obvious path from spec to working repo
CLI and MCP generated from the same core definition
Good defaults instead of lots of configuration
Starter files ready to download and hand off
How it works
Describe the product
Give Shipwright a short brief, an OpenAPI file, or a simple list of actions the client needs.
Generate the working surface
Shipwright creates the CLI, MCP tools, docs, and a clean local project structure.
Run, hand off, and iterate
The client can run it locally, connect their backend, and extend it without starting over.
What you get
A usable product, not a demo.
CLI
A command-line interface the client can run, test, and extend.
MCP server
A tool surface that AI clients can connect to immediately.
Docs
Minimal install and usage instructions.
Clean defaults
Simple structure and opinionated choices so the project stays understandable.
Starter files
Download the first repo files
These are the files Shipwright starts from. Download them individually or hand them to a client as the foundation for the generated repo.
product.yaml
A minimal spec template for the product you want Shipwright to generate.
Download →
README.md
A handoff guide with install steps and the first commands to run.
Download →
package.json
The starter package metadata and runnable scripts.
Download →
src/cli.ts
A small CLI entrypoint the generated repo can grow from.
Download →
src/mcp.ts
The MCP surface that mirrors the CLI commands.
Download →
Build the tools your API deserves
Every API should ship with a CLI and MCP server. Shipwright makes it automatic.
Get Started with Shipwright