Nasa Eonet

What the Nasa Eonet MCP server does

Nasa Eonet MCP server exposes NASA EONET data to MCP-compatible applications. EONET aggregates event information from official sources, including categories such as wildfires, severe storms, volcanoes, storms, snow, icebergs, dust and haze, and manmade events. The service is intended for agents that need to find current or recent Earth events, inspect one event, or receive event records in a format suitable for geospatial processing.

The underlying data source is NASA Goddard's public EONET API at https://eonet.gsfc.nasa.gov/api/v3/. Authentication is not required. The package is distributed as @pipeworx/mcp-nasa-eonet and is licensed under MIT.

How it works

A gateway connection is available at https://gateway.pipeworx.io/nasa-eonet/mcp. The gateway lists the pack's tools along with shared Pipeworx meta-tools. Those shared tools can route questions to other catalog sources, so the number of tools reported by tools/list is larger than the pack-specific list. The initialize response gives the authoritative scope for the connection.

The same gateway also offers a full endpoint at https://gateway.pipeworx.io/mcp, where tools from all available packs are listed directly. The pack endpoint and full endpoint use the same gateway and data-source catalog; they differ in which pack tools are shown directly.

For a local deployment, the npm package communicates over stdin and stdout using MCP. In that mode, only the Nasa Eonet MCP server's own tools are exposed, without the gateway's shared meta-tools or cross-catalog routing. The service can also be called over HTTP through gateway tool endpoints without an MCP client.

Setup and configuration

Add the gateway URL to an MCP client as a remote server:

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

For standalone use, configure the npm package as a local command:

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

Running npx -y @pipeworx/mcp-nasa-eonet directly can be used to confirm that the local process starts. No environment variables or account are specified as required. Gateway users can send HTTP requests such as a POST to /v1/tools/nasa_eonet_events with JSON arguments.

Tools and capabilities

The Nasa Eonet MCP server provides these pack-specific tools:

• events lists events and supports status, time range in days, source, category, bounding box, result limit, and magnitude filters.
• get_event retrieves details for one event by ID.
• geojson returns matching events as a GeoJSON FeatureCollection, with status, days, category, bounding box, and limit filters.
• list_categories returns the available category reference.
• list_sources lists the official sources aggregated by EONET.
• list_layers returns visualization layer information, optionally filtered by category.

The gateway's ask_pipeworx tool can accept a plain-language question and select a tool and arguments automatically. This routing feature belongs to the gateway connection rather than the standalone package.

Limitations and notes

The gateway pack endpoint always includes shared Pipeworx meta-tools; there is currently no documented way to remove them from that connection. Choose the standalone npm process when only the six EONET tools are needed and local stdio operation is preferred. Choose the gateway when cross-catalog routing or HTTP access is useful.