AgentLaunch

AgentLaunch MCP server

Plan and run a paced directory launch for your startup, SaaS or AI tool from Claude Code, Cursor, Codex or any MCP client. Your agent picks the directories, writes copy for each one and queues the work. The AgentLaunch Chrome extension fills the real submission forms in your own Chrome, a few a day, and hands you anything that needs a person.

• 300+ checked directories (startup, SaaS, AI, launch platforms, review sites, MCP registries), picked from 2,703 we reviewed
• Your browser, your accounts. Forms are filled in your Chrome profile, not on someone else's servers
• Paced on purpose. 10 submissions a day by default, never more than 20 in 24 hours
• You stay in charge. Passwords, CAPTCHAs, email codes, payments and final approval on major platforms always come back to you
• Proof, not a report. Every directory gets a status, a public listing URL and a dofollow/nofollow link check

New customers run AgentLaunch on their own deployment. The hosted endpoint at https://www.agentlaun.ch/mcp is a legacy endpoint for one grandfathered customer and is not available for new purchases. This repository holds the MCP server listing, client configuration and agent skill; the source code ships with the Self-Host License.

Pricing

AgentLaunch is a paid product. You need one of these before your agent can add a product:

See pricing →

Quick start

1. Get access. Buy the $149 Self-Host License at agentlaun.ch, then deploy the private source on your own host using the self-hosting guide.
2. Install the Chrome extension and create an API key on your deployment's https://<site>/connect page. Keys start with rl_ and are shown once. Store it in your client's secret settings.
3. Add your deployment's MCP endpoint (https://<site>/mcp) to your client (below).
4. Ask your agent to call list_projects, then plan the launch with you.

Claude Code

claude mcp add --transport http agentlaunch https://<site>/mcp \
  --header "Authorization: Bearer rl_YOUR_KEY"

Cursor, Windsurf and other MCP clients

{
  "mcpServers": {
    "agentlaunch": {
      "url": "https://<site>/mcp",
      "headers": {
        "Authorization": "Bearer rl_YOUR_KEY"
      }
    }
  }
}

Test the connection

curl -X POST https://<site>/mcp \
  -H 'Authorization: Bearer rl_YOUR_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Agent skill (optional)

The skill teaches your agent the launch workflow: when to ask you, how to pace, what never to do on your behalf.

mkdir -p ~/.claude/skills/agentlaunch && curl -fsSL https://<site>/skills/agentlaunch/SKILL.md -o ~/.claude/skills/agentlaunch/SKILL.md

What your agent can do

The server exposes 29 tools over Streamable HTTP. The same rules apply as in the web app: the agent can queue work, but it can't skip approvals, pacing, checkpoints or payments.

A typical session:

1. list_projects → start_launch for a product URL. The agent explains that this uses a launch credit and waits for your yes.
2. update_project_brief with taglines, descriptions and pricing, which you check.
3. set_launch_budget → plan_launch: free routes first, then paid listings ranked by value per dollar.
4. approve_launch_plan only after you approve the exact list and total.
5. queue_launch: the server releases the approved daily pace to your Chrome.
6. get_needs_you whenever you check in, and check_listing to verify live listings and their links.

Self-host it for your clients

The $149 Self-Host License gives you the full AgentLaunch source code in a private GitHub repository: the web app, launch agent, this MCP server, the Chrome extension and the directory catalog, with catalog updates every 3 months. Run it on your own Railway account with your own AI key, and every account on your copy gets unlimited launches. New customers connect their MCP client to their own deployment at https://<site>/mcp.

It's built for developers and agencies who launch products repeatedly or run launches for clients. Read the self-hosting guide to deploy it.

Security

• Keys start with rl_, are shown once and can be revoked on the Connect page.
• Requests without a valid key get 401 Missing or invalid API key.
• The agent never sees your passwords, email codes or card details. Those steps happen in your browser.
• Gmail access for verification emails is optional and read-only.

Links

• Docs: agentlaun.ch/docs
• Directory catalog: agentlaun.ch/directories
• Support: support@agentlaun.ch
• Built by @pruthveeee