MCP Weather Server

Created By
Samarth2001a year ago
Overview

what is MCP Weather Server?

MCP Weather Server is a weather information tool that provides weather forecasts, alerts, and observations using the National Weather Service (NWS) API. Built with FastMCP.

how to use MCP Weather Server?

To use MCP Weather Server, install the required dependencies using pip and then utilize the various API endpoints to fetch weather data.

key features of MCP Weather Server?

  • Get Weather Alerts: Fetch active weather alerts for any US state
  • Get Forecast: Retrieve daily weather forecasts for any location
  • Get Hourly Forecast: Get hour-by-hour forecast data
  • Find Weather Stations: Locate observation stations near a specified location
  • Get Observations: Fetch current weather conditions from specific stations
  • Get Point Metadata: Retrieve detailed location information
  • Get Fire Weather: Access specialized fire weather forecasts

use cases of MCP Weather Server?

  1. Providing real-time weather updates for applications
  2. Integrating weather alerts into user notifications
  3. Analyzing weather patterns for research purposes

FAQ from MCP Weather Server?

  • Do I need an API key to use MCP Weather Server?

No, an API key is not required, but proper request attribution via User-Agent is implemented.

  • What programming language is MCP Weather Server built with?

MCP Weather Server is built with Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Samarth2001
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago