Weather MCP Server

Created By
SeanLFa year ago
A Model Context Protocol (MCP) server that provides weather forecast data from the Government of Canada Weather API. Fetch accurate 5-day forecasts for any location in Canada by latitude and longitude. Easily integrates with Claude Desktop and other MCP-compatible clients.
Overview

what is Weather MCP Server?

Weather MCP Server is a Model Context Protocol (MCP) server that provides accurate weather forecast data from the Government of Canada Weather API, allowing users to fetch 5-day forecasts for any location in Canada using latitude and longitude.

how to use Weather MCP Server?

To use Weather MCP Server, clone the repository, set up a virtual environment, install the package, and run the server. It can also be integrated with Claude Desktop or other MCP-compatible clients.

key features of Weather MCP Server?

  • Fetch weather forecasts for any location in Canada by providing latitude and longitude.
  • Easily integrates with Claude Desktop or any MCP-compatible client.

use cases of Weather MCP Server?

  1. Providing weather updates for travel planning.
  2. Integrating weather data into applications for real-time updates.
  3. Assisting in agricultural planning based on weather forecasts.

FAQ from Weather MCP Server?

  • Can I use Weather MCP Server for locations outside Canada?

No, Weather MCP Server is designed specifically for Canadian locations only.

  • Is there a cost to use Weather MCP Server?

No, Weather MCP Server is free to use.

  • What programming language is Weather MCP Server built with?

Weather MCP Server is built using Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
SeanLF
Star
0
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)

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago