mcpField
A
AEMET

AEMET

Local
github.com/mmillan76Maps & Travel0Updated 14w ago

About AEMET

AEMET is an MCP server that provides Spanish weather data from the official AEMET OpenData API for AI agents and MCP-compatible clients. Its tools cover municipal forecasts, station observations, and active weather warnings.

Key features

  1. 01Get municipal forecasts for up to 7 days
  2. 02Retrieve hourly weather station observations
  3. 03Check regional or nationwide active warnings
  4. 04Return data from AEMET OpenData

Use cases

  1. 01Check a Spanish municipality's forecast
  2. 02Review recent station observations
  3. 03Find active warnings for a region

MCP support

It exposes three tools to MCP clients over stdio: municipal forecasts, station observations, and weather-warning queries.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"mmillan76-aemet": {
"command": "npx",
"args": [
"-y",
"@mmillan76/aemet-mcp"
],
"env": {
"AEMET_API_KEY": "<AEMET_API_KEY>"
}
}
}
}
Run commandnpx -y @mmillan76/aemet-mcp
Environment variables to set
AEMET_API_KEYSecretFree AEMET OpenData API key. Request one at https://opendata.aemet.es/centrodedescargas/altaUsuario

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@mmillan76/aemet-mcp0.1.1

Tools

3

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
municipioCodestringYesINE municipality code (5 digits), e.g. 28079 for Madrid. Look it up at https://www.ine.es/daco/daco42/codmun/codmunmapa.htm

Details

From the project README

aemet-mcp

MCP server that exposes public weather data from AEMET (Agencia Estatal de Meteorología, Spain) to AI agents and MCP-compatible clients.

Three tools, well-typed, backed by AEMET's official OpenData API:

  • get_municipality_forecast — daily forecast (up to 7 days) for a Spanish municipality, by INE code.
  • get_station_observation — last ~12h of hourly observation data (temperature, wind, precipitation…) from a weather station.
  • get_weather_warnings — active weather warnings (CAP alerts) for a region or all of Spain.

Prerequisites

Installation

No install needed — run it directly with npx:

npx -y @mmillan76/aemet-mcp

The server communicates over stdio, so it's meant to be launched by an MCP client rather than run standalone in a terminal.

Configuration

The server reads the API key from the AEMET_API_KEY environment variable. It exits with an error at startup if it's missing.

Claude Desktop / Claude Code

Add to your MCP client config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "aemet": {
      "command": "npx",
      "args": ["-y", "@mmillan76/aemet-mcp"],
      "env": {
        "AEMET_API_KEY": "your-api-key-here"
      }
    }
  }
}

Any other MCP client that supports stdio servers works the same way — point it at npx -y @mmillan76/aemet-mcp with AEMET_API_KEY set in the environment.

Local development

git clone https://github.com/mmillan76/aemet-mcp.git
cd aemet-mcp
npm install
cp .env.example .env   # fill in AEMET_API_KEY
npm run build

Test tool calls interactively with the MCP Inspector:

npx @modelcontextprotocol/inspector node dist/index.js

(the Inspector reads AEMET_API_KEY from your shell environment, so export it — or source .env — before running the command above)

Notes on the AEMET API

AEMET OpenData uses a two-step pattern on every endpoint: the first request returns a JSON envelope with a datos URL, not the actual data; a second request to that URL returns the real payload. This server hides that detail — tools just return the final data. Rate limits apply per API key; if you hit them, the tool returns a clear error instead of retrying silently.

License

MIT — see LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.