English Français العربية

Launches

Official registry Other

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

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http launches 'https://gateway.pipeworx.io/launches/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "launches": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/launches/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-launches
  2. Tools
  3. Quick Start
  4. No MCP client? Call it over HTTP
  5. Standalone (no gateway account)
  6. Using with ask_pipeworx
  7. More
  8. License

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

ToolDescription
get_upcoming_launchesFetch 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_launchesFetch 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_launchGet full details for a specific launch by ID. Returns name, time, status, pad, rocket, mission, orbit info, video links, and mission patches.
search_launchesSearch 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 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

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

Frequently asked questions

What is Launches?

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

How do I install Launches?

It runs as a remote server. In Claude Code: claude mcp add --transport http launches 'https://gateway.pipeworx.io/launches/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Launches need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Launches open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Launches?

It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.