Add it once, then ask in chat. The agent fills directory forms in your own browser from your product profile and a tested playbook, and every backlink is checked on the live page.
Run this once in a terminal. It adds LaunchDistro to your VS Code profile:
LaunchDistro is an MCP server for VS Code, Claude, Cursor and Codex that submits your startup to directories. The agent in VS Code's chat fills each form in your own browser from a tested playbook, stops for sign-ins and CAPTCHAs, and LaunchDistro checks each backlink on the live page. Nothing to install.
From the repo you have open.
Ask the agent to write your product profile from your README and landing page. It saves it with save_product_profile, and every submission uses it, so your details match on every directory.
Each one tested on a real submission.
Before it touches a form, the agent reads that directory's playbook: what the form asks, what the free plan really gives, the traps and where to stop. When a directory wants a badge, it can add it to your footer and show you the diff.
Your browser, your accounts.
The forms fill in your own browser, signed in as you. When a site wants a sign-in, an emailed code, a CAPTCHA or a fee, the chat tells you. Do it, say so, and it carries on.
Add the server, trust it once, ask in chat. Nothing to install.
One line, or MCP: Add Server
The command adds LaunchDistro to your VS Code user configuration with your token. The first time it connects, VS Code asks you to trust it.
Agent mode
Open the chat, pick agent mode and say what you want. The agent picks directories that fit your product and shows you the plan, with a reason for each, before anything is submitted.
Then the live check
The agent opens each directory in your browser and fills the form. It stops for sign-ins and fees, records the confirmation, then checks the live page for your link.
Where the configuration lives, what the prompts mean, and how to check it's working.
MCP: Open User Configuration) makes LaunchDistro available in every project; that's where the command puts it. .vscode/mcp.json adds it to one project, and gets committed with it if you're not careful.servers key. A config copied from Claude Desktop or Cursor uses mcpServers and won't load there.code --add-mcp takes the server as JSON and adds it to your user configuration. On Windows, PowerShell quotes differently, so MCP: Add Server is easier there.MCP (Model Context Protocol) lets the agent in VS Code's chat call tools outside the editor. An MCP server offers those tools; LaunchDistro's runs at launchdistro.com, so VS Code only needs its URL and a token. It gives the agent tools to pick directories for your product, read each one's playbook and check the links went live.