Status: Raw idea · Captured: 2026-08-19 · Owner: Yaro

One-liner

A launch and progress platform for founders, builders, indie hackers and communities where the entire launch is created and operated through MCP — the builder connects their repo, and their own agent/AI assembles the launch page, content and schedule from the repo, the website and project files.

Core loop

  1. Builder connects their repo (and optionally site + project files) via MCP.
  2. Their agent generates the full launch listing: description, positioning, screenshots/assets, tags, media.
  3. The launch is scheduled for a release date, straight from the MCP client — no web form filling.
  4. Post-launch, the builder ships an update and posts "what changed" the same way. The feed of updates becomes a public record of the project's progress and decisions.

Key concepts

MCP-first, not web-first

Everything a builder does on a normal launch site — create listing, upload assets, schedule, post updates — is exposed as MCP tools. The web app is the reader/consumer surface; the builder surface is their agent.

Content generated from real sources

Copy is not written from scratch in a text box. It is derived from the actual repo, README, changelog, commits, website copy and project files. The builder's own AI/agent assets do the writing, so the voice stays theirs.

Updates as the primary content type

Not just a one-shot launch. Each shipped change can be posted as an update. Over time a project accumulates a timeline of what changed and why — progress and decisions, not just version numbers. This is the thing Product Hunt doesn't have.

Projects are companies/communities

A project is not a single listing owned by one account. It is an entity that can have: