
Wraps the Spaceflight News API v4 to pull space industry news, articles, and updates into Claude. Part of the Pipeworx gateway, which offers a plain English query interface through ask_pipeworx instead of making you call tools directly. Free to use, no authentication required. If you need space news for research, briefings, or keeping an AI assistant current on launches and missions, this gives you a structured feed without setting up API keys. You can use the standalone spacenews endpoint or connect to the full Pipeworx gateway for access to 250+ other data sources alongside it.
Spacenews MCP — wraps the Spaceflight News API v4 (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_articles | Fetch the latest spaceflight news articles sorted by publication date. Returns title, summary, URL, image, and source. |
search_articles | Search spaceflight news articles by keyword. Returns matching articles with title, summary, URL, and publication date. |
get_blogs | Fetch the latest spaceflight blog posts sorted by publication date. Returns title, summary, URL, image, and source. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"spacenews": {
"url": "https://gateway.pipeworx.io/spacenews/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/spacenews/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.
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 Spacenews data" })
The gateway picks the right tool and fills the arguments automatically.
MIT