SkillFoxx

Yandex Weather MCP

A local MCP server for the Yandex Weather API: current conditions, forecast, a short summary and comparing two locations, with caching

  • 0 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • Runs a Node.js server that calls the Yandex Weather API with your key and caches responses
  • Only reads weather data
All reasons and checks
Russian stack

aleks-yustas/yandex-weather-mcpAuthor:aleks-yustas

A similar tool with a larger community: Yandex Weather MCP server (SmartHome), 3 ★ on the repository

Install

Manual install

npm install && npm run build && npm start

Local run after cp .env.example .env and filling in YANDEX_WEATHER_API_KEY.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Runs a Node.js server that calls the Yandex Weather API with your key and caches responses
  • Only reads weather data

This is third-party code. Review the repository files before installing.

What it does

The server hides the Yandex Weather key from the MCP client and provides four tools: current weather, a multi-day forecast, a short text summary with advice, and a comparison of two locations. API responses are normalized and cached for 5 to 15 minutes, and input coordinates are validated with Zod schemas. It can run locally via npm or in Docker with HTTP transport on /mcp and a health check, with a sample Nginx config for VDS deployment.

Who it is for. For people who want an agent to check the weather by coordinates instead of opening a weather app

Good fit when

  • You want an agent to answer current weather or forecast questions by coordinates
  • You need to compare weather in two cities in one request
  • You want a self-hosted weather MCP server instead of a third-party cloud one

Not a fit when

  • You need a ready public server without your own key and deployment
  • You need hourly data not available on your Yandex Weather plan

Example request

Compare the weather in Moscow and Saint Petersburg right now and tell me where it is warmer

MCP

Transport
stdio, http
Authentication
API key

Environment variables

YANDEX_WEATHER_API_KEY required, secret
Yandex Weather API key
YANDEX_WEATHER_LANG
Response language, e.g. ru_RU
CACHE_TTL_SECONDS
Response cache TTL in seconds
MCP_TRANSPORT
MCP transport: http or stdio
PORT
HTTP server port, default 3000

Limitations

The project has no stars and, per the README, was written by a single author using a role-play write-up style to explain decisions. It needs your own Yandex Weather API key and your own hosting or a local run; there is no ready public endpoint. There is no stable release or npm version.

How to disable. Stop the container or server process and remove it from your MCP client config.

FAQ

Where do I get an API key?

In the Yandex Weather or Yandex API personal cabinet; the endpoint is set via YANDEX_WEATHER_API_URL if your plan uses a different address.

Can I run it without Docker?

Yes, with npm install, npm run build and npm start, setting MCP_TRANSPORT=stdio for a local MCP client.

Discussion

No questions or reviews yet.

MCP servers
Russian stack

A small MCP server on the Yandex Weather SmartHome API: current weather, daily and hourly forecasts with a free-tier key

MCP serverExtended access3

A weather MCP in Go: the current_weather tool gives the agent current weather by city name from WeatherAPI, run locally or in Docker

MCP serverExtended access246
Russian stack

A small test Yandex Calendar MCP server over CalDAV: upcoming events, event creation and deletion with no confirmation step

MCP serverBroad access
Russian stack

A Go MCP server for reading Yandex Tracker and Yandex Wiki: issues, queues, sprints, comments, pages and dynamic tables

MCP serverExtended access14

Yandex Disk MCP (Antiloop)

Yandex Disk MCP Server

Russian stack

Yandex Disk MCP server: files and folders, public links, upload from URL, trash and search, with Docker support

MCP serverBroad access5

README in short

The README frames the server as the result of several role perspectives (backend, devops, integrations, MCP, quality) and explains choosing TypeScript and Node.js. It covers .env setup, a local run, Docker with HTTP transport on /mcp, four MCP tools with JSON examples, and a VDS deployment guide with Nginx and firewall notes.

README badge

Report a problem