Connect your agent · Launchdog

Add a custom connector to Claude

In Claude (web or Desktop): Customize → Connectors → Add custom connector, and paste this URL.

Connector URL

https://launchdog.dev/mcp

Sign in

Claude opens a Launchdog sign-in window. Approve it, and the connector is ready. That is the whole sign-in.

Paste this prompt

chat app · you paste the snippets

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, preview with `update_product` (dry_run: true) and show it to me before saving.
Then give me the domain verification record from `start_domain_verification` and, for a free launch, the badge HTML from `get_badge_snippet` to paste into my site. Check both with `check_domain_verification` and `check_badge` once I say I've deployed; if a check fails, read its fix.
Run `launch_checklist`, then suggest the earliest free week from `list_launch_weeks`. After my OK call `schedule_launch`. Don't buy anything; if I want a paid tier, give me the checkout link it returns and confirm with `get_launch`.

Your agent hands you the tag and badge to paste into your site. It asks for your OK before anything is saved or booked.

Clients with MCP prompts can also run launch_my_product.

Prompt for coding agents (Claude Code, Codex, Cursor, VS Code…)

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. Read this repo's README and improve the draft: a tagline under 60 characters, a plain 150–1,200 character description with no hype words, up to 3 categories and the built-with tools you can see in this repo. Preview it with `update_product` and dry_run: true, show it to me, and save only after my OK.
4. Call `start_domain_verification` and add the <meta> tag to the site's layout. Tell me to deploy and wait for me to say I've deployed, then call `check_domain_verification`.
5. For a free launch only: call `get_badge_snippet` for this repo's framework and add the badge to the home page footer (in the HTML the server sends). After I deploy, call `check_badge`.
6. If a check fails, read its fix and diagnostics and fix that; don't guess.
7. Call `launch_checklist`, then `list_launch_weeks`. Suggest the earliest free week and show the paid options.
8. After my OK, call `schedule_launch`. Never buy anything: for a paid tier give me the checkout link it returns, then confirm with `get_launch`.

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.”