For AI assistants

QikLaunch MCP server

Connect QikLaunch to Claude, ChatGPT, Cursor, VS Code or any app that supports the Model Context Protocol (MCP). Then just ask: "find new invoicing tools on QikLaunch", "what is winning this week?" or "how do I launch my app there?".

Introduction

MCP is the open standard AI apps use to call outside tools. Add one URL and your assistant can search every live launch, read the weekly board and past winners, and explain the launch plans - with links back to each product's QikLaunch page.

Server URL
https://www.qiklaunch.com/mcp
Transport
Streamable HTTP
Sign-in
None needed (your launches: token)

Claude

Claude app or claude.ai: open Settings → Connectors → Add custom connector, name it QikLaunch and paste the server URL.

Server URL
https://www.qiklaunch.com/mcp

Claude Code: run this once in your terminal.

Terminal
claude mcp add --transport http qiklaunch https://www.qiklaunch.com/mcp

ChatGPT

In ChatGPT's settings, open the connectors (apps) section, turn on developer mode if your plan asks for it, create a new connector and paste the server URL. Menu names change from time to time - look for "Connectors" or "Apps".

Server URL
https://www.qiklaunch.com/mcp

Cursor

Add QikLaunch to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project), then turn it on under Settings → MCP.

mcp.json
{
  "mcpServers": {
    "qiklaunch": {
      "url": "https://www.qiklaunch.com/mcp"
    }
  }
}

VS Code

For GitHub Copilot agent mode, add this to .vscode/mcp.json in your project, or run "MCP: Add Server" from the command palette.

.vscode/mcp.json
{
  "servers": {
    "qiklaunch": {
      "type": "http",
      "url": "https://www.qiklaunch.com/mcp"
    }
  }
}

Other AI apps

Windsurf, Zed, Cline, Goose and other MCP clients: add a remote (HTTP) server with the URL above. Apps that only run local servers can bridge to it with mcp-remote:

Local bridge (stdio)
{
  "mcpServers": {
    "qiklaunch": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.qiklaunch.com/mcp"]
    }
  }
}

Tools

Your assistant picks the right tool on its own. Public tools only read live launches; nothing in review, scheduled for later or demo data is ever returned.

search_launches

Public Read-only

Search products launched on QikLaunch by keyword, category or tag. Returns live launches with their QikLaunch page, website, category, launch week and votes. Use it to find tools for a need ("invoicing for freelancers") or to check whether a product has launched here.

weekly_board

Public Read-only

The QikLaunch weekly launch board in ranking order: this week by default, or a past week. Each week runs Monday 00:00 to Sunday 23:59 UTC. Paid Boost/Spotlight launches are pinned at the top for a few days; only free launches can win the weekly top 3.

get_product

Public Read-only

Full details of one product launched on QikLaunch: description, tags, pricing model, maker, launch week, votes, comments, logo and screenshots. Pass the product slug, its QikLaunch page URL, or its name.

weekly_winners

Public Read-only

The top 3 free launches ("Qik of the Week") for each recently completed QikLaunch week, newest first.

list_categories

Public Read-only

Every QikLaunch category (groups and their sub-categories) with its slug, page URL and number of live launches. Use the slugs with search_launches or submit_launch.

launch_plans

Public Read-only

How to launch a product on QikLaunch: the Free, Boost and Spotlight plans with current prices and what each includes, plus the link to submit. Use it when someone asks how to launch, what it costs, or how the weekly board works.

my_account

Your token Read-only

Your QikLaunch account (personal token): how many launches you have, free launches left, the next open free launch week and the plans. Call this before submit_my_launch.

my_launches

Your token Read-only

Your own QikLaunch launches (personal token): status (in_review, awaiting_payment, scheduled, live, rejected), plan, launch week, page link and stats (votes, comments, visits sent, dofollow). Pass an id for one launch with its description.

submit_my_launch

Your token

