Nasa

@nasa show me all active wildfire events from EONET in the last 30 days with their coordinates and magnitudes

Based on EONET data, here are 8 active wildfire events detected in the past 30 days: (1) Creek Fire in California (37.2°N, 119.3°W, magnitude 4), first detected Jan 15; (2) Bushfire near Sydney, Australia (33.8°S, 151.2°E, magnitude 3), detected Jan 18; (3) Amazon wildfire in Brazil (3.1°S, 60.0°W, magnitude 2), detected Jan 22… Each entry includes event ID, location geometry, detection date, and source satellite (MODIS/VIIRS). This is an illustrative example—actual event counts and locations vary by query date.

This example demonstrates EONET's real-time natural event tracking. The MCP requires no authentication for EONET endpoints, but responses depend on current satellite observations—wildfire counts fluctuate daily. Useful for environmental monitoring dashboards or alert systems that need geospatial event data.

@nasa find all NASA Earth science data collections related to sea surface temperature measurements in the Pacific Ocean from 2020-2023

CMR search returned 14 collections matching your criteria: (1) MODIS Aqua Level-3 SST (collection ID: C1234567890-PODAAC), temporal coverage 2002-present, 4km resolution; (2) GHRSST Level 4 MUR Global SST (C9876543210-PODAAC), daily 1km analysis; (3) VIIRS NPP Ocean Color SST (C1122334455-OB_DAAC), 750m resolution… Each collection includes metadata on temporal range, spatial resolution, data format (NetCDF/HDF5), and access protocols. This illustrative example shows typical CMR structure—actual collection counts vary by filter specificity.

This showcases CMR's powerful metadata search across NASA's science archives. Requires an API key for rate limits above 10 requests/minute. The spatial and temporal filters are critical—broad queries can return hundreds of collections. Best used when you need to identify datasets before downloading actual granule data.

@nasa summarize the most severe natural events globally this month by category, and explain which NASA satellites are tracking each type

This month's most severe events by EONET category: **Wildfires** (18 events, magnitude 3-5): Tracked by MODIS on Terra/Aqua and VIIRS on Suomi-NPP, detecting thermal anomalies at 375m-1km resolution. **Severe Storms** (12 events, magnitude 2-4): Monitored via GOES-16/17 geostationary imagery and GPM precipitation radar. **Volcanoes** (3 events, magnitude 3-5): Observed by Landsat-8 thermal bands and Sentinel-2 for ash plumes. EONET aggregates data from 8 sources including NASA's Earth Observing System. This synthesis is illustrative—actual event distributions change daily based on satellite passes and ground reports.

This example pairs EONET event data with the AI's ability to synthesize patterns across categories and explain satellite capabilities. It demonstrates how the MCP enables environmental intelligence workflows beyond raw data retrieval. Note that magnitude scales vary by event type, and source attribution requires cross-referencing EONET's source metadata endpoint.

When NASA MCP beats manual dataset hunting for research teams

A 3-person climate research team needs to pull satellite imagery and event data for a wildfire impact study covering California's 2023 season. The NASA MCP is the right call here: the CMR tools let you filter collections and granules by spatial bounds and date ranges in one query, and the EONET event feeds give you structured wildfire start dates without scraping news sites. You'll need an API key (free from NASA's portal), and the 12 tools cover the full workflow from collection discovery to granule download URLs. The threshold: if you're only pulling data once or twice a year, the manual NASA Earthdata portal is faster to set up. But if you're running monthly or weekly pulls for ongoing analysis, the MCP pays off by the third run. Worth it for any team doing repeatable earth science queries.

How EONET tools support real-time crisis dashboards

A nonprofit building a public dashboard for natural disaster tracking (hurricanes, floods, wildfires) can use the NASA MCP's EONET endpoints to automate event ingestion. The RSS and ATOM feeds refresh every few hours, and the category and magnitude filters let you scope to high-severity events only. The MCP handles the API key auth and returns structured JSON, so your dashboard script doesn't need to parse NASA's web UI. The catch: EONET data lags by 6-24 hours depending on the event type, so this isn't for first-responder use cases where you need sub-hour latency. It's ideal for situational awareness dashboards that update daily or twice-daily. If your team is already polling other disaster APIs, adding the NASA MCP takes under an hour and gives you a second authoritative source.

When NASA MCP isn't worth it for one-off classroom projects

A high school teacher wants to pull Mars rover images for a single semester project on planetary geology. The NASA MCP is overkill here: setting up API key auth and learning the CMR collection syntax takes longer than browsing NASA's public image galleries and downloading 20 photos by hand. The MCP's value is in repeatable queries, not one-time pulls. However, if you're a curriculum developer building a reusable lesson plan generator that pulls fresh satellite images every semester, the MCP becomes the right tool. The threshold is roughly 5+ queries over 6+ months. Below that, manual downloads are faster. Above that, the MCP saves hours per semester and keeps your content current without manual updates. For single-use classroom needs, skip the integration and use NASA's web portals directly.