LaunchDistro is an MCP server for Codex, Claude, Cursor and VS Code that submits your startup to directories. Codex 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: one config.toml entry covers the Codex CLI, the IDE extension and the ChatGPT desktop app.
From your README and landing page.
Ask Codex to write your product profile from the repo it's already in. It saves it with save_product_profile, and every submission uses it, so your name, tagline and links match on every directory.
Each one tested on a real submission.
Before it touches a form, Codex 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, Codex stops and tells you. Do it, say so, and it carries on.
Add the server, ask Codex, watch the forms fill. The same three steps in the terminal, your editor or the ChatGPT app.
One table in config.toml
Paste the entry into ~/.codex/config.toml with the token from your dashboard. Nothing to install.
In any Codex session
Say what you want. Codex picks directories that fit your product and shows you the plan, with a reason for each, before anything is submitted.
Then the live check
Codex 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.
The details the Codex docs spread across several pages, in one place.
~/.codex/config.toml. Add LaunchDistro once and it's in all three./mcp inside a Codex session lists the servers that connected; codex mcp list in a terminal lists everything configured.<your-token> in the entry. Revoke one and the others keep working.MCP (Model Context Protocol) lets Codex call tools outside the chat. An MCP server offers those tools; LaunchDistro's runs at launchdistro.com, so Codex only needs its URL and a token. It gives Codex tools to pick directories for your product, read each one's playbook and check the links went live.