Connect your agent

Set it up once. From then on you do everything from your agent: it writes your listing, books your launch week and reports your votes and comments.

Choose your agent

Add the server to Claude Code

Terminal

claude mcp add --scope user --transport http launchdog https://launchdog.dev/mcp

Sign in

In Claude Code, run /mcp, pick launchdog and sign in. A browser tab opens to approve it.

Using the Claude desktop app? Sign in from a terminal: run claude, then /mcp, sign in and /exit. Then start a new session in the app: a session loads its MCP servers when it starts.

Paste this prompt

coding agent · edits your repo

Use the launchdog MCP server to launch this product on Launchdog.

1. Call `whoami` first. If I already have a product, resume from its checklist (the first open step says what to do).
2. If there's no product yet, call `create_product` with the site URL (find it in this repo — CNAME, `homepage` in package.json, deploy config — or ask me).
3. Improve the draft from my live home page (what it says the product does); use the README only if it describes the product, not just how to develop it. Aim for a tagline under 60 characters, a plain 150–1,200 character description with no hype words and no numbers that will go stale, up to 3 categories and the built-with tools you can see in this repo. Then the details people search for, from the repo and the live site: pricing (model, and the "from" price and period from the pricing page; leave it out if unsure), platforms, a "best for" line, 3–6 features and up to 4 FAQs a buyer would ask that the site doesn't answer, in your own words (no hype, no links, no prices in answers); what it works with, what it's an alternative to (names only), the repo URL if the source is public and a demo video if there is one. Lint it with `update_product` and dry_run: true, save it, then give me its listing_url to review on the page (until it launches only I can open it, signed in to Launchdog) and change what I ask.
4. Call `launch_checklist` and fix what's left of the listing, then `list_launch_weeks`. Show me the free and paid options side by side, with what each needs, and let me choose. Call `whoami` again: if `account.founding.state` is add_badge, tell me this listing's badge earns a free year of Maker Pass; if `account.founding.open` is true for another reason, tell me what `account.founding.next` says.
5. Paid (launch or featured): after my OK, call `schedule_launch`. It needs nothing else: no badge, no changes to my site. Never buy anything: give me the checkout link it returns, then confirm with `get_launch`. Already booked free? The same call with tier launch or featured upgrades it in its week.
6. Free launch only: it needs the Launchdog badge on my home page. Call `get_badge_snippet` for this repo's framework and add it to the home page footer (in the HTML the server sends). Ask me once for OK to commit and push it. If this repo deploys on push (a CI deploy workflow, Vercel, Netlify…), watch the deploy yourself until it's live and fetch my home page to see the badge; otherwise ask me to deploy. Then call `check_badge` (it also verifies my domain) and `schedule_launch` with tier free for the week I picked. If `check_badge` returns a founding_number, my free year of Maker Pass has started: tell me, and ask whether to book tier launch at $0 in any open week instead. For a paid launch the badge is optional: add it only if I ask.
7. If a check fails, read its fix and diagnostics and fix that; don't guess. If I've already told you my tier, my week or that you may commit and push, don't ask again.
8. Once it's booked: ask me in a sentence or two why I built it and save that as maker_note (`update_product`). Fill in my maker profile with `update_profile` (voters open it from the listing) — a one-line bio in my voice about what I build, and my links from this repo and my site (README, package.json author, the footer); GitHub comes from my sign-in. Show me before saving. Then draft a short launch-day post with the listing URL (from `get_launch`) for me to share on Monday, remind me to upvote and comment on this week's launches on the board, and during my week read comments with `list_comments` and draft replies (`reply_comment`) for my OK. When I ship something worth telling, draft an update for the listing (`add_update`) from the changelog or commits.
9. At the end, if any step was harder than it should have been (a confusing result, a fix that didn't help), tell Launchdog once with `send_feedback`: what you were doing, what you expected and what happened. Show me what you'll send first, and don't include secrets or private code.

Run it from your product's repo so the agent can add the badge if you choose a free launch. Paid launches need neither. It asks for your OK before anything is saved or booked.

Clients with MCP prompts can also run launch_my_product.

Prompt for chat clients (Claude, ChatGPT)

Use the Launchdog connector to launch my product at <SITE URL>.
Call `whoami` first and resume from my checklist if I already have a product; otherwise draft the listing from my site with `create_product`.
Tighten the tagline to under 60 characters and the description to 150–1,200 plain characters, and add the details people search for from my site: pricing (model, and the "from" price and period from the pricing page; leave it out if unsure), platforms, a "best for" line, 3–6 features and up to 4 FAQs a buyer would ask, in your own words (no hype, no links). Lint with `update_product` (dry_run: true), save it, then give me its listing_url to review on the page (until it launches only I can open it, signed in to Launchdog) and change what I ask.
Run `launch_checklist`, then show me the free and paid options side by side from `list_launch_weeks`, with what each needs, and let me choose. Call `whoami` again: if `account.founding.state` is add_badge, tell me this listing's badge earns a free year of Maker Pass; if `account.founding.open` is true for another reason, tell me what `account.founding.next` says.
Paid (launch or featured): after my OK call `schedule_launch`; it needs nothing else. Don't buy anything: give me the checkout link it returns and confirm with `get_launch`. Already booked free? The same call with tier launch or featured upgrades it in its week.
Free launch only: give me the badge HTML from `get_badge_snippet` to paste into my site's home page, check it with `check_badge` once I say I've deployed (it also verifies my domain), then call `schedule_launch` with tier free. If `check_badge` returns a founding_number, my free year of Maker Pass has started: tell me, and ask whether to book tier launch at $0 in any open week instead. If a check fails, read its fix.
Once it's booked: draft my maker profile for `update_profile` (voters open it from the listing) — a one-line bio about what I build and my links (ask me for them) — and save it after my OK. Then draft a short launch-day post with the listing URL for me to share on Monday, remind me to upvote and comment on this week's launches, and during my week draft replies to comments (`list_comments`, `reply_comment`) for my OK.
At the end, if any step was harder than it should have been, tell Launchdog once with `send_feedback`: what you were doing, what you expected and what happened. Show me what you'll send first.

after launch, ask your agent

“How is my launch doing? Summarise views, clicks, votes and rank by day.”
“Read the comments on my launch and draft replies for me to approve.”
“Move my launch to the next week with a free spot.”