NOAA Alerts MCP for AI. Get real-time US severe weather warnings instantly.

Q: How do I find out what kinds of alerts are available using getalerttypes?

You call getalerttypes first. This returns a list of all valid event category values—like 'Tornado Warning' or 'Flash Flood Watch.' You must use these exact strings when filtering with getactivealerts.

Q: Can I check for alerts in an entire state using getactivealerts?

Yes. Pass the two-letter US state code (e.g., 'FL') to getactivealerts. You can then further narrow that search by severity or event type.

Q: Which tool is best for checking a specific intersection?

Use getalertsbypoint. This requires the precise latitude and longitude of the location, giving you the most granular answer possible regarding active warnings at that exact spot.

Q: What if I only have an NWS zone ID?

Use getalertsbyzone. This tool accepts a specific NOAA Zone ID (like TXZ211) and retrieves all alerts applicable to that entire, focused region.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

How this MCP server connects to your AI agent

NOAA Alerts — US Severe Weather Warnings delivers real-time NWS data. Get active warnings—tornadoes, floods, hurricanes—filtered by state, severity level, or exact coordinates anywhere in the United States.

Check every alert type from 120+ event categories instantly.

What AI agents can do with NOAA Alerts — US Severe Weather Warnings Automation

Get active alerts

Filters active weather alerts by US state, severity (Extreme/Severe), urgency, or specific event type. This is the primary alert retrieval tool.

Get alerts by zone

Gets all active weather alerts for a predefined, focused NWS zone ID (e.g., FLZ050).

Get alerts by point

Retrieves all active alerts affecting a specific US location using latitude and longitude coordinates.

+ 1 more capabilities included

Filter alerts by state and criteria

Use get_active_alerts to pull warnings based on a US state code (e.g., CA) and specific parameters like severity or event type.

List all possible alert types

Run get_alert_types to get a definitive list of every 120+ NWS event category available for filtering.

Get alerts by coordinates

Send latitude and longitude values to get_alerts_by_point to pinpoint all active warnings in that exact geographic spot.

Monitor specific zones

Pass a NWS zone ID (like FLZ050) to get_alerts_by_zone for focused monitoring of a defined region.

Ask an AI about this

Included with Plan

Waiting for input…

AI Agent

What AI agents can do with NOAA Alerts: 4 Tools for Real-Time Warning Data

Use these four tools to query real-time US severe weather warnings. Filter alerts by location (point/zone), state, or event type.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using NOAA Alerts — US Severe Weather Warnings on Vinkius

Get Active Alerts

Filters active weather alerts by US state, severity (Extreme/Severe), urgency, or specific event type. This is the primary alert retrieval...

Get Alerts By Zone

Gets all active weather alerts for a predefined, focused NWS zone ID (e.g., FLZ050).

Get Alerts By Point

Retrieves all active alerts affecting a specific US location using latitude and...

Get Alert Types

Lists every possible NWS weather alert category ID. Use this to discover valid...

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

Start a conversation

Open a new chat. The NOAA Alerts integration is available immediately — no restart needed.

Antigravity

Configure Agent Environment

Open your Antigravity agent's workspace configuration or mcp-servers.json file.

Bind the Endpoint

Add the Vinkius endpoint URL to your agent's MCP connections list:

"mcp_servers": {
  "noaa-alerts-us-severe-weather-warnings": {
    "serverUrl": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
  }
}

Provide your secure token in place of [YOUR_TOKEN_HERE] to ensure your agent requests are authenticated.

Execute

Start your Antigravity session. The agent will autonomously discover and utilize the NOAA Alerts tools with full Vinkius guardrails applied.

VS Code Copilot

⚡

One-Click Install (Recommended)

In your Vinkius Dashboard, simply click the Add to VS Code button for this server. We'll automatically configure your local workspace.

Or configure manually

Open MCP Settings

Open VS Code, press Ctrl/Cmd + Shift + P, and search for GitHub Copilot: MCP Servers.

Add Server Config

Add the Vinkius endpoint configuration to your mcp-servers.json file:

