LOCALCLI and MCP Server for Claude Code, Codex and Cursor

Automate the setup.Launch in an hour.

Shipyard is a local CLI and MCP server for Claude Code, Cursor and Codex that automates the boring stuff and lets you ship your project from idea to running in an hour. Set it up once, and our agent creates a perfect prompt, then automatically sets up your hosting, payments, emails, database and anything else to get you live. All while you eat your lunch.

  • Connect your stack once
  • Ship every product in an hour
  • Asks before it buys

This is Shipyard.One idempotent, resumable run.

A local CLI and MCP server. Give it a name, a domain and one paragraph. It provisions and wires the full stack through each provider’s official API, stops before it buys anything, then writes the build prompt for your coding agent.

You give it
nameblackpearl
domainblackpearl.dev
one paragraphA tide table app for sailors who plan their week around the weather.
shipyard apply
Shipyard sets up
DomainCloudflare
DNSCloudflare
HostingRailway
PostgresRailway
EmailResend
PaymentsStripe
AnalyticsGoogle
ErrorsSentry
1Stops and asks before it buys2Live at https://blackpearl.dev3PROMPT.md ready for your coding agent

Most products die.So ship more of them.

Volume matters. In the vibecode era building is fast, and most SaaS products still never find a customer. The ones that win come from people who launch many. Setup is the part that should never take more than an hour.

Connect your whole stack to Shipyard one time. After that every new product goes live in an hour.

Time from working repo to live product

By hand, every timea day or twolive
Shipyard, first productan hour + connect oncelive
Shipyard, every product afteran hourlive

Same sixteen jobs either way. One of them you only set up once.

From idea to live, in an hour.

A Terraform-style plan and apply over sixteen ordered steps. Every step finds before it creates and records what it made, so a failed run resumes from the failed step and never duplicates a resource.

Pick your stack

  1. 1Check the domain12.18 USD, free to take
  2. 2Register the domainasked first
  3. 3Create the GitHub repoNext.js starter
  4. 4Create the hosting projectweb, Postgres
  5. 5Connect the repodeploys on push
  6. 6Add the domain, get the certificatehttps ready
  7. 7Set up sending emailDKIM, SPF, DMARC
  8. 8Create products and webhookStripe, test mode
  9. 9Create the analytics propertyG-7K2M…
  10. 10Verify for Search Consolesitemap sent
  11. 11Error tracking and storageDSN, bucket, keys
  12. 12Generate the app's secretsin your keychain
  13. 13Write hosting variables21, none in the repo
  14. 14Health check4 of 4 pass
  15. 15Write the build promptCLAUDE.md
  16. 16Prepare the launch kitProduct Hunt ready
✓ Live at https://blackpearl.dev

Works with the stack you already use

Pick one provider for each job. More are added all the time.

RailwayFly.iosoonSupabaseCloudflare RegistrarPorkbunsoonResendAmazon SESsoonLemon SqueezysoonGoogle Analytics 4PostHogsoonSentrySupabase AuthAmazon S3soonOpenAIGitHubRailwayFly.iosoonSupabaseCloudflare RegistrarPorkbunsoonResendAmazon SESsoonLemon SqueezysoonGoogle Analytics 4PostHogsoonSentrySupabase AuthAmazon S3soonOpenAIGitHub

See the plan before you spend a cent.

shipyard plan lists every resource that will be created, at which provider, and what it costs. Nothing is created until you run apply.

Step 2will create
cloudflare-registrar

Register blackpearl.dev for one year

Shown with its price. Waits for you to type "buy".

12.18 USD once, asks first
Step 3will create
github

Private repository with the Next.js starter

Auth, Postgres, Stripe Checkout and the webhook already in place.

free
Step 4will create
railway

Project with a web service and Postgres

A worker service too, if you ask for one.

5.00 USD a month
Step 6will create
railway

blackpearl.dev and www, HTTPS certificate

Writes the DNS records and waits until the certificate is issued.

included
Step 7will create
resend

Sending domain, DKIM, SPF and DMARC

Then a sending-only key limited to this one domain.

free tier
Step 8will create
stripe

1 product, 2 prices, coupon WELCOME20

Plus the webhook endpoint on your live domain. Test mode.

no monthly fee
Step 9will create
google-analytics

Property with a web stream

The measurement ID goes straight into your variables.

free
Step 10will create
google-search-console

Verify the domain, submit the sitemap

Ownership is proven with a DNS record.

free
Step 11will create
sentry + cloudflare-r2

Error tracking, a bucket and scoped keys

The storage keys only open this one bucket.

free tier
Step 13will create
railway

21 environment variables

Every key and ID on the host. Nothing is written to the repo.

none in the repo
Step 14will create
shipyard

Health check against the live domain

Site, database, a real test email, a real test webhook.

4 checks
Step 16will create
shipyard

Product Hunt and directory launch kit

Every field ready to paste, screenshots in the right sizes.

you press publish

Five moves.Two of them are yours.

01 You

Approve

Shipyard checks the domain and shows you the whole plan with prices. The only thing a launch buys is the domain, and it waits for your word.

  • Price shown before anything happens
  • A spend cap per launch
  • Or bring a domain you already own
