API and MCP

Nick Launches is agent-native. Search the catalog, audit a site, and open a launch draft from any MCP client, with no browser in the loop.

Read the docs Quickstart

The MCP server

One base URL, https://nicklaunches.com/api/mcp/, served over Streamable HTTP. No install, no local process, no API key to paste. Point a client at it and the tools show up.

Claude Code

claude mcp add --transport http nicklaunches https://nicklaunches.com/api/mcp/

Claude Desktop, Cursor and other clients

{
  "mcpServers": {
    "nicklaunches": {
      "url": "https://nicklaunches.com/api/mcp/"
    }
  }
}

No API keys

Search and reads are anonymous, so an agent can explore the catalog the moment it connects. The first time it tries to create a draft it hands you a one-time link. You approve it in a browser you are already signed into, and the connection is bound to your account from then on. No token ever passes through the transcript.

Nothing to generate, nothing to store in your dotfiles
One click in a browser you already trust
Revoke any connection at any time

Manage your connections How the link flow works

How a submission works

An agent can never publish, pay, or pick a week for you. It opens a draft, and that is where its job ends.

What your agent does

1
Your agent calls submit_product
It passes your product URL, plus any details you want to override.
2
Nick Launches drafts the listing
We fetch the site, read the metadata and write a first pass at name, tagline and description.
3
You get a review link
The draft is saved to your account and the tool returns a link straight to it.

What you do

4
You finish it in the browser
Edit the copy, upload media, pick a plan and choose a launch week.
5
A human reviews it
Every launch is checked by a person before it goes live on the site.

The agent stops here, you take over

Tools

Six tools, all callable from any MCP client. The same logic backs the REST API, so nothing behaves differently between the two.

search_products

Find launched products in plain language.

get_product

The full listing for one product.

list_launch_directories

The vetted launch directory catalog.

check_launch_readinessNick Launches only

Audit a URL before you launch: backlink badge, duplicates, listing quality and the next free weeks.

submit_product

Scrape your site, draft the listing, hand back a review link.

get_my_launches

Status, upvotes and rank for your own launches.

REST API

Same functions, plain HTTP, for scripts and CI. The base URL is https://nicklaunches.com/api/v1/. Reads are open, writes take the bearer token you get when you approve a connection.

Method	Path	Auth	What it does
GET	/products/	None	Search and page the live catalog.
GET	/products/{slug}/	None	One full product listing.
GET	/directories/	None	The vetted launch directory catalog.
POST	/launch-readiness/	None	Audit a URL before you launch.
POST	/submissions/	Bearer	Open a launch draft from a URL.
GET	/me/launches/	Bearer	Status of your own launches.

curl

curl -s "https://nicklaunches.com/api/v1/products/?limit=5" \
  -H "Accept: application/json"

curl -s -X POST "https://nicklaunches.com/api/v1/submissions/" \
  -H "Authorization: Bearer $NICKLAUNCHES_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://yourproduct.com"}'

The full contract is published as an OpenAPI document at /api/v1/openapi.json.

Coming next

The MCP is the first of a set of builder tools, and it is expanding. Here is what is queued behind it.

First Users
An ICP audience report from your URL, with segments, pain points, subreddits and search queries.
Directory campaign planner
Pick and sequence submissions across the vetted directory catalog.
Launch analytics
Upvotes, impressions, opens, clicks and rank for your launches.
Badge management
Generate and verify your backlink badge without leaving your editor.
Changelog publishing
Ship a changelog entry to your product page from your agent.