AEMET
MCP server exposing AEMET (Spanish weather agency) forecasts, station data and warnings.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
@mmillan76/aemet-mcpclaude mcp add aemet -e 'AEMET_API_KEY=<your aemet_api_key>' -- npx -y @mmillan76/aemet-mcp@0.1.1
{
"mcpServers": {
"aemet": {
"command": "npx",
"args": [
"-y",
"@mmillan76/aemet-mcp@0.1.1"
],
"env": {
"AEMET_API_KEY": "<your aemet_api_key>"
}
}
}
}
Environment variables
AEMET_API_KEYrequired secret Free AEMET OpenData API key. Request one at https://opendata.aemet.es/centrodedescargas/altaUsuario
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
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
- Node.js 20+
- A free AEMET OpenData API key: request one at https://opendata.aemet.es/centrodedescargas/altaUsuario
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.
Frequently asked questions
What is AEMET?
MCP server exposing AEMET (Spanish weather agency) forecasts, station data and warnings.
How do I install AEMET?
It runs on your machine. In Claude Code: claude mcp add aemet -e 'AEMET_API_KEY=<your aemet_api_key>' -- npx -y @mmillan76/aemet-mcp@0.1.1. For other clients, paste the JSON configuration from this page into their MCP settings.
Does AEMET need an API key?
Yes. It expects AEMET_API_KEY, which you set in its configuration.
Is AEMET open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains AEMET?
It is published by mmillan76. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.