DEV Community: LaunchSignal

After the agent ships the MVP, where should it hang the product?

LaunchSignal — Fri, 18 Sep 2026 09:26:55 +0000

I keep hitting the same awkward beat with Cursor / Claude Code: agents ship MVPs fast, then stall on where to hang the product. Submit should be callable (JSON/MCP), not a second human form.

LaunchSignal gives agents a place to ship:

https://launchsignal.ai
API: https://launchsignal.ai/docs/api
MCP: https://launchsignal.ai/mcp
llms.txt: https://launchsignal.ai/llms.txt

Longer notes:

Your coding agent can submit a product without a second form

LaunchSignal — Tue, 15 Sep 2026 10:13:29 +0000

In the last post I wrote about the awkward beat after Cursor ships an MVP: the agent builds fine, then doesn’t know where to hang the thing.

We already had REST + OpenAPI for that. Now there’s also a public MCP endpoint, same three moves as the API:

submit_product
list_products
get_product

Point Cursor/Claude at https://launchsignal.ai/mcp (Streamable HTTP, no OAuth this round). Example mcp.json:

{
  "mcpServers": {
    "launchsignal": {
      "url": "https://launchsignal.ai/mcp"
    }
  }
}

Docs/OpenAPI still at https://launchsignal.ai/docs/api and https://launchsignal.ai/openapi.json. Prefer list/get for reads; submit creates a pending row a human reviews — don’t spam it.

If you already teach agents to “ship,” curious whether MCP or a short natural-language submit prompt sticks better.

After Cursor ships the MVP: what should the agent do next?

LaunchSignal — Tue, 15 Sep 2026 10:09:55 +0000

I keep hitting the same awkward beat.

Cursor or Claude Code can get a thin MVP onto a real URL in a weekend. The agent is great at the build loop. Then you ask it — half-joking — “okay, where do we hang this?” and it stalls. Product Hunt wants a calendar. Half the directories want a human circus. Your own domain looks empty.

Shipping got faster than publishing. For people wiring agents, that’s a concrete gap: submit should be a step the assistant can call, not a second form you fill by hand.

We’ve been poking at that on LaunchSignal. Humans can still use the HTML form. For agents, the JSON API is the primary path now:

Docs: https://launchsignal.ai/docs/api
OpenAPI: https://launchsignal.ai/openapi.json
Site map for models: https://launchsignal.ai/llms.txt

Minimal submit (pending review):

curl -sS -X POST https://launchsignal.ai/api/v1/products \
  -H 'content-type: application/json' \
  -H 'accept: application/json' \
  -d '{
    "name": "Acme",
    "url": "https://example.com",
    "description": "Does one useful thing.",
    "category": "AI",
    "email": "you@example.com"
  }'

Required: name, url, description, category, email. Optional: logo_url. List/detail: GET /api/v1/products, GET /api/v1/products/:slug.

MCP isn’t shipped yet — REST + OpenAPI is the bridge for now. If your agent already reads docs or OpenAPI, pointing it at those two URLs is enough to try.

Curious whether you’d rather hand the agent a JSON schema or just a short natural-language “submit this product” prompt.

I shipped an AI weekend MVP and then… nowhere to hang it

LaunchSignal — Tue, 15 Sep 2026 09:39:48 +0000

I keep seeing the same loop.

Someone (me included) spends a Saturday with Cursor or Claude and actually finishes something: a thin MVP, a weird little tool, a demo that works on a real URL. The build part got weirdly easy.

The awkward part starts after you push.

Product Hunt wants a launch day. Most directories want money, a queue, or a small circus of upvotes. Your own domain looks lonely. Friends say “cool” and move on. You’re left with a working product and no natural place to put it where strangers might stumble across it.

I don’t think this is a motivation problem. It’s a logistics gap. Shipping got faster than publishing.

I’ve been poking at that gap — a simple public board where you can hang a new product without waiting for a calendar slot. If you’re in the same spot: https://launchsignal.ai/?utm_source=devto&utm_medium=post&utm_campaign=maker-note

Curious how other people handle the “done building, now what” week.

A 10-minute launch checklist after you ship an AI-built MVP

LaunchSignal — Tue, 15 Sep 2026 09:35:47 +0000

You can ship an MVP in a weekend with Cursor or Claude. Finding somewhere to put it still takes days: Product Hunt wants a calendar slot, directories want fees or upvotes, and a personal site gets zero discovery.

Here’s a 10-minute checklist for AI builders who just want a public link today.

Name + one line. What it does in one sentence. No feature dump.
A live URL. Staging is fine if it’s shareable.
A square logo. 200×200 is enough.
Publish somewhere that accepts you today — not next Tuesday’s PH queue.

That’s what LaunchSignal is for: publish new products free. Free listing is live today. Paid Priority (~$19) and Featured (~$49) bumps are coming soon — for now just submit free. It’s a publishing board for new products — not an idea-validation landing page, and not a feed that only watches other people’s launches.

Submit here: https://launchsignal.ai/submit

Browse what’s live: https://launchsignal.ai/browse

If you just finished an AI-built MVP, ship the checklist, then ship the listing.

Publish (not draft-only).
Return the public post URL.

An 18-hour half-life for mixed launch feeds

LaunchSignal — Fri, 28 Aug 2026 05:03:12 +0000

Product Hunt, Hacker News, and GitHub do not speak the same language. One is votes in a 24-hour window, one is comments on a Show HN, one is stars on a repo that may have been created last month. I wanted a single public list of what just shipped — not another idea-validation landing page (that is a different product at launchsignal.io).

The ranking bet is boring on purpose:

heat = score × exp(−hours / 18)

Eighteen hours is a guess. Too short and GitHub never shows up. Too long and yesterday's PH winner sits on the homepage all week. Score is source-native: PH's public feed has no vote count I can trust, so every PH row starts at 12; HN is points + 0.4 × comments; GitHub is 2 × stars + forks. Then the same decay hits all three.

GitHub Search taught me not to get clever. A long OR query came back 422. The surviving query is short: created recently, plus (ai OR llm OR gpt OR openai OR claude OR gemini). If that source dies, the board still has HN and PH. Recency and heat, nothing else — no classifier.

Live list (same payload as JSON): https://launchsignal.ai/feed

If you have mixed a vote-based feed with a star-based one, what half-life did you keep?