Measure MCP Server

Measure MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for weather, climate, air quality and geocoding from measurespace.io.

What you get

A Model Context Protocol (MCP) server for weather, climate, air quality, agriculture, pollen and geocoding services from measurespace.io.

• Hourly weather forecast for next 5 days
• Daily weather forecast for next 15 days
• Daily climate forecast for next 9 months
• Hourly and daily air quality forecast for next 4 days
• Agriculture: Growing Degree Days (GDD), crop growth stage, heat and frost stress days
• Pollen: Daily pollen forecast for next 5 days

What the assistant can call

Once Measure is connected, these are the calls the assistant has available:

• Implementation — Folder
• GEOCODING_API_KEY — City ↔ lat/lon geocoding
• HOURLY_WEATHER_API_KEY — Hourly weather forecast
• DAILY_WEATHER_API_KEY — Daily weather forecast
• DAILY_CLIMATE_API_KEY — Daily climate forecast
• AIR_QUALITY_API_KEY — Air quality forecast
• AGRICULTURE_API_KEY — Agriculture services
• POLLEN_API_KEY — Daily pollen forecast

Configuration and credentials

You will need 7 environment variables: GEOCODING_API_KEY, HOURLY_WEATHER_API_KEY, DAILY_WEATHER_API_KEY, DAILY_CLIMATE_API_KEY, AIR_QUALITY_API_KEY, AGRICULTURE_API_KEY, POLLEN_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.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Measure's toolset — Implementation, GEOCODING_API_KEY, HOURLY_WEATHER_API_KEY and 5 more — is a fair guide to whether it matches your workflow. It is maintained by MeasureSpace; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Measure's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• 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 measure mcp server does with a few real requests.