Introduction
Search the Nick Launches catalog, audit a site before it launches, and open a launch draft, from an agent or from curl.
Nick Launches is a weekly launch directory for indie builders. Everything a maker does in the browser, browsing the catalog, checking whether a product is ready, opening a launch draft, is also reachable programmatically through an MCP server and a small REST API.
The two transports call the same functions, so nothing behaves differently depending on how you arrived. Pick MCP if you work inside Claude Code, Claude Desktop or Cursor. Pick REST if you are writing a script.
Connect an agent and run your first tool call in about two minutes.
No API keys to create. One browser click binds an agent to your account.
Config for Claude Code, Claude Desktop, Cursor and VS Code.
Seven tools, from catalog search to a preflight launch audit.
The same surface over HTTP, with an OpenAPI document.
What lands next as this grows into a builder toolkit.
What an agent can do
Reads are anonymous. Your agent can search the catalog, pull a full listing, list the launch directories we track, and run a launch readiness audit against any URL without any credentials at all.
Writes need a connection. Opening a launch draft or listing your own launches is bound to your Nick Launches account through a one time browser approval, described in Authentication.
What an agent cannot do
An agent can open a draft. It can never publish a launch.
No tool and no endpoint selects a plan, picks a launch week, creates a payment, or makes a listing public. A
submission created through the API lands in draft status and stops there. A human finishes at
/submit/plan/, and an admin reviews the listing before it goes live.
That boundary is deliberate and it is not configurable. It is what makes it safe to let an agent prepare a launch unattended.
Endpoints at a glance
| Surface | URL |
|---|---|
| MCP, Streamable HTTP | https://nicklaunches.com/api/mcp/ |
| REST base | https://nicklaunches.com/api/v1/ |
| OpenAPI document | https://nicklaunches.com/api/v1/openapi.json |
| Connection approval | https://nicklaunches.com/connect/ |
| Your connections | https://nicklaunches.com/profile/connections/ |
The part you will not find elsewhere
Most directories give you a submit endpoint. The one worth wiring into an agent first is
check_launch_readiness: give it a URL and it comes back
with a score, a list of checks, the exact backlink badge snippet to install if it is missing, whether
the product is a duplicate or eligible for a relaunch, a suggested listing, and the next launch weeks
that still have room.
Run it before you submit anything and you fix the reasons a listing gets rejected while the agent is still holding the context.