AEMET logo

AEMET

Access Spanish forecasts, station observations, and active weather warnings through MCP.

Install AEMET

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "aemet": {
      "command": "npx",
      "args": [
        "-y",
        "@mmillan76/aemet-mcp"
      ],
      "env": {
        "AEMET_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 3 tools correctly (6d ago).

Overview

The AEMET MCP server connects AI agents and MCP-compatible clients to Spain’s official AEMET OpenData weather API. It provides tools for municipality forecasts, recent weather-station observations, and active CAP warnings. The server runs over stdio and uses an AEMET API key supplied through an environment variable. Reach for it when an agent needs current Spanish weather data rather than general-purpose forecast information.

Use cases

  • Retrieve seven-day forecasts for Spanish municipalities
  • Check recent observations from AEMET weather stations
  • Monitor active weather warnings by region
  • Answer agent queries using official Spanish weather data

Key features

  • Municipality forecasts by INE code
  • Up to seven days of daily forecast data
  • Recent hourly station observations
  • Active CAP warnings for regions or Spain
  • AEMET OpenData API integration
  • stdio transport for MCP clients

Tools3

What AEMET lets your agent do. Expand a tool for its parameters.

Verified live~373 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

7/7 checks healthy over the last 41d

What it can do

From the 3 tools this server returned when we ran it.

Read-only tools · 3
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age84 days
Maintainers1

Observed 2026-10-18 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @mmillan76/aemet-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads81Package downloads in the last 30 days.
Last commit3mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed3Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How AEMET works

What AEMET MCP server does

The AEMET MCP server exposes selected public data from Spain’s Agencia Estatal de Meteorología through three typed MCP tools. It is intended for AI agents and clients that can launch standard input/output MCP servers.

The available data covers three use cases:

  • Daily forecasts for a Spanish municipality, identified by its INE code, for up to seven days.
  • Approximately the latest 12 hours of hourly observations from a weather station, including measurements such as temperature, wind, and precipitation.
  • Active CAP weather alerts for a selected region or for Spain as a whole.

This makes the server suitable for assistants that need location-specific Spanish weather information, recent station readings, or a check for current warnings.

How it works

The server communicates with its MCP client over stdio. A client starts the package, sends tool requests, and receives the resulting weather data; it is not designed to provide a standalone terminal interface.

Behind the tools, the server calls AEMET’s official OpenData API. AEMET uses a two-request response flow: an initial API call returns a JSON envelope containing a URL in datos, and a follow-up request retrieves the actual payload. The server handles this sequence internally, so callers receive the final data instead of managing the intermediate URL.

AEMET applies rate limits per API key. When a limit or other API error occurs, the server reports an error rather than silently retrying.

Setup and configuration

The AEMET MCP server requires Node.js 20 or newer and a free AEMET OpenData API key. Keys can be requested through AEMET’s OpenData registration page. Set the key in AEMET_API_KEY; startup fails if that variable is absent.

No package installation is required for normal use. Configure an MCP client to run:

Terminal
npx -y @mmillan76/aemet-mcp

Pass AEMET_API_KEY in the client’s environment. Claude Desktop and Claude Code can use this command-and-environment configuration, and other clients can use the same arrangement when they support stdio servers.

For local development, clone the repository, run npm install, create .env from .env.example, set the API key, and run npm run build. The compiled server can be inspected interactively with MCP Inspector using node dist/index.js, with the API key exported in the shell or loaded from the environment.

Tools and capabilities

  • get_municipality_forecast: retrieves a daily forecast for a Spanish municipality by INE code, covering up to seven days.
  • get_station_observation: retrieves roughly 12 hours of hourly observations from a weather station, including weather measurements such as temperature, wind, and precipitation.
  • get_weather_warnings: retrieves active CAP alerts for a region or all of Spain.

Limitations and notes

The data source is limited to AEMET’s public Spanish weather services. Municipality forecasts require an INE code, and station observations require a weather station. API-key rate limits can affect requests. The server supports stdio rather than acting as an independently hosted HTTP service, and it does not silently retry failed or rate-limited API calls.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about AEMET

AEMET is an MCP server that connects AI agents and MCP-compatible clients to Spain’s AEMET OpenData weather API. Its main tools retrieve municipality forecasts, recent station observations, and active CAP warnings for regions or Spain as a whole. It uses an API key and communicates with clients over stdio.

Run it with `npx -y @mmillan76/aemet-mcp`; no separate package installation is needed for normal use. Configure your MCP client to launch that command and provide `AEMET_API_KEY` in its environment. Node.js 20 or newer is required.

Yes, AEMET works with Cursor if it supports stdio MCP servers. Configure Cursor to launch `npx -y @mmillan76/aemet-mcp` and set the required `AEMET_API_KEY` environment variable.

It requires a free AEMET OpenData API key in the `AEMET_API_KEY` environment variable. Request the key through AEMET’s OpenData registration page; the server exits with an error at startup when the variable is missing.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAEMET AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/aemet?style=directory)](https://allmcps.com/mcp/aemet)
HTML Embed
<a href="https://allmcps.com/mcp/aemet"><img src="https://allmcps.com/api/badge/aemet?style=directory" alt="AEMET on AllMCPs" /></a>