Skip to main content

AEMET-MCP. Integration via MCP with the AEMET API

en es

DESCRIPTION

AEMET is the State Meteorological Agency of Spain.

Aemet-mcp allows you to retrieve historical climate data and meteorological information from the AEMET API directly from Claude AI and other MCP compatible clients, using the Model Context Protocol (MCP).

Aemet-mcp is an MCP server that exposes tools enabling LLMs to query data from weather stations across Spain.

It includes secure handling of API keys and resource JSON files for using supporting data.

KEY FEATURES

  • Query for historical daily values (temperature, wind, precipitation, etc.)
  • Access to monthly climate summaries by station.
  • Filtering by year, month, and AEMET station code.
  • Query beach conditions, including ultraviolet radiation indices.
  • Rainfall data analysis prompt for Spanish municipalities with historical precipitation data
  • Responses ready for use in JSON format.

INSTALLATION

Installing via Smithery

To install AEMET Weather Data Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @AnCode666/aemet-mcp --client claude

Install with uv

Prerequisites

  • Python 3.10 or higher.
  • uv package manager.

Installing uv

The first step is to install uv, a package manager for Python.
It can be installed from the command line.

On macOS and Linux:

curl -LsSf https://astral.sh/uv/install.sh | sh

On Windows:

powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

You can also install it with pip:

pip install uv

For more information about installing uv, visit the uv documentation.

Install with Docker

You can also run AEMET-MCP using Docker:

Prerequisites

  • Docker installed on your system

Steps

  1. Build the Docker image:
docker build -t aemet-mcp .
  1. Run the container:
docker run -e AEMET_API_KEY=YOUR_AEMET_API_KEY aemet-mcp

Replace YOUR_AEMET_API_KEY with your actual API key from AEMET.

Integration with Claude Desktop using Docker

To use the Docker version with Claude Desktop, add this configuration to your claude_desktop_config.json:

"aemet_mcp_docker": {
    "command": "docker",
    "args": [
        "run",
        "--rm",
        "-i",
        "-e", "AEMET_API_KEY=YOUR_AEMET_API_KEY",
        "aemet-mcp"
    ]
}

INTEGRATION WITH CLIENTS LIKE CLAUDE DESKTOP

Once uv is installed, you can use the MCP server from any compatible client such as Claude for Desktop, in which case the steps to follow are:

  1. Go to Claude > Settings > Developer > Edit Config > claude_desktop_config.json
  2. Add the following block inside "mcpServers":
"aemet_mcp_": {
    "command": "uvx",
    "args": [
        "aemet_mcp"
    ],
    "env": {
        "AEMET_API_KEY": "YOUR_AEMET_API_KEY"
    }
}
  1. Get a free API key from AEMET at: https://opendata.aemet.es/centrodedescargas/altaUsuario
  2. Replace YOUR_AEMET_API_KEY with your actual API key (leave the quotes).
  3. If you already have another MCP server configured, separate each with a comma ,.

In general, to integrate it into any other MCP-compatible client such as Cursor, CODEGPT, or Roo Code, simply go to the MCP server configuration of your client and add the same code block.

USAGE EXAMPLES

Once properly configured, you can ask things like:

  • "What's the weather like in Seville?"
  • "Give me a list of the beaches in the province of Málaga"
  • "Tell me the radiation levels at Maspalomas beach for tomorrow"
  • "Give me the historical rainfall data for Albacete between January 1st, 2020 and February 1st, 2020"
  • "Give me a list of the weather stations within a 50 km radius from the coordinates lat:40.4165, lon:-3.70256"

Rainfall Data Analysis

The server includes a specialized prompt for analyzing historical precipitation data for Spanish municipalities. Use the obtener_datos_lluvia_municipio prompt with:

obtener_datos_lluvia_municipio("Madrid", "2023-01-01", "2023-12-31")

This prompt provides structured guidance for meteorological analysis, including:

  • Municipality code search and validation
  • Nearest weather station identification
  • Historical precipitation data retrieval
  • Statistical analysis and trend identification
  • Climate pattern analysis with seasonal variations
  • Data visualization recommendations

DISTRIBUTIONS

Smithery

smithery badge

Glama

AEMET-MCP MCP server

MseeP

MseeP.ai Security Assessment Badge Verified on MseeP

MCP Review

MCP review certified

Metadata

Release files for aemet-mcp 0.3.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for aemet-mcp 0.3.2
File Size Uploaded
aemet_mcp-0.3.2.tar.gz 128.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for aemet-mcp 0.3.2
File Interpreter ABI Platform
aemet_mcp-0.3.2-py3-none-any.whl Python 3 none any Details

Total release size: 255.7 kB

Release files / aemet_mcp-0.3.2.tar.gz

Download URL aemet_mcp-0.3.2.tar.gz
Size 128.2 kB
Tags Source
SHA-256 checksum
How to use checksums
ca8b569cfdcedddcf5ae7c10c26b337b28b35e4d2c13a4aaff7f3fd1b8ffa802
BLAKE2b-256 checksum
How to use checksums
a05f3ed47ac4794db44e73384b6fa5c7d9c38298a90d59f0b0436d7f16beac58
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 27, 2025.

Transparency log

Release files / aemet_mcp-0.3.2-py3-none-any.whl

Download URL aemet_mcp-0.3.2-py3-none-any.whl
Size 127.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
789187ba8b47ccdda4417ab7b89ed730e9098a8ceb5dc55eb02ff06656f448f8
BLAKE2b-256 checksum
How to use checksums
50edd2a4672b63e31872ebb7ac419cdcf78d1db15ee317d59167283549e09166
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 27, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

0.3.2 This release

2 release files

0.3.1

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.20

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page