Tldr; we built an MCP server that lets you connect one and sets up your domains, emails, cloudflare, database, analytics, AI integration and much more in just one hour, allowing you to ship at the speed of light.
In 2023, Marc Lou's ShipFast fixed the slowest part of launching a product. You bought a Next.js boilerplate with payments, login and email already written, and you skipped weeks of code. It worked because back then, writing the code was the hard part.
That has changed. Today Claude Code, Cursor or Codex writes a login flow in two minutes. Nobody needs to buy code they can generate before their coffee is cold.
In today's era, volume is everything: everyone can build an app or SaaS in a night, and 99% of these ideas won't make any money.
That means you need to ship agressively, and often. What's holding you down in shipping more often is now not the tech, but the integrations, which often costs a day or two to set up properly.
\*\*What a launch costs you today\*\*
Do the sum once. Say the setup takes you twelve hours per product, spread over a day or two of waiting on DNS, re-reading docs and chasing one wrong key. Ship four ideas a month and that is 48 hours: more than a working week, every month, spent on work that is identical each time and teaches you nothing about whether the idea is any good.
Put a price on your time. At $75 an hour, 48 hours is $3,600 a month. At $40 it is still $1,920. And that is the cheap part. The expensive part is the ideas you never launched because the setup did not feel worth it for something that might not work.
The point of shipping in volume is that each attempt is cheap. If an attempt costs two days, you make ten a year. If it costs an hour, you make ten a month, and the market gets to pick the winner instead of your gut.
\*\*The new bottleneck\*\*
Because the code was never the last step. To put a product in front of a paying customer you still have to:
\\- Buy a domain and point the DNS
\\- Create the hosting project and the database
\\- Verify a sending domain so your emails arrive
\\- Create the Stripe product, the prices and the webhook
\\- Copy a dozen keys into the right places without leaking one
\\- Connect analytics, search and error tracking
None of that is hard. All of it is slow. It is eight dashboards, forty clicks each, and one typo in an environment variable that costs you an evening. Your AI can write the app, but it cannot click through Cloudflare for you.
I kept hitting this. I could build a product in a weekend and then lose another weekend wiring it up. So I built the thing I wanted.
\*\*What Shipyard is\*\*
Shipyard is a local CLI and MCP server for Claude Code, Cursor and Codex. You connect your accounts once. After that, every new product goes like this:
\\- Describe the product and pick a UI style.
\\- Review everything that will be set up, and what it costs, before anything happens, our agent can spend money only if you allow it to.
\\- Press launch.
Shipyard then registers the domain, sets up DNS, creates the repo, the hosting and the database, verifies your email domain, creates your Stripe product and webhook, and writes every secret to the right place. At the end it hands your coding tool a build prompt written for the exact stack it just created, including UI guidelines in your colours.
You paste the prompt. Your AI builds on infrastructure that is already live. All why you're eating your lunch.
Shipyard was launched this way. Shipyard bought its own domain.
\*\*Idempotent by design\*\*
Real APIs fail halfway. A registrar times out, a certificate takes twenty minutes, a webhook secret arrives late. So every step follows one rule: find before create. Before making a repository, a DNS record, a Stripe product or a database, Shipyard looks for the one it made earlier and adopts it.
Progress is written to a state file after each step. If a launch stops at step seven, you fix the cause and resume from step seven. Running the same launch twice gives you one of everything, not two.
The same engine has a rehearsal mode. It walks all sixteen steps against a simulated set of providers, shows you every resource and every price, and touches nothing real.
\*\*How secrets are handled\*\*
This is the part I was strictest about, because a setup tool is exactly the kind of program that leaks keys.
Tokens live in the operating system's keychain. They are never written to a plain file and never sent to our servers. The website has no endpoint that could receive one.
Every log line, error and terminal output passes through a redactor that masks known secret values before anything is printed.
Secrets go from the provider that issued them straight into your host's environment variables. Only the variable names are written into the repo, never the values.
Each token is asked for with the narrowest scope that works, listed with the reason for each permission. Storage keys are minted for one bucket only.
Licences are checked offline against a public key built into the program. There is no call home.
\*\*The setup page\*\*
Vibecoders do not want to live in a terminal, so most of Shipyard happens in a page in your browser. One command starts a small server bound to 127.0.0.1 on a random port, opens the page, and protects it with a random key in the address. It has a strict content security policy and loads nothing from the internet.
In that page you connect each account with the exact clicks beside it, see a dashboard of your stack, fill in the product form, review the plan and watch the launch run step by step, with a timer and a note on how long each step usually takes.
\*\*The MCP server\*\*
Shipyard is also an MCP server, so your coding tool can drive it. Tools such as shipyard\\_plan, shipyard\\_apply, shipyard\\_check, shipyard\\_prompt and shipyard\\_seo let Claude Code, Cursor or Codex show the plan, run a rehearsal, check a product's health after a deploy and fetch today's SEO task, without leaving the chat.
The guard rails hold wherever a launch is started from. Anything that spends money stops and waits for a person.
\*\*The build prompt\*\*
The last step is the one that makes the rest useful to an AI. Most bad AI builds start with a vague brief: the tool invents a database, picks its own payment flow and you spend the evening undoing it.
Shipyard writes the brief from facts. The prompt names the host, the database, the real environment variable names, the webhook path and the sending address, and it is committed to the repo as CLAUDE.md and AGENTS.md so every coding tool reads it. If you leave the UI guidelines on, it also carries a full design system derived from the colour you picked, with contrast already checked.
\*\*Why it runs on your machine\*\*
A tool that holds the keys to your Stripe, your domain and your hosting has to earn trust. So the rules are strict:
It runs locally. Your keys are stored in your computer's keychain and are never sent to our servers.
It asks before it spends. The only purchase in a launch is the domain. You see the price and type "buy" first, and a spend cap refuses anything above it.
It asks for the narrowest permissions that work, and tells you which and why.
It never touches DNS records it did not create, and it never deletes a domain.
You own every account. If you stop using Shipyard tomorrow, everything it set up keeps running.
Pretty sure I cannot post links here but looking for ShipyardMCP\\\[dot\\\]com will get you there. If youre a vibecoder struggling with these annoying tasks, reach out and i can give you a free trial.