LaunchEngine.dev

io.github.Naman6019由 GitHub 账号 Naman6019 发布v0.0.3更新于 Nov 7, 2026

Find posts where someone is asking for a product like yours, scored 1-100, with reply drafts.

概览

AI 生成的概览

LaunchEngine.dev MCP 服务器可查找正在寻找类似产品的公开帖子,按 1-100 分评估购买意向,并生成供你发布的回复草稿。

可以做什么
  • 列出项目,查看积分余额与套餐
  • 查找项目的意向信号并按分数排序,可选择先执行实时扫描
  • 查看单条信号详情:帖子、作者、评分、理由与已保存草稿
  • 按咨询、直接或技术语气生成回复草稿,供你审阅后发布
  • 为项目订阅关键词,让后续扫描搜索该词
适用场景
适合做早期需求发现的创业者和市场人员,希望在 MCP 客户端内直接找到 Reddit、Hacker News 及开放网络上具有购买意向的帖子,并获得回复草稿。
运行要求
通过 npx 以 stdio 在本地运行,需要 Node 20 或更高版本。需要 LaunchEngine.dev 账号,并在 LAUNCHENGINE_DEV_API_KEY 中提供工作区 API 密钥,缺少时所有调用都会失败。LAUNCHENGINE_DEV_API_URL 可选,仅在自建 API 时设置。需要访问 LaunchEngine API 的网络。
安装前请注意
API 密钥是工作区机密,通过环境变量传入。find_intent_signals 与 draft_reply 每次调用消耗 1 积分,scan: true 还会占用工作区每日扫描额度;新工作区初始有 100 积分。draft_reply 会保存草稿,subscribe_to_keyword 会修改数据。不会自动发帖,且 Reddit 与 Hacker News 将自动化自我推广视为垃圾信息。

安装

在 SourceWeft 中

  1. 打开 控制台中的 LaunchEngine.dev,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

LaunchEngine.dev MCP server

Find public posts where someone is asking for a product like yours, while they are still choosing.

LaunchEngine.dev scans Reddit, Hacker News and the open web for posts that match your product, scores each one 1–100 for buying intent, and drafts a reply for you to edit and post. This server gives any MCP client (Claude, Cursor, VS Code, Cline, Windsurf) the same data as six tools.

Nothing is ever posted for you.

Quick start

  1. Sign up at launchengine.dev. A new workspace starts with 100 credits, no card required.
  2. Create a project for your product, then an API key under Dashboard → Agents. Keys look like le_live_....
  3. Add the server to your client (below), then ask it something.

Install

Every client runs the same command, npx -y @launchengine-dev/mcp, with your key in LAUNCHENGINE_DEV_API_KEY. Node 20 or newer is required.

Claude Desktop

Download the .mcpb bundle from the latest release and open it: Claude Desktop installs it and asks for the key.

Or add it by hand, in ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "launchengine": {      "command": "npx",      "args": ["-y", "@launchengine-dev/mcp"],      "env": { "LAUNCHENGINE_DEV_API_KEY": "le_live_..." }    }  }}

Claude Code

bash
claude mcp add launchengine \  --env LAUNCHENGINE_DEV_API_KEY=le_live_... \  -- npx -y @launchengine-dev/mcp

Cursor, Cline and Windsurf

The same mcpServers block as Claude Desktop, in:

ClientFile
Cursor~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project)
ClineCline → MCP Servers → Configure → cline_mcp_settings.json
Windsurf~/.codeium/windsurf/mcp_config.json

VS Code

.vscode/mcp.json uses servers rather than mcpServers, and can prompt for the key once and keep it out of the file:

json
{  "inputs": [    {      "type": "promptString",      "id": "launchengine-key",      "description": "LaunchEngine.dev API key (le_live_...)",      "password": true    }  ],  "servers": {    "launchengine": {      "type": "stdio",      "command": "npx",      "args": ["-y", "@launchengine-dev/mcp"],      "env": { "LAUNCHENGINE_DEV_API_KEY": "${input:launchengine-key}" }    }  }}

What to ask

  • "List my LaunchEngine projects."
  • "Find posts from the last 7 days scoring 80 or more for my project."
  • "Scan live sources now, then show me the top five." (uses a daily scan)
  • "Show me the full post for the top signal, then draft a technical reply."
  • "Start monitoring the keyword 'alternative to Mixpanel' for this project."
  • "How many credits do I have left?"

Tools

ToolCostChanges dataWhat it does
list_projectsfreenoYour projects: name, URL, description, target ICP, competitors. Start here
get_credit_balancefreenoCredit balance and plan
find_intent_signals1 creditnoScored posts for a project, highest intent first. scan: true searches live sources first
get_intent_detailsfreenoOne signal in full: post, author, score, reasons, saved draft
draft_reply1 creditsaves the draftA reply for you to review and post, in a consultative, direct or technical tone
subscribe_to_keywordfreeyesAdd a keyword for a project's scans to search

Every parameter is described in the tool schema your client receives. The full reference, generated from the same schemas, is at https://launchengine.dev/docs/agents.

The tools carry MCP annotations, so a client can ask before the two that spend credits: neither is marked read-only, even though they only read posts.

Costs and limits

  • find_intent_signals and draft_reply cost 1 credit per call. A failed call is refunded. Everything else is free.
  • scan: true also uses one of the workspace's daily scans (one a day on the free plan, shared across projects). Without it, the tool reads signals that earlier scans already found, which is fast and the usual choice.
  • Requests are rate limited per key (60 a minute by default).

Two things to know before you automate

Drafts are assistive. draft_reply returns text for a person to review and post, and it never posts. Drafts help with the poster's problem and name no product. Reddit and Hacker News both treat automated self-promotion as spam, and your account is the one that would be actioned.

Scanning is metered twice. The call costs a credit, and scan: true additionally spends the daily scan allowance.

Environment

VariableRequiredDefaultPurpose
LAUNCHENGINE_DEV_API_KEYyes—Workspace key, le_live_.... Every call fails with UNAUTHORIZED_KEY without it
LAUNCHENGINE_DEV_API_URLnohttps://launchengine.dev/apiAPI base URL. Only set this when running the API yourself

The server starts and lists its tools without a key, so a client or registry can inspect it before you have one.

Troubleshooting

It runs but nothing happens. That is expected. This is a stdio server: it prints one line to stderr, then waits for an MCP client to send JSON-RPC on stdin.

$ npx -y @launchengine-dev/mcp[launchengine-dev-mcp] v0.0.3 ready on stdio (API: https://launchengine.dev/api). Key loaded.

If you do not see that line, the install failed. --help prints usage and config snippets, and --version prints the version; both exit immediately.

UNAUTHORIZED_KEY. The key is missing, mistyped or revoked. Check its status on the Agents page, and create a new key if it was revoked.

INSUFFICIENT_CREDITS. The call costs more credits than the workspace has. get_credit_balance shows the balance; the Billing page shows plans.

RATE_LIMITED from a scan. The day's scans are used up. Read stored signals instead (scan: false), or wait for the allowance to reset.

'launchengine-dev-mcp' is not recognized. You ran npx from inside this package's own directory, where npm treats it as the package you asked for and never links its bin. Run it from anywhere else.

Links

License

MIT

来源:README.md,提交 f34fae1

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.0.3最新Oct 9, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分