project
Your launch projects — name, URL, tagline, description, category, audience, pricing — used to personalize the checklist and build submission copy.
Free (no plan gate, no credits). You start a project and checklists, scores, and submission copy hang under it. The active project is what launch tools read by default.
MCP Tool
- Tool name:
startupkit_project - Actions:
list·get(default) ·create·update·activate·delete - Input:
action,project(id or name — defaults to the active project forget/update, required foractivate/delete), plus any ofproduct_name,product_url,tagline,description,category,audience,pricing_model - Output: The project (or list of projects)
CLI
startupkit projects # list all projects
startupkit projects --get <id-or-name> # show one
startupkit projects --create --name Acme --category saas --audience b2b
startupkit projects --update Acme --tagline "Ship faster"
startupkit projects --activate Acme
startupkit projects --delete AcmeAPI
curl -X POST https://api.startupkit.com/v1/projects \
-H "Authorization: Bearer $STARTUPKIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"product_name":"Acme","product_url":"https://acme.com","category":"saas","audience":"b2b","pricing_model":"freemium"}'GET /v1/projects lists, GET/PATCH/DELETE /v1/projects/:id manage one (the id also accepts a unique project name). The legacy GET/PUT /v1/project alias reads/writes the active project.
Categories: saas, ai, developer, mobile, marketplace, consumer, other. Audience: b2b, b2c, both. Pricing: free, freemium, paid, trial.