# US Airport Weather Sentinel AI Agent Connect > US Airport Weather Sentinel MCP connects your AI agent to the National Weather Service. It provides real-time METAR observations and active weather alerts for US airports. Instead of checking multiple tabs, your agent can monitor wind gusts, visibility, and storm warnings, reporting only the specific changes that matter since your last check. ## Overview - **Category:** travel - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_ZdrZHqXg8XNnQGjdphhjeaC6hRhbVasIygU5q5HU/ai-agent-connect - **Tags:** airport, weather, nws, alerts, metar, travel, sentinel, disruption ## Description You can stop manually refreshing weather pages to see if a storm is hitting your flight path. This MCP pulls live data from the National Weather Service and gives your AI client a direct line to airport conditions. You can ask for a full snapshot of an airport's current status, including temperature, wind, and visibility, alongside any active warnings in that zone. If you are monitoring an airport over a long period, you don't need to re-read the same data. You can use delta tools to have your agent report only what has changed, such as a new wind gust or a newly issued tornado warning. It works for single airports or you can batch up to three locations to get a quick status check on a flight corridor. It is a stateless, keyless way to keep your agent informed about weather-driven disruptions without managing complex API credentials. ## Tools ### airport_status Provides current METAR conditions and active NWS alerts for a specific US airport. Use this for an initial check before travel to see immediate weather and warnings. ### alert_watch Monitors active NWS alerts for an airport zone. You can filter for specific events like FloodWarnings or TornadoWarnings to focus on what matters. ### alerts_delta Returns only the new or recently expired NWS alerts since a specific timestamp. This prevents your agent from repeating old information. ### conditions_delta Identifies changes in observed weather like wind gusts or visibility since your last check. It tracks specific shifts in temperature, wind, and visibility. ### find_airports Locates the correct IATA or ICAO code for a US airport. Use this when you only have a city name or a partial airport name. ### watch_status Fetches a compact status report for up to three US airports at once. This is the fastest way to check a multi-leg trip or a specific flight corridor. ## Prompt Examples **Prompt:** ``` Is there anything going at SFO right now that would affect my flight? ``` **Response:** ``` SFO currently has clear visibility and light winds, but there is an active Wind Advisory in the zone. ``` **Prompt:** ``` Last check at JFK was at 14:00 UTC. What changed since then? ``` **Response:** ``` Since 14:00 UTC, a new Severe Thunderstorm Warning has been issued for the JFK area. ``` **Prompt:** ``` Check SFO, JFK, and DEN in one go. Any of them in trouble? ``` **Response:** ``` SFO and DEN are clear. JFK has an active Winter Storm Warning active in its zone. ``` ## Capabilities ### Delta Reporting Your agent compares timestamps to report only new weather changes or alerts. ### Multi-Airport Batching The agent checks up to three airports in a single request to save time. ### Specific Alert Filtering You can instruct your agent to watch only for specific threats like Tornado or Flood warnings. ### Airport Discovery The agent finds the correct airport codes using city names or fragments. ## Use Cases ### Pre-flight Check Ask your agent for a full airport status report to see if visibility or wind will impact your departure. ### Continuous Monitoring Set your agent to check for delta changes in weather conditions every few minutes. ### Alert Watchlisting Focus your agent on specific weather threats like Winter Storm Warnings for a specific region. ### Corridor Scanning Check the status of three different airports along a flight route in one command. ## Benefits - Reduces noise by reporting only weather changes since the last check. - Eliminates the need to manage NWS API credentials manually. - Consolidates METAR data and NWS alerts into a single response. - Allows for rapid status checks across multiple airport locations. ## How It Works Connect the MCP to your client and start querying airport data immediately. 1. Connect the MCP to your preferred client like Claude or Cursor. 2. Use find_airports to get the correct IATA code for your destination. 3. Run airport_status to get the initial weather and alert snapshot. 4. Pass the previous timestamp to delta tools to receive only new updates. ## Frequently Asked Questions **Do I need an API key for the National Weather Service?** No. This MCP uses the public NWS API, so there are no credentials or accounts required to use it. **How many airports can I check at once?** You can check up to three US airports in a single call using the watch_status tool. **How does the delta feature work?** You provide a timestamp from your previous check, and the MCP returns only the new alerts or weather changes that occurred after that time. **Can I filter for specific types of weather warnings?** Yes. You can use the alert_watch tool to monitor specific event types like TornadoWarnings or FloodWarnings. **What happens if the airport station feed is empty?** If the station feed is momentarily empty, the conditions field may return null. **Do I need credentials?** No. The National Weather Service API is public and requires no key, no account, no signup. Anonymous access is rate-limited to roughly 30 requests per minute, which is why batched calls are capped at 3 airports and the tools keep their fetch count low. **How do the "since" delta tools work?** The server is stateless. Call airport_status (or any delta tool), keep the as_of timestamp in the agent's context, and on the next check pass it as since. The tool fetches the recent observations/alerts and returns only what is newer than that timestamp — e.g. new alerts, gusts above 39 km/h, visibility drops. The station feed keeps ~50 most recent observations, so a baseline older than that window comes back as "no observations since X" with a note. **Which airports are supported?** The major US commercial airports (roughly 45): JFK, LGA, EWR, BOS, IAD, ATL, ORD, DFW, AUS, DEN, SEA, SFO, LAX, SNA, PHX, LAS, SLC, MCO, MIA, FLL, TPA, MSY, STL, DTW, BNA, MEM, CHS, CLT, RDU, GSP, OAK, PDX, GEG, RNO, ONT, SAN, HNL and more. find_airports lists the exact supported codes; the airport code resolves to its NWS forecast zone and METAR station automatically. **Why can't I filter alerts by state or time?** The NWS API's 2026 revision dropped the state/sent/since query parameters — the server resolves your airport to its NWS forecast zone and filters time deltas client-side from the timestamps each alert carries. So you always filter by the airport (zone) and by `since`, which is what a traveler cares about anyway.