# Noonlaunch MCP server

Launch a product on Noonlaunch, search its directory and weekly winners, and find 333 launch sites.

## At a glance

Noonlaunch is an MCP server in the Web & Search category. It is hosted remotely and connects over HTTP, and declares no required credentials. It exposes 10 tools, including search-directory, get-product and get-weekly-winners. It scores B (73/100) on the MCP Skills Hub health score as of Oct 28, 2026.

## Install

### How to install Noonlaunch in Claude Code

1. Add the server

```bash
claude mcp add --transport http noonlaunch https://noonlaunch.com/mcp
```

2. Verify it's connected

```bash
claude mcp list
```

3. Sharing it with your team?

   Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

4. Use it in a session

   Ask Claude to use the tools this server exposes (e.g. search-directory, get-product, get-weekly-winners). It discovers them automatically.

### How to install Noonlaunch in Claude Desktop

1. Open your MCP config

   macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

2. Add this server

```json
{
  "mcpServers": {
    "noonlaunch": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://noonlaunch.com/mcp"
      ]
    }
  }
}
```

3. Why the wrapper?

   This is a remote (HTTP) server and Claude Desktop only launches local processes, so mcp-remote proxies the connection. It will open a browser window if the server needs OAuth.

4. Restart Claude Desktop

   The tools appear under the 🔌 menu once the app reloads.

### How to install Noonlaunch in Cursor

1. Create / edit .cursor/mcp.json in your project

```json
{
  "mcpServers": {
    "noonlaunch": {
      "url": "https://noonlaunch.com/mcp"
    }
  }
}
```

2. Enable it

   Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

### How to install Noonlaunch in Codex CLI

1. Add to ~/.codex/config.toml

```toml
[mcp_servers.noonlaunch]
command = "npx"
args = ["-y", "mcp-remote", "https://noonlaunch.com/mcp"]
```

2. Why the wrapper?

   Codex runs MCP servers as local processes, so mcp-remote bridges this HTTP endpoint to stdio.

3. Run Codex

   Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

### How to install Noonlaunch in Windsurf

1. Edit ~/.codeium/windsurf/mcp_config.json

```json
{
  "mcpServers": {
    "noonlaunch": {
      "serverUrl": "https://noonlaunch.com/mcp"
    }
  }
}
```

2. Reload

   Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

### How to install Noonlaunch in Cline

1. Open Cline → MCP Servers → Configure

   Adds to cline_mcp_settings.json.

2. Add the server

```json
{
  "mcpServers": {
    "noonlaunch": {
      "type": "streamableHttp",
      "url": "https://noonlaunch.com/mcp"
    }
  }
}
```

### How to install Noonlaunch in VS Code

1. Create .vscode/mcp.json

```json
{
  "servers": {
    "noonlaunch": {
      "type": "http",
      "url": "https://noonlaunch.com/mcp"
    }
  }
}
```

2. Start it

   VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

## Tools

- `search-directory` — Search the Noonlaunch product directory. Returns approved products matching the query, ordered by community votes, with links to their Noonlaunch product pages.
- `get-product` — Get full public details of one Noonlaunch product by its slug (the last part of its noonlaunch.com/product/... URL).
- `get-weekly-winners` — Get the Noonlaunch launch board for a week: the top-voted free launches, with the top 3 marked as winners. weeks_ago 0 is the current (still running) week, 1 is the last completed week.
- `list-launch-directories` — Browse Noonlaunch's curated list of 333 startup launch directories and communities where founders can submit a product. Filterable by category, cost and minimum domain authority.
- `get-plans` — What it costs to launch on Noonlaunch, and what each plan includes. Use this to answer a pricing question on its own. To actually submit a product, call check_product instead: which plans apply depends on the site, because relaunching one that is already listed needs a paid plan.
- `check-product` — Check whether a product can be submitted to Noonlaunch, and get the plans, categories and launch weeks available for it. Always call this first, and always ask the person for their live public website URL rather than guessing it from their code.
- `submit-product` — Submit a product to Noonlaunch. Nothing is published by this call. It returns a claim link to give the person straight away, and for free launches the badge snippet to install. Call check_product first.
- `verify-badge` — Check that the Noonlaunch badge is installed on the product site and publish the listing if it is. Only for free launches, and only after the person has deployed the change. Paid listings are published by payment instead, so use check_status for those.
- `check-status` — Where a submission stands: whether it has been claimed, paid for, verified and published. This is the only way to find out whether a payment has landed. Poll it rather than assuming.
- `report-badge-problem` — Report that the badge check is wrong: the badge is installed and visible but we cannot find it. Only use this after verify_badge has failed twice and you have confirmed the badge really is live on the page. A person reviews it within 24 hours.

Source repository: https://github.com/mukund1158/noonlaunch-mcp

---

Source: https://mcp-skills-hub.vercel.app/mcps/com-noonlaunch-mcp · MCP Skills Hub · data as of 2026-10-28T12:31:05Z