Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Find posts where someone is asking for a product like yours, scored 1-100, with reply drafts.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
LAUNCHENGINE_DEV_API_KEY, LAUNCHENGINE_DEV_API_URL标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"launchengine-dev": {
"command": "npx",
"args": [
"-y",
"@launchengine-dev/mcp"
],
"env": {
"LAUNCHENGINE_DEV_API_KEY": "your-value",
"LAUNCHENGINE_DEV_API_URL": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add launchengine-dev --env LAUNCHENGINE_DEV_API_KEY=your-value --env LAUNCHENGINE_DEV_API_URL=your-value -- npx -y @launchengine-dev/mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"launchengine-dev": {
"command": "npx",
"args": [
"-y",
"@launchengine-dev/mcp"
],
"env": {
"LAUNCHENGINE_DEV_API_KEY": "your-value",
"LAUNCHENGINE_DEV_API_URL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"launchengine-dev": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@launchengine-dev/mcp"
],
"env": {
"LAUNCHENGINE_DEV_API_KEY": "your-value",
"LAUNCHENGINE_DEV_API_URL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
LAUNCHENGINE_DEV_API_URL env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 Naman6019 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:LAUNCHENGINE_DEV_API_KEY
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.0.3)于29天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, ProAgentStore
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP-first control plane for ProAgentStore agents and private instances.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
le_live_....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.
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):
{
"mcpServers": { "launchengine": { "command": "npx", "args": ["-y", "@launchengine-dev/mcp"], "env": { "LAUNCHENGINE_DEV_API_KEY": "le_live_..." } } } }
claude mcp add launchengine \
--env LAUNCHENGINE_DEV_API_KEY=le_live_... \ -- npx -y @launchengine-dev/mcp
The same mcpServers block as Claude Desktop, in:
| Client | File |
|---|---|
| Cursor | ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project) |
| Cline | Cline → MCP Servers → Configure → cline_mcp_settings.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
.vscode/mcp.json uses servers rather than mcpServers, and can prompt for the key once and keep it out of the file:
{
"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}" } } } }
| Tool | Cost | Changes data | What it does |
|---|---|---|---|
list_projects | free | no | Your projects: name, URL, description, target ICP, competitors. Start here |
get_credit_balance | free | no | Credit balance and plan |
find_intent_signals | 1 credit | no | Scored posts for a project, highest intent first. scan: true searches live sources first |
get_intent_details | free | no | One signal in full: post, author, score, reasons, saved draft |
draft_reply | 1 credit | saves the draft | A reply for you to review and post, in a consultative, direct or technical tone |
subscribe_to_keyword | free | yes | Add 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.
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.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.
| Variable | Required | Default | Purpose |
|---|---|---|---|
LAUNCHENGINE_DEV_API_KEY | yes | — | Workspace key, le_live_.... Every call fails with UNAUTHORIZED_KEY without it |
LAUNCHENGINE_DEV_API_URL | no | https://launchengine.dev/api | API 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.
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.
@launchengine-dev/mcpMIT