AEMET-MCP. Integration via MCP with the AEMET API

Created By
AnCode666a year ago
MCP server for check Spanish climate data using AEMET web API
Overview

What is AEMET-MCP?

AEMET-MCP is a server that integrates with the AEMET API to provide access to historical climate data and meteorological information for Spain.

How to use AEMET-MCP?

To use AEMET-MCP, install it via the Smithery package manager and configure it with your AEMET API key in any compatible client like Claude for Desktop.

Key features of AEMET-MCP?

  • Retrieve historical daily values (temperature, wind, precipitation, etc.)
  • Access monthly climate summaries by station
  • Filter data by year, month, and AEMET station code
  • Query beach conditions, including UV radiation indices
  • Responses are formatted in JSON for easy integration

Use cases of AEMET-MCP?

  1. Analyzing historical weather patterns in Spain
  2. Providing real-time weather updates for specific locations
  3. Researching climate data for academic or professional purposes

FAQ from AEMET-MCP?

  • Can AEMET-MCP be used for real-time data?

No, AEMET-MCP primarily provides access to historical climate data.

  • Is there a cost to use AEMET-MCP?

AEMET-MCP is free to use, but you need to obtain a free API key from AEMET.

  • What programming language is AEMET-MCP built with?

AEMET-MCP is built using Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AnCode666
Star
2
Language
Python
License
MIT license

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago