WeatherXM PRO MCP Server

This MCP server exposes the WeatherXM PRO APIs as MCP tools, allowing clients to access weather station data, observations, and forecasts through the MCP protocol. The weatherxm pro mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 1 defined tool rather than through you.

What it actually does

• Get stations near a location (latitude, longitude, radius)
• Get stations within a bounding box (min/max latitude and longitude)
• Get all available stations
• Get the latest observation for a specific station
• Get historical observations for a station on a specific date
• Search for H3 cells by region name

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at npm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Its toolset

Everything the assistant can do here goes through one of these:

• Build — The Build tool exposed by this server

Configuration

You will need one environment variable: WEATHERXMPRO_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js and npm installed - A valid WeatherXM PRO API key

Caveats

• 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.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the weatherxm pro mcp server does with a few real requests.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. WeatherXM PRO's toolset — Build — is a fair guide to whether it matches your workflow. It is maintained by WeatherXM; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.