Ipma Pt
IPMA Portugal MCP — weather, UV, sea state, and earthquakes from the
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).
claude mcp add --transport http ipma-pt 'https://gateway.pipeworx.io/ipma-pt/mcp'{
"mcpServers": {
"ipma-pt": {
"type": "http",
"url": "https://gateway.pipeworx.io/ipma-pt/mcp"
}
}
}Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
mcp-ipma-pt
IPMA Portugal MCP — weather, UV, sea state, and earthquakes from the
Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.
Tools
| Tool | Description |
|---|---|
ipma_forecast | Portugal weather forecast — official IPMA 5-day forecast for a Portuguese city: Lisbon, Porto, Faro, the Algarve, Madeira (Funchal), Azores (Ponta Delgada). Returns daily min/max temperature (°C), precipitation probability, weather description in English, and wind direction/strength. Example: ipma_forecast({ city: "Lisboa" }) |
ipma_uv_forecast | UV index forecast for Portugal from IPMA — daily peak-hours ultraviolet index for a Portuguese city (Lisbon, Porto, Algarve, Madeira, Azores) for the next ~3 days, with risk level (Low to Extreme). Example: ipma_uv_forecast({ city: "Faro" }) |
ipma_sea_forecast | Sea state forecast for the Portuguese coast from IPMA oceanography — significant wave height (m), wave period (s), wave direction, and sea surface temperature (°C) for 12 coastal zones on the mainland, Madeira, and Azores. Good for surf, sailing, and beach conditions. Example: ipma_sea_forecast({ city: "Sagres" }) |
ipma_seismic | Portugal earthquakes — recent seismic events recorded by IPMA for mainland Portugal + Madeira or for the Azores archipelago. Returns time, magnitude, depth, epicenter region, coordinates, and felt intensity when reported. Covers roughly the last 30 days. Example: ipma_seismic({ area: "azores", min_magnitude: 2 }) |
ipma_locations | List the Portuguese cities and islands IPMA publishes weather forecasts for — district capitals plus Madeira and Azores islands — with their globalIdLocal codes and coordinates region. Filter by name. Example: ipma_locations({ query: "faro" }) |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"ipma-pt": {
"url": "https://gateway.pipeworx.io/ipma-pt/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/ipma-pt/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1679+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/ipma_forecast \
-H 'Content-Type: application/json' \
-d '{"city":"Lisboa"}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/ipma_forecast. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"ipma-pt": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-ipma-pt"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-ipma-ptIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Ipma Pt data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Frequently asked questions
What is Ipma Pt?
IPMA Portugal MCP — weather, UV, sea state, and earthquakes from the
How do I install Ipma Pt?
It runs as a remote server. In Claude Code: claude mcp add --transport http ipma-pt 'https://gateway.pipeworx.io/ipma-pt/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Ipma Pt need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Ipma Pt open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Ipma Pt?
It is published by pipeworx-io. 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.