Wems MCP Server

Real-time natural hazard monitoring: earthquakes, tsunamis, volcanoes, solar weather, air quality

Local serverstdioPython

What is the Wems MCP server?

Most monitoring and observability work still happens through a UI a human drives. Wems MCP server moves it into the conversation instead. Real-time natural hazard monitoring: earthquakes, tsunamis, volcanoes, solar weather, air quality.

The short version

A powerful Model Context Protocol (MCP) server that connects AI assistants to authoritative natural hazard data sources. Monitor earthquakes, tsunamis, volcanoes, and solar events with configurable alerts and webhooks.

The tools it exposes

The server publishes 14 tools. What each one is for:

  • check_earthquakes — Query recent earthquake activity
  • check_solar — Monitor space weather (K-index, flares, CMEs)
  • check_volcanoes — Track volcanic activity alerts
  • check_tsunamis — Monitor tsunami warnings
  • check_hurricanes — Track tropical cyclones & forecast tracks
  • check_wildfires — Fire weather alerts & active perimeters
  • check_severe_weather — Monitor tornadoes, thunderstorms, flash floods
  • check_floods — Flood warnings & USGS river gauge data
  • check_air_quality — AQI monitoring with pollutant data
  • check_threat_advisories — Terrorism, travel risk & cyber threat monitoring
  • check_space_weather_alerts — Active space weather alerts & warnings from NOAA SWPC
  • check_drought_status — US state drought conditions with D0-D4 levels (Premium)

What it needs from you

Configuration is passed through the environment: WEMS_CONFIG, STRIPE_API_KEY, STRIPE_SECRET_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

The server ships on PyPI as wems-mcp-server, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

How it compares

This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Wems's toolset — check_earthquakes, check_solar, check_volcanoes and 11 more — is a fair guide to whether it matches your workflow. It is maintained by heliosarchitect; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Wems.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
check_earthquakesQuery recent earthquake activity
check_solarMonitor space weather (K-index, flares, CMEs)
check_volcanoesTrack volcanic activity alerts
check_tsunamisMonitor tsunami warnings
check_hurricanesTrack tropical cyclones & forecast tracks
check_wildfiresFire weather alerts & active perimeters
check_severe_weatherMonitor tornadoes, thunderstorms, flash floods
check_floodsFlood warnings & USGS river gauge data
check_air_qualityAQI monitoring with pollutant data
check_threat_advisoriesTerrorism, travel risk & cyber threat monitoring
check_space_weather_alertsActive space weather alerts & warnings from NOAA SWPC
check_drought_statusUS state drought conditions with D0-D4 levels (Premium)
configure_alertsUpdate alert thresholds and webhooks
fuse_multi_source_incidentsMulti-source incident fusion (feature-flagged)

How to install the Wems MCP server

{
  "mcpServers": {
    "wems": {
      "command": "uvx",
      "args": ["wems-mcp-server"],
      "env": {
        "WEMS_CONFIG": "your-value",
        "STRIPE_API_KEY": "your-value",
        "STRIPE_SECRET_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
WEMS_CONFIGConfiguration value read at startup.Optional
STRIPE_API_KEYCredential the server authenticates with.Yes
STRIPE_SECRET_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Wems to check earthquakes.
  • Use Wems to check solar.
  • Use Wems to check volcanoes.

Frequently asked questions

It connects Wems to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (check_earthquakes, check_solar, check_volcanoes, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Wems directly.