Launches

Launches MCP — wraps Launch Library 2 API (ll.thespacedevs.com, free, no auth)

Install Launches

Pick your client, then add it in one click or paste the config.

STDIONode.js

~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

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

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y @pipeworx/mcp-launches

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 5d ago.

Overview

Tools4

What Launches lets your agent do. Expand a tool for its parameters.

Self-reported~207 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @pipeworx/mcp-launches (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads421Package downloads in the last 30 days.

Last commit26d agoMost recent push to the default branch.

Install checkInconclusiveStarted but did not complete the MCP handshake in our test.

Tools exposed4Callable tools this server registers over MCP.

Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

From the project README

mcp-launches

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

Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.

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.):

config.json

{
  "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:

config.json

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

Both URLs reach the same gateway and the same 1683+ 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

Terminal

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:

config.json

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

Or run it directly to confirm it starts:

Terminal

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:

Code

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

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

License

MIT

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Launches

launches is an MCP server that wraps the free Launch Library 2 API at ll.thespacedevs.com without requiring authentication. It provides tools to retrieve upcoming launches, confirmed past launches, individual launch details, and keyword searches across rocket, mission, and agency data, including schedules, statuses, pads, rockets, and mission descriptions.

Use the get_upcoming_launches tool to fetch the next scheduled rocket launches. Results include the launch name, NET time, status, launch pad, rocket type, and mission description; the default result count is 10.

Use get_past_launches to retrieve confirmed rocket launches, sorted newest-first. Its launches results include successful, failed, and partial-failure outcomes, while scheduled launches whose outcomes are not yet confirmed appear separately in unconfirmed; since and until ISO date filters can bound the window.

Use get_launch with a launch ID to retrieve full details, including the launch time, status, pad, rocket, mission, orbit information, video links, and mission patches.

Use search_launches with a keyword to find matching launches by rocket name, mission, or agency. Results include the launch name, time, status, pad, rocket, and mission.

Related MCP servers

All in Aerospace & Astrodynamics All alternatives

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/launches?style=directory)](https://allmcps.com/mcp/launches)

HTML Embed

<a href="https://allmcps.com/mcp/launches"><img src="https://allmcps.com/api/badge/launches?style=directory" alt="Launches on AllMCPs" /></a>

At a glance

Category: Aerospace & Astrodynamics
Transport: STDIO
Runtime: Node.js
Last updated: Oct 12, 2026

GitHub stars0

Last commit26d ago

npm / month421

53Quality signal: Good · 53/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools24/30

Adoption & activity6/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

Own this project?

This listing is pre-filled from public sources. Claim it via your GitHub README, a site badge, or DNS TXT to edit it and earn the Verified badge.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically.

Claim this listing

Install Launches

Supply-chain signal

Adoption & maintenance

From the project README

mcp-launches

Tools

Quick Start

What this endpoint actually serves

No MCP client? Call it over HTTP

Standalone (no gateway account)

Using with ask_pipeworx

More

License

Frequently Asked Questions about Launches

What is the launches MCP server?

How can I get upcoming rocket launches?

How do I find past launches and count launches that actually happened?

How do I retrieve details for a specific launch?

How can I search launches by rocket, mission, or agency?

AllMCPs Directory Badge