Let your agent handle the launch.
Give it your repo and this site. It imports the details, asks for anything missing, and finds the directories that fit. You approve the quote, and it tracks every result.
A repo URL is enough to start.
Replace the placeholder in the brief. Any agent that can make HTTPS requests can start; installing an MCP client is optional.
Your agent fills in what it can from the repo and asks you only for what it can’t know.
Prefer to do it yourself? Check my serverRead https://mcpserverlist.io/llms-full.txt and launch my MCP repository at <GitHub repository URL> through MCP Server List. Import its details, resolve missing facts from the source and our project context, and automatically check all supported destinations. Keep resolving source-evidenced facts to improve coverage after the minimum is met; leave optional owner answers optional. Honor my existing authorization for the exact scope and quoted cost; ask only for missing approval or credentials. Track the actual results.
Import the source
Pinned repository metadata becomes a saved launch draft with field evidence.
Check the fit
Eligible destinations and their dependencies are selected automatically. Exclusions stay visible.
Authorize the quote
Use existing owner authority where it applies. Ask only for missing approval of the exact scope and spend.
Resume and track
Saved intake IDs, next actions, payment receipts and provider outcomes work through REST or MCP.
Import, then follow the questions.
Create an account, then use import_repository, get_launch_intake, answer_launch_questions and check_launch_coverage. The equivalent HTTPS requests are shown here.
Each response includes a draft, open questions and next actions.
Send owner credentials straight to POST /api/v1/connections from a secrets store. Pass only the returned connection IDs to tools, and never paste provider secrets into chat.
# Authenticated requests; keep the account key private.
POST /api/v1/intakes
{ "repository_url": "https://github.com/you/your-mcp" }
# Resolve only returned questions and connect the owner.
PATCH /api/v1/intakes/{id}
{ "answers": {}, "github_connection": "connection-id" }
# No directory-selection form. The service checks the fit.
POST /api/v1/intakes/{id}/preflight
{}
# Resume after an interruption.
GET /api/v1/intakes/{id}Then approve, pay and track.
Check the final quote. A launch costs $49 and needs at least one qualifying submission. The quote lists the exact directories your server qualifies for, which is not every directory in the catalog.
An authorized agent pays through a Stripe SPT HTTP 402 challenge. Hosted Checkout is the fallback for a human. Once payment settles, we open the pull requests and report each result.
Some steps still need the owner, like merging a fix to your repo, directory logins and policy confirmations. Importing a URL never approves any of them.
Machine-readable contracts
Maintainers decide whether each directory accepts your server.