Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
MCP server exposing live Helldivers 2 galactic war data.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.avengersofsuperearth.com/mcp打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"helldivers2": {
"command": "npx",
"args": [
"-y",
"helldivers2-mcp"
]
}
}
}在终端中运行这条命令
claude mcp add --transport http helldivers2 https://mcp.avengersofsuperearth.com/mcpclaude mcp add helldivers2 -- npx -y helldivers2-mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"helldivers2": {
"url": "https://mcp.avengersofsuperearth.com/mcp"
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"helldivers2": {
"command": "npx",
"args": [
"-y",
"helldivers2-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"helldivers2": {
"type": "http",
"url": "https://mcp.avengersofsuperearth.com/mcp"
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"helldivers2": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"helldivers2-mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.avengersofsuperearth.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 xerno42 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(1.0.2)于42天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Georgia MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
An MCP server for Georgian public data, read from the organizations that publish it.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A stateless Model Context Protocol (MCP) server that exposes live Helldivers 2 galactic war data to LLMs.
Data is sourced from the community API at api.helldivers2.dev.
| Registry | Package |
|---|---|
| npm | helldivers2-mcp |
| Docker Hub | xerno42/helldivers2-mcp |
| GitHub Container Registry | ghcr.io/xerno42/helldivers2-mcp |
| MCP Registry | io.github.xerno42/helldivers2-mcp |
| Tool | Description |
|---|---|
get_war_status | Galaxy-wide war statistics (kills by faction, missions won/lost, accuracy, deaths, impact multiplier) and active planets with owner, player count, active events, attack vectors, and region health |
get_assignments | Active Major Orders with title, briefing, decoded task list (faction, difficulty, target planet), current progress numbers, reward type and amount, and time until expiry |
get_all_planets | Full planet list with IDs, names, and sectors |
get_planet_details | Detailed per-planet info: biome, hazards, initial/current owner, health, waypoints, active events, full combat statistics, attacking planets, and regions (up to 5 planets per call) |
get_dispatches | In-game dispatch feed — High Command broadcasts with published date (relative time) and message text; optional limit parameter (default 20, max 50) |
get_steam_news | Steam news for Helldivers 2 with title, URL, publish date (relative time), and full article content; optional limit parameter (default 10, max 30) |
get_space_station_details | DSS details: current host planet (full planet info), time until next election, and active tactical actions with name, description, status, planet effects, and resource costs |
X-Super-Contact header (required by the upstream API)cp .env.example .env # set X_SUPER_CONTACT=your@email.com
npm install npm run dev # hot-reload via tsx watch on :3000
npm run build # tsc → dist/
npm run start
Image is available on Docker Hub and GitHub Container Registry.
docker pull xerno42/helldivers2-mcp # pull from Docker Hub
docker pull ghcr.io/xerno42/helldivers2-mcp # pull from GHCR
docker build -t helldivers2-mcp . # build locally
#then run with: docker run -p 3000:3000 -e X_SUPER_CONTACT=your@email.com helldivers2-mcp
All configuration is via environment variables.
| Variable | Default | Description |
|---|---|---|
X_SUPER_CONTACT | *(required)* | Forwarded as X-Super-Contact to the upstream API per their usage guidelines |
PORT | 3000 | HTTP port to listen on |
BIND_HOST | 127.0.0.1 | Interface to bind (0.0.0.0 for Docker/containers) |
MCP_ALLOWED_ORIGINS | *(unset)* | Comma-separated list of allowed browser Origin headers. Unset means browser-originated requests are blocked; server-to-server calls (no Origin header) are always allowed |
MCP_RATE_LIMIT_PER_MIN | 60 | Sustained request rate limit (requests per minute) |
MCP_RATE_LIMIT_BURST | = MCP_RATE_LIMIT_PER_MIN | Burst capacity for the token-bucket rate limiter |
| Method | Path | Description |
|---|---|---|
POST | /mcp | MCP Streamable HTTP transport endpoint |
GET | /health | Liveness check — returns { "ok": true } |
The server uses the stateless Streamable HTTP transport. Each POST /mcp request creates a fresh McpServer + transport pair, handles the request, then tears them down. There is no session state.
Call the MCP server directly over HTTP using the Streamable HTTP transport. Each request is a JSON-RPC tools/call message sent to POST /mcp.
Using the official MCP TypeScript SDK:
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";
const client = new Client({ name: "my-app", version: "1.0.0" });
const transport = new StreamableHTTPClientTransport( new URL("https://mcp.avengersofsuperearth.com/mcp") );
await client.connect(transport);
// List available tools const { tools } = await client.listTools(); console.log(tools.map((t) => t.name));
// Get current war status const warStatus = await client.callTool({ name: "get_war_status", arguments: {}, }); console.log(warStatus.content[0].text);
// Get details for specific planets by index (up to 5) const planets = await client.callTool({ name: "get_planet_details", arguments: { planetindices: [57, 153] }, }); console.log(planets.content[0].text);
await client.close();
Without the SDK — raw JSON-RPC over fetch:
async function callTool(name: string, args: Record<string, unknown> = {}) {
const res = await fetch("https://mcp.avengersofsuperearth.com/mcp", { method: "POST", headers: { "Content-Type": "application/json", "Accept": "application/json, text/event-stream", }, body: JSON.stringify({ jsonrpc: "2.0", id: 1, method: "tools/call", params: { name, arguments: args }, }), }); const text = await res.text(); // The response is an SSE frame ("event: message\ndata: {json}\n\n"); // concatenate its data line(s) to recover the JSON-RPC payload. const json = text .split("\n") .filter((line) => line.startsWith("data:")) .map((line) => line.slice(5).trim()) .join(""); const data = JSON.parse(json); return data.result.content[0].text; }
const status = await callTool("get_war_status"); const assignments = await callTool("get_assignments"); const dispatches = await callTool("get_dispatches", { limit: 5 }); const planets = await callTool("get_planet_details", { planetindices: [57, 153] });
Using the official MCP Python SDK:
import asyncio
from mcp import ClientSession from mcp.client.streamable_http import streamablehttp_client
async def main(): async with streamablehttp_client("https://mcp.avengersofsuperearth.com/mcp") as (read, write, _): async with ClientSession(read, write) as session: await session.initialize()
tools = await session.list_tools() print([t.name for t in tools.tools])
result = await session.call_tool("get_war_status", {}) print(result.content[0].text)
result = await session.call_tool( "get_planet_details", {"planetindices": [57, 153]}, ) print(result.content[0].text)
asyncio.run(main())
Without the SDK — raw JSON-RPC over httpx:
import httpx
MCP_URL = "https://mcp.avengersofsuperearth.com/mcp"
def call_tool(name: str, arguments: dict = {}) -> str: payload = { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": name, "arguments": arguments}, } headers = { "Content-Type": "application/json", "Accept": "application/json, text/event-stream", } response = httpx.post(MCP_URL, json=payload, headers=headers) response.raise_for_status() import json
text = "".join( line[5:].strip() for line in response.text.splitlines() if line.startswith("data:") ) return json.loads(text)"result"0
status = call_tool("get_war_status") assignments = call_tool("get_assignments") planets = call_tool("get_planet_details", {"planetindices": [57, 153]})
A public instance is available at https://mcp.avengersofsuperearth.com/mcp. No setup required — just add it to your claude_desktop_config.json:
{
"mcpServers": { "helldivers2": { "url": "https://mcp.avengersofsuperearth.com/mcp" } } }
{
"mcpServers": { "helldivers2": { "command": "node", "args": ["/path/to/helldivers2-mcp/dist/index.js"], "env": { "X_SUPER_CONTACT": "your@email.com" } } } }
{
"mcpServers": { "helldivers2": { "url": "http://localhost:3000/mcp" } } }
npm run test # Jest (ESM mode)
npm run test:watch npm run test:coverage npm run lint # ESLint
Run a single test file:
npm run test src/__tests__/tools.war.test.ts
src/tools/your-tool.ts and export a Tool object with .definition and .handler.TOOLS array in src/index.ts.textResponse(...) on success or errorResponse(...) on failure — never throw from a handler.hd2Fetch (in-memory 2-minute cache + rate-limit-aware queue).MIT