Ext Ops Panel
Open dashboard
Comparison

claude-dev-standards vs GeoEDGE MCP

claude-dev-standards is a plugin bundle for AI coding tools published by Nsyamala1. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). GeoEDGE MCP is an MCP server published by GeoEDGE-git. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
Marketplaceclaude-dev-standardsGeoEDGE MCP
Claude Code: claude-plugins-community Listed
Version: ff24e1a
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.9
Downloads/month (PyPI): 713
Downloads/week (PyPI): 107
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

claude-dev-standards vs GeoEDGE MCP
Factclaude-dev-standardsGeoEDGE MCP
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (geoedge-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/nsyamala1/claude-dev-standardsNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

claude-dev-standards

In its own words, on Claude Code: claude-plugins-community:

Universal Development Standards (v2.3.0) — A Claude Code skill that enforces production-grade engineering practices across the full SDLC.

GeoEDGE MCP

In its own words, on Official MCP Registry:

Geospatial analysis: vector and raster GIS operations, cartographic maps, spatial data access

How to run each

claude-dev-standards As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install claude-dev-standards@claude-community

GeoEDGE MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --env "GEOEDGE_MCP_LICENSE_KEY=<YOUR_GEOEDGE_MCP_LICENSE_KEY>" --transport stdio geoedge-mcp -- uvx geoedge-mcp

Requires: GEOEDGE_MCP_LICENSE_KEY (secret)

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of claude-dev-standards publish no settings it asks for, so we do not compare settings.

What it can do: claude-dev-standards · What it can do: GeoEDGE MCP · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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