火箭发射数据查询MCP服务

为AI代理提供火箭发射数据查询能力的MCP服务,封装Launch Library 2 API,支持获取即将发射、历史发射、任务详情及关键词搜索,适用于航天动态追踪与自动化数据分析场景。

  • by pipeworx-io
  • TypeScript
  • 本地部署
  • 更新于
在 GitHub 查看 pipeworx-io/mcp-launches

使用说明

mcp-launches

Launches MCP — wraps Launch Library 2 API (ll.thespacedevs.com)

Part of Pipeworx — an MCP gateway connecting AI agents to 1882+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

Tool Description
get_upcoming_launches Fetch the next scheduled rocket launches from Launch Library 2. Returns launch name, NET (no-earlier-than) time, status, launch pad, rocket type, and mission description. Default 10 results.
get_past_launches Fetch rocket launches that have already flown, sorted newest-first, from Launch Library 2. launches holds only those with a confirmed outcome — successful, failed or partial failure — so counting them answers "how many launches happened". A launch whose scheduled time has passed but whose outcome upstream has not yet confirmed is reported separately in unconfirmed with its current status, rather than being counted as flown. Use since and until to bound a window (ISO dates). Returns launch name, time, status, pad, rocket type, and mission description. Default 10 results.
get_launch Get full details for a specific launch by ID. Returns name, time, status, pad, rocket, mission, orbit info, video links, and mission patches.
search_launches Search launches by keyword (rocket name, mission, agency). Returns matching launches with name, time, status, pad, rocket, and mission.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "launches": {
      "url": "https://gateway.pipeworx.io/launches/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/launches/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1882+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/get_upcoming_launches \
  -H 'Content-Type: application/json' \
  -d '{"limit":10}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/get_upcoming_launches. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "launches": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-launches"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-launches

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Launches data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT