Weather

io.github.byrnessPublished by GitHub account byrnessv1.0.8Updated Oct 24, 2026

An MCP server for weather information.

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

A local MCP server that provides weather information to an AI assistant.

What you can do
Provides weather information to the assistant through MCP tools, so it can answer weather-related questions during a conversation. The manifest lists no individual tools, so the exact set of queries and locations supported is not documented here. It runs as a local process on the user's machine over stdio.
When to use it
Worth adding when you want an assistant to answer weather questions from within a chat, and you are comfortable running a small local server. It is a narrow, single-purpose server, so it adds little if you do not need weather data.
Requirements
Runs locally over stdio, installed from the npm package @byrness/mcp-weather-server, so a Node.js runtime and npm are needed. The manifest declares no authentication, environment variables or headers. Desktop only; not available as a web executable.
Before you install
The manifest declares no credentials, secrets or write actions. The README gives no detail on where weather data comes from, so you cannot tell from this listing which third-party service receives requests or what data it sees.

Installation

In SourceWeft

  1. Open Weather in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

A Simple MCP weather Server written in TypeScript

See the Quickstart tutorial for more information.

Source: README.md at commit 537b5c7

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.8LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.