Noaa Swpc logo

Noaa Swpc

Access NOAA space weather alerts, solar wind, geomagnetic indices, aurora forecasts, and GOES X-ray data through MCP.

Install Noaa Swpc

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "noaa-swpc": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-noaa-swpc"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Noaa Swpc connects MCP-compatible AI clients to NOAA's Space Weather Prediction Center products through the Pipeworx gateway. It exposes tools for alerts, solar wind, Kp indices, aurora forecasts, GOES X-ray flux, Boulder K values, and the three-day forecast text. Use it when an agent needs current or recent space weather data without managing NOAA credentials. Hosted access is available over HTTPS, while an npm package provides a local stdio bridge.

Use cases

  • Check current NOAA space weather alerts
  • Inspect recent solar wind measurements
  • Compare planetary Kp index history
  • Retrieve short-term aurora forecasts
  • Monitor GOES X-ray flux and geomagnetic activity

Key features

  • Current SWPC alerts and warnings
  • DSCOVR solar wind data
  • Planetary and Boulder K indices
  • 30-minute northern and southern aurora forecasts
  • GOES X-ray flux history
  • Three-day forecast text

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

10/10 checks healthy over the last 58d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @pipeworx/mcp-noaa-swpc (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads462Package downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Noaa Swpc works

What Noaa Swpc does

Noaa Swpc provides MCP access to keyless JSON products from NOAA's Space Weather Prediction Center. Its data covers operational space weather conditions and forecasts, including current alerts and warnings, solar wind measurements, geomagnetic activity, aurora probability, GOES X-ray flux, and forecast text.

The integration is independent and unofficial. Data is retrieved from NOAA's services.swpc.noaa.gov/products/... endpoints through the Pipeworx service. It is a fit for agents that need to answer questions about recent solar activity, inspect geomagnetic conditions, or retrieve structured space weather observations.

How it works

The hosted MCP endpoint is:

https://gateway.pipeworx.io/noaa-swpc/mcp

An MCP client can connect to that URL and list the Noaa Swpc tools. The scoped endpoint also exposes shared Pipeworx gateway tools, including routing and discovery functions. The exact tool scope is reported by the connection's initialize response. A full gateway endpoint is also available at https://gateway.pipeworx.io/mcp; both endpoints use the same gateway and data sources.

The service can also be called directly over HTTP. For example, a POST request to https://gateway.pipeworx.io/v1/tools/alerts with an empty JSON body invokes the alerts tool. The gateway supports anonymous calls, and a Pipeworx account can be used for a higher daily call allowance.

For local MCP deployments, @pipeworx/mcp-noaa-swpc runs through npx as a stdio adapter. It forwards requests to the hosted gateway, so it requires network access and has no offline mode.

Setup and configuration

Add the hosted endpoint to an MCP client such as Claude Desktop, Cursor, or Windsurf:

config.json
{
  "mcpServers": {
    "noaa-swpc": {
      "url": "https://gateway.pipeworx.io/noaa-swpc/mcp"
    }
  }
}

The local option uses this configuration:

config.json
{
  "mcpServers": {
    "noaa-swpc": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-noaa-swpc"]
    }
  }
}

Anonymous local calls are capped at 50 per day. A free Pipeworx account raises the limit to 200 calls per day. Add PIPEWORX_API_KEY to the local server environment to authenticate with a key. Set PIPEWORX_META_TOOLS=1 if the local bridge should also list the shared gateway tools. Behind an HTTPS proxy, newer Node.js releases can use the proxy environment with NODE_USE_ENV_PROXY=1.

Tools and capabilities

  • alerts() retrieves current SWPC alerts and warnings.
  • solar_wind(window?) returns recent DSCOVR plasma and magnetic-field data for five-minute, one-hour, two-hour, or one-day windows.
  • kp_index(window?) provides planetary K index history for the current value, one day, seven days, or 30 days.
  • aurora_forecast() returns the 30-minute Ovation forecast for northern or southern regions.
  • goes_xray(window?) retrieves recent GOES X-ray flux for six-hour, one-day, three-day, or seven-day periods.
  • boulder_kp() returns the real-time Boulder K index.
  • forecast_text() returns the raw three-day SWPC forecast.

The service is released under the MIT license.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Noaa Swpc

Noaa Swpc is an MCP server that connects AI clients to NOAA's Space Weather Prediction Center through the Pipeworx gateway. Its main tools retrieve alerts, solar wind, planetary and Boulder K indices, aurora forecasts, GOES X-ray flux, and three-day forecast text from NOAA space weather products.

Install it by adding the hosted HTTPS endpoint to your MCP client, or run the npm stdio bridge with npx. The hosted URL is https://gateway.pipeworx.io/noaa-swpc/mcp; the local package is @pipeworx/mcp-noaa-swpc and forwards calls to the same gateway.

Yes, Noaa Swpc works with Cursor through the hosted MCP URL. Add https://gateway.pipeworx.io/noaa-swpc/mcp as an MCP server entry, or configure the npm stdio bridge if you prefer a local process.

No, anonymous calls can run without an API key. The local bridge allows up to 50 calls per day anonymously; a free Pipeworx account and the PIPEWORX_API_KEY environment variable raise that limit to 200 calls per day.

Yes, call the gateway's tool endpoints over HTTP. For example, POST an empty JSON object to https://gateway.pipeworx.io/v1/tools/alerts with a Content-Type of application/json to invoke the alerts tool.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNoaa Swpc AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/noaa-swpc?style=directory)](https://allmcps.com/mcp/noaa-swpc)
HTML Embed
<a href="https://allmcps.com/mcp/noaa-swpc"><img src="https://allmcps.com/api/badge/noaa-swpc?style=directory" alt="Noaa Swpc on AllMCPs" /></a>