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 分