Summary
Wraps the Launch Library 2 API so you can query rocket launch data without dealing with authentication or raw HTTP calls. Part of the Pipeworx gateway, which offers a streamable HTTP transport and an ask_pipeworx tool that lets you ask questions in plain English instead of constructing tool calls manually. The underlying API is free and requires no auth, making this a frictionless way to add space launch data to your Claude workflows. You can connect to just the launches endpoint or use the full Pipeworx gateway to access their entire catalog of 250+ data sources. Good fit if you're building anything that needs current or historical launch schedules without maintaining your own API client.
Plug Mailtrap into your AI workflow and let it handle the email.
Connect Mailtrap MCP →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
Make coding agent sessions - Searchable, Shareable, Vendor-neutral & Scored.
Try For Free →
Your agent targets a perfect 10 Code Health score. Deterministic. Every commit.
Try For Free →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
belt cli automatically finds the best tools and skills for your agent. image, video, music, tts...
one prompt install →mcp-launches
Launches MCP — wraps Launch Library 2 API (ll.thespacedevs.com)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ 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.):
{
"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 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
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
Featured
Plug Mailtrap into your AI workflow and let it handle the email.
Connect Mailtrap MCP →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →Make coding agent sessions - Searchable, Shareable, Vendor-neutral & Scored.
Try For Free →Your agent targets a perfect 10 Code Health score. Deterministic. Every commit.
Try For Free →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →belt cli automatically finds the best tools and skills for your agent. image, video, music, tts...
one prompt install →