blackpearl.devWaiting on you
First year12.18 USD
Renews at12.18 USD / year
Spend cap20.00 USD
BuyStop
02 Shipyard

Build

A repository with a small Next.js starter, a hosting project with a web service and Postgres, and a deploy on every push to main.

  • GitHub repo from the starter
  • Railway: web, worker, Postgres
  • Domain attached, certificate issued
Creating blackpearlBuild
GitHub repositoryCreated
Railway projectCreated
PostgresCreated
HTTPS certificateCreated
03 Shipyard

Wire

The part that eats the day: DNS for hosting and email, Stripe products and the webhook, analytics, search, error tracking and storage, all pointed at each other.

  • DKIM, SPF and DMARC, verified
  • Stripe in test mode, webhook on your domain
  • Never touches a record it did not create
DNS for blackpearl.devWire
CNAME blackpearl.devhosting
TXT resend._domainkeyDKIM
MX sendSPF
TXT _dmarcDMARC
04 Shipyard

Verify

Every key and ID is written into your host as environment variables, then the live site is tested from the outside. You get told what works and what does not.

  • 21 variables, none in the repo
  • A real test email, a real test webhook
  • Run it again any time: shipyard check
Health checkhttps://blackpearl.dev
Site reachable over httpsOK
Database upOK
Test email acceptedOK
Stripe webhook receivedOK
05 You

Build the product

Your coding agent gets a prompt written for this exact stack, committed to the repo as CLAUDE.md and AGENTS.md. And when you are ready to go public, the launch kit is waiting.

  • Variable names and what each is for
  • How to send email, take payments, store files
  • Product Hunt fields, ready to paste
CLAUDE.mdin your repo
## Taking payments
Use Stripe Checkout. Grant access from the webhook, not the success page.
## Security baseline
Authorize every server action.
Security and safety

Your keys never leave your machine.Your money never moves without a yes.

Provider tokens live in your OS keychain and go straight from your machine to each provider’s API. No Shipyard server ever sees them. Purchases need explicit confirmation under a per-launch spend cap, and secrets are redacted from all output.

Read how it is built
  • Keys in your keychainNever in a file, never in the repo, never on our servers.
  • Narrowest permissionsYou are told exactly which scopes each token needs, and why.
  • Asks before it spendsEvery purchase shows its price and waits for you to confirm.
  • A spend cap per launchAnything above the cap is refused, even if you say yes.
  • Secrets never loggedKeys are redacted in every output and every error message.
  • Careful teardownLists what it deletes, needs the project name typed, never deletes a domain.
  • Hands off your DNSIt only changes records it created. Yours are left alone.
  • Official APIs onlyNo browser automation, no scraping, no card numbers handled.

One idempotent run.A full production stack.

Idempotent and resumable

Every step finds before it creates and records the resource in local state. A failed run continues from the failed step and never makes a second copy.

Plan, then apply

Sixteen ordered steps, Terraform-style. The plan shows each resource, its provider and its cost before anything is created.

Official APIs only

GitHub, Railway, Cloudflare, Resend, Stripe, Google and Sentry through their documented APIs. No browser automation.

Wired end to end

DNS, certificate, DKIM, SPF and DMARC, Stripe products and webhook, then every key written to the host as environment variables.

Verified from outside

A health check hits the live domain: HTTPS, database, a real test email and a real test webhook.

A prompt that matches the stack

Generates a build prompt and a CLAUDE.md naming the exact variables and services provisioned, so your coding agent starts with the infrastructure in place.

Claude Code
# add Shipyard to Claude Code
claude mcp add shipyard -- shipyard mcp
# then just ask
> launch blackpearl on blackpearl.dev
Plan ready: 16 steps, 12.18 USD once.
Buying the domain needs your yes.

Let your agent run the launch.

The same engine runs as an MCP server for Claude Code, Cursor and Codex, with tools to plan, apply, check and summarise a launch. The agent never sees a token, cannot confirm a purchase, and cannot destroy anything without your typed confirmation.

Read the MCP docs

Fair questions.

Where do my API keys go?

Into the keychain of your own computer, and from there straight to each provider. They are never written to a file, never put in the repo, and never sent to this website. The site only knows which providers you picked.

Can it spend my money without asking?

No. The only thing a launch buys is the domain. You see the price, and nothing happens until you type "buy". Every launch also has a spend cap, 20 dollars unless you change it.

What if something fails halfway?

Fix what the message tells you and run the same command again. It carries on from where it stopped and never creates a second copy of anything.

Is this a boilerplate?

No. A boilerplate gives you code and leaves the day of setup to you. Shipyard does the setup: accounts wired, DNS written, keys in place. The starter it commits is deliberately small.

What does it not do?

It does not create your provider accounts, pass identity checks, or handle a card number. Stripe verifies your business before live payments. And you submit your own Product Hunt launch.

How do I undo a launch?

One command lists exactly what it will delete and waits for you to type the project name. It never deletes the domain, and it only touches DNS records it created itself.

Connect once. Ship every week.

More launches means more chances that one of them works. Rehearse the first one tonight against fake providers: no keys, no accounts, nothing touched.

Shipyard: automate the setup, launch in an hour