🌦️ Weekly Weather MCP Server

Created By
rossshannona year ago
Weather MCP server which returns 7 days of detailed weather forecasts anywhere in the world
Overview

What is Weekly Weather MCP?

Weekly Weather MCP is a server that provides 8-day global weather forecasts and current weather conditions using the OpenWeatherMap One Call API 3.0.

How to use Weekly Weather MCP?

To use the Weekly Weather MCP, you need to obtain an OpenWeatherMap API key, run the server with the API key, and configure your MCP-supported client to call the weather functions.

Key features of Weekly Weather MCP?

  • No separate configuration file needed; API key can be passed directly through environment variables or parameters.
  • Support for querying weather conditions anywhere in the world.
  • Provides current weather and detailed 8-day forecasts (today + 7 days).
  • Hourly forecasts for the next 48 hours.
  • Daily forecasts with morning, afternoon, and evening data points.
  • Weather summaries and precipitation probabilities.
  • Detailed weather information including temperature, humidity, wind speed, etc.
  • Support for different time zones.

Use cases of Weekly Weather MCP?

  1. Planning outdoor activities based on weather forecasts.
  2. Determining the best days for lawn mowing or gardening.
  3. Checking weather conditions for travel planning.

FAQ from Weekly Weather MCP?

  • How do I get an OpenWeatherMap API key?

Visit OpenWeatherMap, register an account, and subscribe to the One Call API 3.0 plan.

  • Is there a limit on API calls?

Yes, the free tier allows 1,000 API calls per day, with options to increase limits based on your subscription.

  • What should I do if I encounter an "Invalid API key" error?

Ensure you have subscribed to the One Call API 3.0 plan and that your API key is correctly set in the environment variables.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rossshannon
Star
3
Language
Python
License
MIT 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)

11 hours ago