"noaa-alerts-us-severe-weather-warnings": {
  "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}

Ensure you replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

LangChain

Install Dependencies

Install the LangChain MCP adapters for your environment:

pip install langchain-mcp-adapters

Connect the Server

Use the SSEClient in LangChain to connect to the Vinkius managed endpoint:

from langchain_mcp_adapters.client import SSEClient

# Connect to Vinkius
client = SSEClient(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
tools = client.get_tools()

CrewAI

Define the Tool

Load the Vinkius MCP tools into your CrewAI agents:

from crewai import Agent
from mcp_crewai import MCPTool

# Connect securely to Vinkius
vinkius_tools = MCPTool(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

# Assign to Agent
researcher = Agent(
    role='Data Researcher',
    tools=vinkius_tools.get_all()
)

Execute Task

Run your CrewAI process. The agent will autonomously route tasks to the Vinkius managed server.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on every call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with NOAA Alerts — US Severe Weather Warnings, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 5,100+ others, all in one place
Add new capabilities to your AI anytime you want
Every connection is secured and compliant automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog every week

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by NOAA. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 4 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Checking for severe weather warnings shouldn't require switching between three different government dashboards., Solved with Vinkius AI Gateway

Today, if you need to know about a flood watch in Texas, you might have to check the NOAA site for state coverage, then Google Maps for coordinates, and maybe call an API just to confirm the alert type. It's slow, it’s fragmented, and it's prone to missing details.

With this MCP server, your agent runs one command: 'Check all flood alerts in central Texas.' It handles the state boundaries, pulls the latest data from `get_active_alerts`, and gives you a clean list of what's active. You just get the answer.

NOAA Alerts MCP Server: Get precise warnings by point or zone.

Manually checking an alert for a major city involves guessing if it falls under a state code, a specific NWS zone ID, or just needs lat/lon. This guesswork wastes time when seconds count.

Now you can use `get_alerts_by_point` to pinpoint the exact risk at any latitude/longitude pair. It's immediate, precise, and works every single time.

Support 24/7 support@vinkius.com ↗

Security Vinkius Trust Center ↗

SLA Service Level Agreement ↗

Report Listing Send Report ↗

severe-weather

emergency-alerts

real-time-notifications

disaster-preparedness

nws-data

geospatial-data

What your AI can actually do with this

NOAA Alerts: Real-Time US Severe Weather Warnings

You're gonna get real-time access to active weather alerts across the entire United States; this server pulls all its data straight from NWS feeds. It lets your AI client check everything—tornadoes, floods, hurricanes—filtered by state code, severity level, or even exact coordinates anywhere in the U.S.

The system gives you four distinct ways to pull critical data using specific tools.

To get active warnings based on a whole US state, you use get_active_alerts. This tool lets you filter alerts using a US state code (like CA) and narrow it down by parameters such as severity or the specific event type. You'll need to run get_alert_types first; that function gives you a definitive list of every NWS event category ID, letting you know exactly what filters are valid for your other tools.

If you gotta monitor a defined region, you use get_alerts_by_zone. Just pass in a specific NWS zone ID—say, FLZ050—and it pulls all active weather alerts affecting that focused area. For pinpoint accuracy, send the latitude and longitude values to get_alerts_by_point; this tool retrieves every active warning impacting that precise geographic spot.

If you need a broad sweep of available alert types without specifying location or criteria, run get_alert_types to get a complete list of all 120+ NWS event categories. This lets your agent know what filter values it can use when calling the other tools.

This data is critical for emergency management, logistics operations, insurance claims processing, and any workflow that needs reliable, immediate weather awareness. You're dealing with active warnings—tornadoes, floods, hurricanes—and you need to check every alert type instantly, which this server handles through its mechanisms:

You can pull all alerts for an entire US state using get_active_alerts and filter by severity or event type.
You can pinpoint active warnings affecting a precise spot on the map by sending coordinates to get_alerts_by_point.
You can focus your monitoring on a specific, predefined region using get_alerts_by_zone, just by passing in the NWS zone ID.
To build out custom filtering criteria for any tool, you always start by running get_alert_types to get that definitive list of all available alert categories.

The server gives your agent four specific tools: get_active_alerts filters alerts by US state code and allows narrowing results using severity (Extreme/Severe), urgency level, or a chosen event type; get_alert_types lists every possible NWS weather alert category ID available for filtering purposes across the entire system; get_alerts_by_point retrieves all active alerts that affect an exact US location based on provided latitude and longitude coordinates; and get_alerts_by_zone gets all active weather warnings for a focused, predefined NWS zone ID.

You use these tools to pull everything from the whole country down to one specific GPS coordinate. You're always dealing with real-time data across 120+ event categories and multiple severity levels.

Built · Hosted · Managed by Vinkius NOAA Alerts — US Severe Weather Warnings MCP Server

Server ID 019d75de-438e-700a-b1cd-66984ac92dd0

Vinkius Inspector

Compliance Grade A+

Score 100/100

Report View Report ↗

Here's how it actually works

The bottom line is you get structured, real-time weather alerts pulled directly into your agent's context using specific tools.

First, you tell your AI agent what kind of alerts you need—for example, 'Tornado Warnings in Florida.'

The agent selects the best tool (get_active_alerts) and passes the necessary parameters (State: FL, Severity: Severe, Event Type: Tornado Warning).

The server executes the query and returns a structured list of active warnings, including location, expiration time, and advisory details.

Who is this actually for?

This is for the operations engineer who can't rely on manual dashboard checks at 2 AM. It targets anyone whose job relies on knowing exactly where a weather event hits and when it ends—from supply chain managers to emergency dispatchers.

Logistics Coordinator

Checks for severe alerts in shipping lanes or port cities before scheduling transport routes.

Emergency Dispatcher

Instantly pulls get_active_alerts by point to confirm which neighborhoods need immediate evacuation warnings.

Risk Analyst/Insurance Underwriter

Runs checks using get_alert_types and get_active_alerts to map the scope of potential damage across multiple states after a storm hits.

What Changes When You Connect

Pinpoint exact risks with get_alerts_by_point. Don't just know the state; find out what hit 34.05 N, 118.24 W right now.

Manage complex data sets using get_active_alerts to filter by severity (Extreme, Severe, etc.) and event type—don't waste time sifting through irrelevant warnings.

Streamline regional monitoring with get_alerts_by_zone. Instead of querying a whole state, you focus only on the specific NWS zone ID for better performance.

Avoid guessing what kind of alert exists. Use get_alert_types to pull the master list and ensure your agent queries against valid event categories every time.

Confirm operational status instantly. Instead of checking multiple dashboards, one call can aggregate all active alerts across a state or zone.

See it in action

01 01

Planning an industrial site shutdown

A plant manager needs to know if the facility is safe before workers return. They prompt their agent: 'What severe weather warnings are active near our coordinates?' The agent runs get_alerts_by_point and returns a list showing no critical alerts, confirming safety.

02 02

Tracking flood risk in multiple counties

A civil engineer needs to assess the scope of flood damage across several areas. They use get_active_alerts, filtering by 'Flood' event type and checking specific zones via get_alerts_by_zone for a comprehensive view.

03 03

Responders need immediate confirmation

During an active emergency, dispatch needs to confirm if the highest level of threat is present. They ask: 'Show me all Extreme severity alerts nationwide.' The agent calls get_active_alerts using the 'Extreme' filter and gets a prioritized list.

04 04

Mapping seasonal weather change

A climate researcher wants to know every type of warning possible. They first call get_alert_types to build a master dictionary, then use that list with get_active_alerts to map the full range of potential warnings.

The honest tradeoffs

Checking every location separately

Anti-pattern

A user tries to check 50 different addresses by calling get_alerts_by_point fifty times in a row. This is slow, expensive, and brittle.

The Fix

Instead of point-by-point checks, use get_active_alerts combined with state codes or use get_alerts_by_zone if the locations fall within a defined NWS zone.

Ignoring alert types

Anti-pattern

A user only asks for 'Tornado Warnings' but misses other critical advisories like Flash Flood Watches, potentially missing vital context.

The Fix

Always run get_alert_types first. Then use the full list of event types in get_active_alerts to ensure you capture all relevant warnings.

Over-relying on state names

Anti-pattern

The agent assumes a single call for 'Texas' covers every corner, but misses alerts that fall between defined NWS zones.

The Fix

For focused coverage, use get_alerts_by_zone with the specific zone ID (e.g., TXZ211). This provides better geographical granularity than just the state name.

When It Fits, When It Doesn't

Use this server if your process requires real-time weather data and needs to filter by location, severity, or event type. It's perfect for logistics planning, emergency response tools, and risk modeling. Don't use it if you just need general historical climate trends (you’d need a separate archival service). Also, don't try to pull alerts for locations outside the US; this data is strictly NWS-sourced. If your main requirement is filtering by where an alert hits, start with get_alerts_by_point. If you need to check a whole region quickly, use get_active_alerts filtered by state code. Use get_alert_types whenever you are building new logic and aren't sure of the exact filter names.

Questions you might have

How do I find out what kinds of alerts are available using get_alert_types? +

You call get_alert_types first. This returns a list of all valid event category values—like 'Tornado Warning' or 'Flash Flood Watch.' You must use these exact strings when filtering with get_active_alerts.

Can I check for alerts in an entire state using get_active_alerts? +

Yes. Pass the two-letter US state code (e.g., 'FL') to get_active_alerts. You can then further narrow that search by severity or event type.

Which tool is best for checking a specific intersection? +

Use get_alerts_by_point. This requires the precise latitude and longitude of the location, giving you the most granular answer possible regarding active warnings at that exact spot.

What if I only have an NWS zone ID? +

Use get_alerts_by_zone. This tool accepts a specific NOAA Zone ID (like TXZ211) and retrieves all alerts applicable to that entire, focused region.

If I use `get_alerts_by_point` with incorrect latitude or longitude, how does the tool handle it? +

It returns a specific error message indicating invalid coordinates. The system won't crash; instead, your agent receives an explicit failure signal and no alert data. You can then adjust your input values.

When running `get_active_alerts`, can I filter by both severity level and event type simultaneously? +

Yes, you pass multiple parameters to refine the search. For instance, you can request all 'Severe' alerts that are specifically a 'Flash Flood Watch.' This narrows down results quickly.

Using `get_active_alerts`, what key data points (like expiration time or county name) should I expect in the response object? +

The alert payload includes critical details: the specific geographic area, the defined severity level, and a precise end timestamp. This lets you know exactly when the warning expires.

Does the server impose any rate limits when calling `get_alerts_by_zone` repeatedly during a short period? +

The service is designed for frequent querying, but we recommend checking the official NOAA API documentation linked in the listing. High-volume usage may require adhering to standard API quota policies.

How quickly are alerts updated? +

NWS alerts are updated in real-time. When a warning is issued or cancelled, it appears within seconds on the API. Tornado Warnings have a typical lead time of 13 minutes.

How this MCP server connects to your AI agent

NOAA Alerts — US Severe Weather Warnings delivers real-time NWS data. Get active warnings—tornadoes, floods, hurricanes—filtered by state, severity level, or exact coordinates anywhere in the United States.Check every alert type from 120+ event categories instantly.

What AI agents can do with NOAA Alerts — US Severe Weather Warnings Automation

Get active alerts

Get alerts by zone

Get alerts by point

What AI agents can do with NOAA Alerts: 4 Tools for Real-Time Warning Data

Get Active Alerts

Filters active weather alerts by US state, severity (Extreme/Severe), urgency, or specific event type. This is the primary alert retrieval...

Get Alerts By Zone

Gets all active weather alerts for a predefined, focused NWS zone ID (e.g., FLZ050).

Get Alerts By Point

Retrieves all active alerts affecting a specific US location using latitude and...

Get Alert Types

Lists every possible NWS weather alert category ID. Use this to discover valid...

Security and governance baked right in.

Claude AI

Open Claude Settings

Add Custom Connector

Start a conversation

Claude Code

Open your terminal

Add the MCP Server

Start coding

Cursor

One-Click Install (Recommended)

Open Cursor Settings

Add New Server

Use in Composer

Antigravity

Configure Agent Environment

Bind the Endpoint

Execute

VS Code Copilot

One-Click Install (Recommended)

Open MCP Settings

Add Server Config

Windsurf

One-Click Install (Recommended)

Open Windsurf Settings

Add Server Endpoint

LangChain

Install Dependencies

Connect the Server

CrewAI

Define the Tool

Execute Task

Choose How to Get Started

Build Your Own

Make Your AI Do More

Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more

Checking for severe weather warnings shouldn't require switching between three different government dashboards., Solved with Vinkius AI Gateway

NOAA Alerts MCP Server: Get precise warnings by point or zone.

severe-weather

emergency-alerts

real-time-notifications

disaster-preparedness

nws-data

geospatial-data

What your AI can actually do with this

NOAA Alerts: Real-Time US Severe Weather Warnings

Here's how it actually works

Who is this actually for?

What Changes When You Connect

Planning an industrial site shutdown

Tracking flood risk in multiple counties

Responders need immediate confirmation

Mapping seasonal weather change

The honest tradeoffs

Checking every location separately

Ignoring alert types

Over-relying on state names

When It Fits, When It Doesn't

Questions you might have

NOAA Alerts — US Severe Weather Warnings delivers real-time NWS data. Get active warnings—tornadoes, floods, hurricanes—filtered by state, severity level, or exact coordinates anywhere in the United States.

Check every alert type from 120+ event categories instantly.