Launch your own product on QikLaunch (personal token). It is submitted for review in your account, exactly like the website form: free launches get the next open free week, paid plans (boost, spotlight) return a checkout_url to pay. Ask the user to confirm the details before calling.

get_my_badge

Your token Read-only

The "Launched on QikLaunch" badge code for one of your launches (personal token), as HTML and as React/JSX. Add it to the footer of the product website (find the shared footer/layout component in the repo), ship it, then call verify_my_badge. Free launches keep their dofollow link only while the badge is live.

verify_my_badge

Your token

Check the live product website for the QikLaunch badge right now (personal token). Call it after the badge change is deployed; a found badge turns the launch link dofollow. At most 6 checks a minute.

partner_account

Partner token Read-only

Your partner deal (monthly quota and what is left, plans and partner prices, billing) plus the categories and launch weeks you can submit to. Call this before submit_launch.

submit_launch

Partner token

Submit a product to QikLaunch for one of your customers, exactly like POST /api/v1/submissions. It goes into review; the maker gets an email (with an account if they are new). Counts against your monthly quota. Returns the submission id, status, launch week and, for paid plans billed by card, a checkout_url the maker must pay.

submission_status

Partner token Read-only

The current status of a launch you submitted (awaiting_payment, in_review, scheduled, live or rejected), its plan, launch week and public URL.

Your launches (personal token)

Makers can let their AI assistant see and submit their own launches. Create a token in Settings → API tokens and add it as a header. You then also get my_account, my_launches, submit_my_launch, get_my_badge and verify_my_badge.

Launch from your editor (Claude Code, Cursor, Codex)

  1. Open your project and ask: "launch this product on QikLaunch".
  2. The agent reads your README and package.json and drafts the listing. You approve or edit it.
  3. It submits with submit_my_launch, adds the badge to your site footer with get_my_badge, and after you deploy checks it with verify_my_badge.
  4. You get your launch page link: it goes live in your launch week once approved.
Cursor / VS Code with your token
{
  "mcpServers": {
    "qiklaunch": {
      "url": "https://www.qiklaunch.com/mcp",
      "headers": {
        "Authorization": "Bearer ql_usr_YOUR_TOKEN"
      }
    }
  }
}
Claude Code with your token
claude mcp add --transport http qiklaunch https://www.qiklaunch.com/mcp --header "Authorization: Bearer ql_usr_YOUR_TOKEN"

The token acts as you: keep it private, give each app its own token, and revoke any you no longer use.

REST API

The same personal token works with a small JSON API for scripts, Zapier or n8n. Base URL: https://www.qiklaunch.com/api/v1/me, 60 requests per minute.

GET /api/v1/me Your account, free launches left, next open free week
GET /api/v1/me/products Your launches with status, week and stats
GET /api/v1/me/products/{id} One launch with its description
POST /api/v1/me/products Submit a launch (same fields as submit_my_launch)
GET /api/v1/me/products/{id}/badge Badge code for your footer (HTML and JSX)
POST /api/v1/me/products/{id}/badge/verify Check your site for the badge now
Example
curl https://www.qiklaunch.com/api/v1/me/products \
  -H "Authorization: Bearer ql_usr_YOUR_TOKEN" \
  -H "Accept: application/json"

Partners

Directories, agencies and launch platforms with a Partner API token can also submit launches and track them from their AI tools. Send the token as a header; the partner tools then appear automatically. They use the same quota, plans and billing as the REST API.

Cursor / VS Code with a partner token
{
  "mcpServers": {
    "qiklaunch": {
      "url": "https://www.qiklaunch.com/mcp",
      "headers": {
        "Authorization": "Bearer ql_pat_YOUR_TOKEN"
      }
    }
  }
}

Keep your token private: put it only in your own local config, never in a shared repository.

Limits and privacy

  • 60 requests per minute per IP address (or per partner token).
  • Public tools return only what is already public on qiklaunch.com: no emails, no private data.
  • Makers launch their own products on the website: submit your product.
  • Questions or ideas for more tools? Contact us.