How AI-Native
Distribution Works
LaunchNests bridges the gap between software development and distribution. Your AI coding agent connects to our cloud control plane via Model Context Protocol (MCP), pulling evergreen playbooks and operating your local browser safely.
"LaunchNests provides the intelligence, workflow, playbooks, state, and coordination. The user's agent performs the work."
We never ask for your passwords, cookies, or browser tokens. Playbooks, relevance formulas, and status telemetry are coordinated in the cloud; all DOM inspection, form submissions, and authentication happen entirely in your local browser session.
Why Cloud-Connected MCP Beats Downloading Static Git Repos
Services like LaunchRepo require you to clone a static git repository with 300 raw markdown files onto your machine. Here is why LaunchNests Ship was engineered with a dynamic Cloud MCP architecture instead.
1. Always Evergreen
Platforms change their form fields, character limits, and categories constantly. A downloaded static markdown file goes stale in weeks. LaunchNests updates playbooks in the cloud database so your agent always retrieves today's verified spec.
2. Dynamic Relevance Scoring
With a static folder, you must manually guess which directories fit your product. LaunchNests uses deterministic scoring to match your product's category, pricing, and audience against active directories, prioritizing the highest ROI first.
3. Zero Local Workspace Clutter
No need to pollute your repository with 300 markdown files, python scripts, or git invitations. A single CLI command links your local workspace to the cloud MCP server in seconds.
4. Centralized Verification Audit
Instead of dumping local CSV files, every submission attempt, status transition (12 states), and public URL verification is tracked centrally on your founder dashboard.
The 5-Stage Distribution Lifecycle
From defining your product brief to live verification across 50+ launch platforms.
Define Your Product Profile Once
In your LaunchNests dashboard, enter your canonical product brief: brand name, 60-character tagline, short & long descriptions, pricing model, logo URL, screenshot assets, and target audience categories.
Connect Your Local Agent via CLI
In your project terminal, run npx launchnests-ship init and npx launchnests-ship login. This links your project and configures the LaunchNests MCP tools in your coding agent (Claude Code, Cursor, Windsurf, Codex).
✓ Configuration written to launchnests.json
$ npx launchnests-ship login
✓ Authenticated terminal session via secure OS keyring
Agent Retrieves Prioritized Targets & Playbooks
When you prompt your agent to distribute the product, it invokes get_launch_targets to fetch the scored targets, then calls get_playbook to get the exact fields, character constraints, and navigation sequence.
target: "Product Hunt" (Priority: 91, Relevance: 94.5%)
playbook: { url: "producthunt.com/posts/new", taglineMax: 60, descMax: 260 }
Safe Local Browser Automation & Human Handoff
Your agent uses Chrome DevTools MCP to navigate forms in your local browser. If a login, CAPTCHA, 2FA challenge, or payment screen appears, it immediately triggers a human handoff, pauses execution, and waits for your confirmation.
"Please sign in with Google in your Chrome window and confirm when done. The agent will resume automatic form completion."
Verification & Live URL Confirmation
Submissions are never marked as "published" simply on an agent's word. The agent records the live submission URL back to LaunchNests via update_submission. Our system verifies HTTP 200 availability and builds a verifiable audit trail.
LaunchNests vs Static Repos vs Agencies
See why modern software teams choose LaunchNests Ship over manual agencies and static git repositories.
| Feature | LaunchNests Ship | Static Git Repos (LaunchRepo) | Submission Agencies |
|---|---|---|---|
| Playbook Freshness | Always live via Cloud MCP | Static files (stale in weeks) | Manual, opaque spreadsheets |
| Relevance Engine | Automated AI & DA scoring | Manual search across 300 files | Blind directory blast |
| Local Workspace Footprint | Zero clutter (1 CLI link) | 300+ local markdown files | N/A (external agency) |
| Browser Credential Safety | 100% Local (never leaves machine) | 100% Local | Must share passwords or OTP |
| Audit Trail & Proof | Centralized Cloud Dashboard | Local CSV file on your laptop | Static PDF or email report |
| Pricing Model | Free / $29 Starter / $89 Unlimited | €105 - €120 one-time | $300 - $500 per launch |
Compatible With Your Favorite Coding Agent
Built natively on Model Context Protocol (MCP). Plugs directly into any modern AI environment.
Claude Code
Native CLI & MCP execution
Cursor
Configured in .cursor/mcp.json
Codex
Direct tool-calling bridge
Windsurf / Custom
Standard stdio / SSE MCP transport