Ext Ops Panel
Open dashboard
Comparison

Openweather vs SkyGlance Spotter

Openweather is an MCP server published by mschneider82. Marketplaces we read that list it: 1 (Docker MCP Catalog). SkyGlance Spotter is a plugin bundle for AI coding tools published by Darsh Joshi. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceOpenweatherSkyGlance Spotter
Docker MCP Catalog Listed
Version: sha256:e2f49acbb718
Forks (GitHub): 13
Pulls (Docker Hub): 67 302
Stars (Docker Hub): 4
Stars (GitHub): 21
Not marked · First seen
Not listed
Community marketplace darshjoshi/skyglance-mcp Not listed Listed
Version: 0.3.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Openweather vs SkyGlance Spotter
FactOpenweatherSkyGlance Spotter
Marketplaces that list it11
Stars (GitHub) (differs)21 (better)0 (worse)
Pulls (Docker Hub) (differs)67 302No figure on Docker Hub
Forks (GitHub) (differs)13 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/openweather)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 15, secrets among them: 0
Parts of the bundle (differs)Not a bundle2
LicenceMITMIT
Repository (differs)github.com/mschneider82/mcp-openweathergithub.com/darshjoshi/skyglance-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-13

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Openweather

In its own words, on Docker MCP Catalog:

A simple MCP service that provides current weather and 5-day forecast using the free OpenWeatherMap API.

SkyGlance Spotter

In its own words, on Community GitHub marketplaces:

The Claude directory edition: 22 read-only tools and the sky skill, home location and opt-in history set in the plugin's settings.

How to run each

Openweather As a local MCP server: Docker image

Claude Code
claude mcp add --env "OWM_API_KEY=<YOUR_OWM_API_KEY>" --transport stdio openweather -- docker run -i --rm -e OWM_API_KEY mcp/openweather

Requires: OWM_API_KEY (secret)

SkyGlance Spotter As a Claude Code plugin

Claude Code
/plugin marketplace add darshjoshi/skyglance-mcp
/plugin install skyglance-spotter@skyglance

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of SkyGlance Spotter publish no list of tools, so we do not compare tools.

Settings each asks for

Only Openweather asks for

  • OWM_API_KEY (secret)

Only SkyGlance Spotter asks for

  • SKYGLANCE_EDITION
  • SKYGLANCE_HOME_DIR
  • SKYGLANCE_HOME_LAT
  • SKYGLANCE_HOME_LON
  • SKYGLANCE_POLL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Openweather · What it can do: SkyGlance Spotter · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built