noaa-enso
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
@pipeworx/noaa-enso
Oceanic Nino Index (ONI) seasons and the El Nino / La Nina state they imply, from the NOAA Climate Prediction Center.
Part of Pipeworx — an MCP gateway connecting AI agents to 2034+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
enso_oni(latest?, from_year?, to_year?)— 3-month ONI seasons with Nino 3.4 sea-surface temperature, anomaly, state and strength band, plusdata_as_of. Answers "what is the current ENSO state / ONI".
Related MCP server: mcp-server-eia
Auth
Keyless.
Data sources
NOAA Climate Prediction Center, Oceanic Nino Index (1950 to the latest season).
State uses the publisher's +/-0.5 C threshold per season; NOAA only declares an episode after five consecutive overlapping seasons, which the response notes. Strength bands (weak, moderate, strong, very strong at 0.5/1.0/1.5/2.0) follow NOAA's published convention.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"noaa-enso": {
"url": "https://gateway.pipeworx.io/noaa-enso/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/noaa-enso/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 2034+ 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/enso_oni \
-H 'Content-Type: application/json' \
-d '{"latest":6}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/enso_oni. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Run it from npm
@pipeworx/mcp-noaa-enso is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with npx, and it forwards every call to the same
https://gateway.pipeworx.io/noaa-enso/mcp endpoint shown above. It needs network access;
there is no offline mode.
{
"mcpServers": {
"noaa-enso": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-noaa-enso"]
}
}
}Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
"env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to
also list ask_pipeworx and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by
default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check
your Node version's documentation.
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 Noaa Enso data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
US weather & geo for AI agents: forecasts, alerts, earthquakes, elevation, geocoding. No keys.
US weather & geo for AI agents: forecasts, alerts, earthquakes, elevation, geocoding. No keys.
Search NOAA climate stations and datasets, fetch historical weather observations.
US NWS weather alerts and 5-day forecasts for AI agents. $0.01 per call.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceExposes public weather and climate data through a standardized API, allowing AI agents to retrieve current conditions, 7-day forecasts, and historical data. It enables weather-aware automation and data enrichment for conversational agents and travel planning.-
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with structured access to the U.S. EIA Open Data API for energy data including power plants, operations, fuel prices, projections, and state CO2 emissions.MIT
- AlicenseNot gradedqualityFmaintenanceProvides NOAA tide predictions and observed water levels, allowing AI agents to query tide stations and current water level data.2 npmMIT
- FlicenseBqualityCmaintenanceEnables dynamic, real-time weather alerts and forecasts from the National Weather Service through AI agentic tool calls.22-