MCP Weather Server

Created By
le-yoa year ago
Weather MCP server
Overview

What is MCP Weather Server?

The MCP Weather Server is a simple Model Context Protocol (MCP) server that provides weather information for any location.

How to use MCP Weather Server?

To use the MCP Weather Server, clone the repository, install the dependencies, and run the server using Node.js. Connect it to Claude Desktop by adding it as a new MCP server in the settings.

Key features of MCP Weather Server?

  • Get current weather information for any location.
  • Compatible with Claude Desktop and other MCP clients.
  • Uses the free wttr.in weather API (no API key required).

Use cases of MCP Weather Server?

  1. Retrieving current weather conditions for various locations.
  2. Integrating weather data into AI applications.
  3. Providing weather updates through voice assistants like Claude.

FAQ from MCP Weather Server?

  • Can I use this server without an API key?

Yes! The server uses the free wttr.in API, which does not require an API key.

  • Is it possible to extend the server?

Yes! You can add more weather-related tools or implement other MCP features.

  • What programming language is used for this server?

The server is built using JavaScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
le-yo
Star
1
Language
JavaScript
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)

a day ago