Aemet MCP Server

If you already use Aemet, the aemet mcp server is the piece that lets your assistant work with it directly. MCP server for AEMET — Spain's weather agency. Forecasts, CAP warnings, station observations.

What the server does

Tools for working with AEMET OpenData, the public API of Spain's State Meteorological Agency.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Package — Description

Credentials and setup notes

Configuration is passed through the environment: AEMET_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

The server ships on npm as pnpm, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Where it fits

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. Aemet's toolset — Package — is a fair guide to whether it matches your workflow. It is maintained by jocarrd; worth a glance at recent repository activity before you build anything load-bearing on it.

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

Worth knowing first

• 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.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.