Spacex

What the spacex MCP server does

The spacex MCP server gives MCP-compatible agents access to SpaceX launch, vehicle, crew, and satellite information. Its launch data comes from SpaceX API v4, described by the project as a revival of the discontinued SpaceX API. Starlink records come from the public CelesTrak catalog.

The available data includes the latest launch, the next scheduled launch, recent completed launches, rocket configurations, astronauts associated with Crew Dragon missions, and Starlink orbital elements. Launch responses can include mission descriptions, rocket and launch-pad details, status information, and links to webcast, article, or Wikipedia pages.

How it works

The project can be used through the Pipeworx gateway or as a local package. The hosted pack endpoint is https://gateway.pipeworx.io/spacex/mcp. A full gateway connection is also available at https://gateway.pipeworx.io/mcp; both endpoints reach the same gateway and data sources, but the pack endpoint lists this pack's tools directly.

A gateway connection includes the SpaceX tools plus shared Pipeworx meta-tools. These include discovery, search, memory, and ask_pipeworx, which can route a natural-language request to tools across the wider catalog. The standalone package exposes only the SpaceX tools and does not include those gateway features.

The server also supports direct HTTP calls through endpoints such as POST https://gateway.pipeworx.io/v1/tools/get_latest_launch with an empty JSON object.

Setup and configuration

For a hosted MCP connection, add the pack endpoint to an MCP client configuration:

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

For local stdio use, configure the package command instead:

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

Running npx -y @pipeworx/mcp-spacex starts the local server directly. The standalone mode requires no Pipeworx account and communicates through stdin and stdout. No environment variables or credentials are documented as required.

Tools and capabilities

The spacex MCP server includes these tools:

• get_latest_launch returns the most recent launch, including its UTC date, success state, mission details, rocket, launch pad, and available media links.
• get_next_launch returns the upcoming launch, with a scheduled UTC date that may be marked as to be determined, plus mission, rocket, and pad information.
• get_past_launches lists recent launches in reverse chronological order with dates, statuses, and success values.
• get_rockets lists configurations such as Falcon 1, Falcon 9, Falcon Heavy, and Starship, with reusability, maiden-flight, cost, launch-count, success-count, and success-rate fields.
• get_crew lists astronauts who have flown or are assigned to Crew Dragon missions, including agency, role, mission, flight status, Wikipedia link, and image URL.
• get_starlink returns live Starlink satellite records from CelesTrak, ordered by orbital-element epoch and including identifiers, epoch, mean motion, inclination, and eccentricity.

Limitations and notes

Scheduled launch dates can be undecided. Crew data is derived from recent crewed SpaceX launches rather than presented as a general astronaut database. The gateway pack endpoint lists additional shared tools, so its tool count is larger than the six SpaceX-specific tools. Use the local package when you need only this pack's tools without gateway routing.