# LaunchSignal MCP server

> Browse approved product launches and submit new products for review on the LaunchSignal directory.

- Listing: https://mcp.tc/i/launchsignal
- Connect: use the server's own URL `https://launchsignal.ai/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Marketing & SEO](https://mcp.tc/c/marketing-seo)
- Vendor: LaunchSignal
- Homepage: <https://launchsignal.ai/>

## About

LaunchSignal is a free product-launch listing platform. This server lets an assistant list approved products, fetch one by slug, submit a new product for moderation, apply a listing boost, and verify a backlink badge for a Verified mark and free Priority placement.

It runs as a hosted Streamable HTTP endpoint at https://launchsignal.ai/mcp. No sign-in or API key is needed. Boosts run in demo mode without charge unless the operator enables Stripe payments, in which case a checkout URL is returned.

## What it can do

- List approved product launches, newest or boosted first
- Filter listings by category with cursor pagination
- Fetch an approved product by slug
- Submit a product for moderation
- Apply a Priority or Featured boost to a listing
- Verify a LaunchSignal backlink on a product homepage

## Tools (5)

- `submit_product`: Submit a new product listing for moderation with name, URL, description, category, email and logo.
- `list_products`: List approved products, newest or boosted first, with optional limit, cursor and category.
- `get_product`: Fetch an approved product by slug; returns not\_found if missing or not approved.
- `boost_product`: Apply a Priority or Featured boost to an approved listing; may return a Stripe checkout URL.
- `verify_backlink`: Check for a LaunchSignal link on the product homepage to grant a Verified mark and 7 free Priority…

## Example prompts

- "List the newest AI products on LaunchSignal."
- "Show me the LaunchSignal listing for the product with slug elmren-voice."
- "Submit my product Acme Notes at https://acme.example to LaunchSignal as Productivity."
- "Verify the LaunchSignal backlink for my product slug acme-notes."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http launchsignal https://launchsignal.ai/mcp
```

2. Start Claude Code and type `/mcp`. **launchsignal** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **LaunchSignal** and paste this URL:

```url
https://launchsignal.ai/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=LaunchSignal&connectorUrl=https%3A%2F%2Flaunchsignal.ai%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://launchsignal.ai/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://launchsignal.ai/mcp` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=launchsignal&config=eyJ1cmwiOiJodHRwczovL2xhdW5jaHNpZ25hbC5haS9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "launchsignal": {
      "url": "https://launchsignal.ai/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=launchsignal&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Flaunchsignal.ai%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"launchsignal","type":"http","url":"https://launchsignal.ai/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "launchsignal": {
      "type": "http",
      "url": "https://launchsignal.ai/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "launchsignal": {
      "serverUrl": "https://launchsignal.ai/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add launchsignal --url https://launchsignal.ai/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.launchsignal]
url = "https://launchsignal.ai/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http launchsignal https://launchsignal.ai/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "launchsignal": {
      "type": "http",
      "url": "https://launchsignal.ai/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://launchsignal.ai/mcp`.

## Recent changes

- 2026-11-16 02:57 UTC: 2 tools changed. Source: automatic check. Changed: submit\_product, verify\_backlink.
- 2026-11-03 08:51 UTC: 1 tool changed. Source: automatic check. Changed: submit\_product.
- 2026-10-23 01:38 UTC: 1 tool changed. Source: automatic check. Changed: boost\_product.
- 2026-10-18 10:38 UTC: 2 tools changed. Source: automatic check. Changed: get\_product, submit\_product.
- 2026-10-15 04:20 UTC: Tracking started: 5 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/launchsignal#history (Atom feed: https://mcp.tc/i/launchsignal/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.1.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-10-15
- Updated: 2026-11-16

---
Source: https://mcp.tc/i/launchsignal (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
